search

lachesis / scallion

GPU-based Onion Hash generator
Other
1.25k stars 164 forks source link

Why doesn't certificate show 4096/4096 like other ones? (Scallion GPG import process example) #100

Open htpasswd opened 7 years ago

htpasswd commented 7 years ago

Hello. I created a GPG key using this command from Windows: C:\scallion-v2.0\scallion.exe -o c:\gpgkeys.txt -k 4096 --gpg beef$ Then, on Linux, created key.asc and copied there all text from inside <PrivateKey>...copied this...</PrivateKey> tags. Then imported it into GPG with this command: gpg2 --import --allow-non-selfsigned-uid key.asc Then changed UID this way: gpg2 --edit-key replace me adduid name...email...comment...O 1 deluid passwd trust 5 save Then created subkey: gpg2 --edit-key F1D9BEEF ... addkey ... RSA ...

But, if I manage my keys using KGpg, it shows the next picture: 2 Certificates that I create using gpg2 --full-gen-key, show "4096/4096", any other certificates show the same "4096/4096". Why do Scallion certificates show other parameters? Is this a sign of weakness?

lachesis commented 7 years ago

I don't know - what does the second number mean in KGpg? I was originally going to guess it had something to do with the missing self-signed UID or subkeys, but those look alright as far as I can tell from your screenshot.