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

Gossip headers when using Autocrypt #48

Closed
carmelatroncoso opened this issue May 11, 2018 · 4 comments
Closed

Gossip headers when using Autocrypt #48

carmelatroncoso opened this issue May 11, 2018 · 4 comments

Comments

@carmelatroncoso
Copy link
Collaborator

At the beginning, we say that the Gossip headers do not change. Is this true? If this is the case what is the use of the Autocrypt? Or does the gossip only include the sender's key?

@azul
Copy link
Member

azul commented May 12, 2018

@carmelatroncoso I'm not sure what you are referring to. Can you point me to the section and cite the phrase?

Thanks! 🌞

@carmelatroncoso
Copy link
Collaborator Author

Section inclusion in messages, under "Use and architecture". Now has my version (of what I thought you wanted to say), but before it read like this:

Every mail has the Autocrypt header as usual:

Autocrypt: ...
Gossip headers are left untouched (in contrast to in-band cc).

In addition we include a header with our head imprint (root hash of our latest CC block) in the encrypted and signed part of the message:

@azul
Copy link
Member

azul commented May 14, 2018

Ahh... I think now i understand the confusion. I was trying to say that the gossip headers are left untouched by the claimchain addition. The headers themselves contain the senders believ about all recipients keys.

I will look at the current version and try to make this more clear. I think i will remove the entive part talking about what stays the same.

@azul
Copy link
Member

azul commented May 14, 2018

Just read the section after you rewrote it and it exactly covers what i meant. Thanks!

@azul azul closed this as completed May 14, 2018
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

2 participants