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

Update DarkMail #18

Open
elijh opened this issue Sep 6, 2014 · 0 comments
Open

Update DarkMail #18

elijh opened this issue Sep 6, 2014 · 0 comments

Comments

@elijh
Copy link
Contributor

elijh commented Sep 6, 2014

DarkMail plans have changed a lot lately. Some clarifications it would be good to add:

  • For key validation, DarkMail is using a modified form of DNSSEC/DANE. Essentially, provider endorses user keys. There was some mention in the talk very briefly about a forward hash in the key format, so that an auditor could detect if they have seen all the endorsed keys, or detect if provider tries to split the endorsement chain. Not perfect, since a provider might still alter the chain, but it reduces their opportunities to do so.
  • For meta-data protected routing, DarkMail is using "onion headers", where sending relay doesn't know recipient and recipient relay doesn't know sender. This breaks down for single provider situations, but is a valid way to go.
  • DarkMail server supports both SMTP and DMTP (their new SMTP replacement), switching between the two.
  • DarkMail keys are like OpenPGP, but redesigned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant