DNS proof instructions unsafe
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Yesterday I tried to proof I own grons.nl. The app (Mac 1.0.34-20171027003854+8e989533a) instructs to create a DNS record named grons.nl. and if that wouldn't work a record named @.
Too late I realized that I already have a record grons.nl. for the SPF configuration. That record was then overwritten by my DNS provider.
In the second attempt, @ as name was ignored by my DNS provider. So it again created a record named grons.nl..
May I suggest that the record be named _keybase.[domain].? This is more in line with what dmarc and domainkeys are doing.
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 tracing the DNS proof flow that produces the Mac app's record-name instructions, using the reported grons.nl. and @ cases as reproduction targets. Verify that the guidance uses a dedicated _keybase.[domain]. record and does not overwrite an existing SPF record; add or update coverage for both provider behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100