Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify DNS TXT record schema modification #63

Merged
merged 2 commits into from
Sep 9, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Add note about key being a 64-character hex string
As requested by @RangerMauve
  • Loading branch information
ryanramage authored Sep 2, 2019
commit aec2791218d806ceca5ada59ff55783fa6710f5f
2 changes: 1 addition & 1 deletion proposals/0005-dns.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ The first option is to set a DNS TXT record at the domain which maps to a "key"-
datkey={key}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we clarify that the key in this case must be 64 hex characters?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I have added that to the note. on line 68.

```

The above schema does not have to start of the TXT record, it just has to match somewhere in the TXT record.
The above schema does not have to start of the TXT record, it just has to match somewhere in the TXT record. The 'key' must be a 64-character hex string.

## .well-known/dat
[usage-wellknown-dat]: #usage-wellknown-dat
Expand Down