Explicitly pass usage flags during key creation
Reported by Support | September 15th, 2013 @ 12:00 AM
Assigned to Everything #11432. If the usage flags for a key are not passed explicitly to gnupg on key creation, it will enable all possible usages based on the key type, which makes for potentially less secure keys.
We should pass the default usages:
- Primary key: Signing and certification (sc) - Subkey: Encrpytion
only (e)
Comments and changes to this ticket
-
Support September 15th, 2013 @ 12:15 AM
- State changed from “new” to “started”
(from [83f4692dbcde9f07a5a287662dcb2d39e90dc9a4]) Pass sign as key usage for primary key and encrypt as key usage for the subkey if RSA/RSA is selected. [#56 state:started] https://github.com/GPGTools/Libmacgpg/commit/83f4692dbcde9f07a5a287...
-
Support September 15th, 2013 @ 04:04 AM
- State changed from “started” to “fixed”
(from [ec4ca058045b71c87acb3cdcb6b12e37b320f5a3]) By default, key usages are set as defined by the gnupg command line. [#56 state:fixed] https://github.com/GPGTools/Libmacgpg/commit/ec4ca058045b71c87acb3c...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Luke Le
Mento
steve
Support