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

Why do I need to create another subkey when GPG creates a default subkey #168

Open
tachang opened this issue Sep 15, 2016 · 2 comments
Open

Comments

@tachang
Copy link

tachang commented Sep 15, 2016

Why do you need to create another subkey when gpg by default creates a subkey? Couldn't you use that subkey and set an empty password?

Is it because that subkey is encryption only and we need a subkey that supports decryption too? But then why select option 6:

Please select what kind of key you want:
(3) DSA (sign only)
(4) RSA (sign only)
(5) Elgamal (encrypt only)
(6) RSA (encrypt only)

For a key that is encrypt only?

@tlimoncelli
Copy link
Contributor

I confess that the reason for this decision was that "it worked". I tried a few other things that didn't work and this was the first one that did work. Maybe I didn't see the default subkey? (I don't know, I didn't keep notes about that).

I'm not a crypto expert, just a GPG user. I'd be glad to change the process if you find something that works better.

@tachang
Copy link
Author

tachang commented Sep 16, 2016

Yeah I just wanted to open up a discussion about it. Maybe someone who uses GPG a lot more and understands the output will chime in.

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