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.

Sign up for GitHub

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

Jump to bottom

Communications Security #3

Open
Whytehorse opened this issue Aug 11, 2017 · 3 comments
Open

Communications Security #3

Whytehorse opened this issue Aug 11, 2017 · 3 comments

Comments

@Whytehorse
Copy link

We need to add a list of public keys to the FAQ so that fraudsters can't impersonate us, redirect funds, etc.
@xsttx
Copy link
Contributor

xsttx commented Aug 11, 2017

Yes

@xsttx
Copy link
Contributor

xsttx commented Aug 11, 2017

How do you suggest implementing it?

@Whytehorse
Copy link
Author

I would just copy/paste the public key into a doc on github and then use it to sign announcements, binaries, etc. Then we can just verify the MD5sum of the files or the signature on the announcement to verify it's authenticity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Whytehorse @xsttx