keybase / keybase/keybase-issues
second web site via DNS verification cause first to be untrusted
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if this is the real issue, but I registered angrybug.com using DNS TXT record, and it succeeded. Then I registered steveh.id.au via DNS TXT record, and it succeeded. Later I noticed that the first one is now failing the proof.
Is this an issue?
Regards,
Steve.
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
Reproduce the DNS TXT verification flow with angrybug.com and steveh.id.au, then investigate why the earlier proof is reported as failing after the second registration. Done means both sites' trust status is explained and the issue has a confirmed cause or documented non-bug behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100