strong password in dbconfig.yml not escaping
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 292
- PR merge metrics
- No merged PRs in 30d
Description
For some reason in the following
development:
dialect: postgres
datasource: dbname=local user=admin password="......" host=localhost port=5432 sslmode=disable
dir: migrations/postgres
When I use a complicated strong password with symbols, this gives me auth errors, but as soon I turn the password to something simple - it goes through.
Am I missing something?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the authentication failure with the dbconfig.yml example, varying the password symbols while keeping the PostgreSQL connection settings unchanged. Trace how the datasource password is parsed and determine which strong-password cases fail; the issue is done when valid passwords containing symbols authenticate successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100