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

Use SHA256 or SHA512 for all PGP signatures #1116

Closed
andrewdavidwong opened this Issue Aug 12, 2015 · 6 comments

Comments

Projects
None yet
3 participants
@andrewdavidwong
Member

andrewdavidwong commented Aug 12, 2015

SHA256 or SHA512 should be used as the digest algorithm for PGP signatures on all of the following:

  • ISOs (switched to SHA256)
  • Developer emails (switched to SHA256)
  • QSBs (partial: Marek switched to SHA256; Joanna is still using SHA1)
  • Warrant canaries (partial: Marek switched to SHA256; Joanna is still using SHA1)
@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Aug 12, 2015

Member

Does anyone know if there's any reason to prefer SHA512 over SHA256 (either in general or for specific purposes)? For example, the Tor Project signs their TBB archives with SHA512, but I'm not sure whether that's because it's more secure or faster[1] or both.

[1] http://crypto.stackexchange.com/q/26336

Member

andrewdavidwong commented Aug 12, 2015

Does anyone know if there's any reason to prefer SHA512 over SHA256 (either in general or for specific purposes)? For example, the Tor Project signs their TBB archives with SHA512, but I'm not sure whether that's because it's more secure or faster[1] or both.

[1] http://crypto.stackexchange.com/q/26336

@marmarek marmarek added this to the Release 3.1 milestone Sep 2, 2015

@marmarek marmarek added the T: task label Sep 2, 2015

@rootkovska rootkovska added task and removed T: task labels Sep 2, 2015

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 8, 2015

Member

SHA-1 Freestart Collision

Abstract: We present in this article a freestart collision example for SHA-1, i.e., a collision for its internal compression function. This is the first practical break of the full SHA-1, reaching all 80 out of 80 steps, while only 10 days of computation on a 64 GPU cluster were necessary to perform the attack. [...]

Member

andrewdavidwong commented Oct 8, 2015

SHA-1 Freestart Collision

Abstract: We present in this article a freestart collision example for SHA-1, i.e., a collision for its internal compression function. This is the first practical break of the full SHA-1, reaching all 80 out of 80 steps, while only 10 days of computation on a 64 GPU cluster were necessary to perform the attack. [...]

marmarek added a commit to marmarek/qubes-builder that referenced this issue Oct 12, 2015

marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue Oct 28, 2015

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jul 31, 2016

Member

@rootkovska, would you be willing to switch to SHA256 or SHA512 for signing QSBs and canaries? Your signatures on those are the only two things left.

Member

andrewdavidwong commented Jul 31, 2016

@rootkovska, would you be willing to switch to SHA256 or SHA512 for signing QSBs and canaries? Your signatures on those are the only two things left.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 5, 2016

Member

@rootkovska you can simply add digest-algo SHA256 to ~/.gnupg/gpg.conf in your qubes-secpack accessing VM (or appropriate split-gpg backend).

Member

marmarek commented Aug 5, 2016

@rootkovska you can simply add digest-algo SHA256 to ~/.gnupg/gpg.conf in your qubes-secpack accessing VM (or appropriate split-gpg backend).

@rootkovska

This comment has been minimized.

Show comment
Hide comment
@rootkovska

rootkovska Aug 7, 2016

Member

Sure, I shall switch for the next secpack canary.

Member

rootkovska commented Aug 7, 2016

Sure, I shall switch for the next secpack canary.

@rootkovska

This comment has been minimized.

Show comment
Hide comment
@rootkovska

rootkovska Sep 8, 2016

Member

Done, see my sig on the QSB 25.

Member

rootkovska commented Sep 8, 2016

Done, see my sig on the QSB 25.

@rootkovska rootkovska closed this Sep 8, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment