Contents
Is the default key in PGP always encrypted?
With the PGP 5.x and higher versions, it is the default setting to also encrypt to the default key. You can change this under PGP options / General / Always encrypt to default key.
Why does PGP abort after generating a key?
It will not create the directory if needed, so if the directory’s not there already, PGP will abort after generating the key. This also happens if PGPPATH points to a directory for which you don’t have write permission.
How can I generate PGP key for export?
As a company administrator, you can now generate PGP keys used in scheduled Import jobs by using Security Center. Note* PGP keys for Export Jobs are still configured in Provisioning. You can export or remove the newly generated keys and the PGP keys previously generated through Provisioning in Security Center.
Why do I need Two public key rings for PGP?
PGP may have to search through several thousand keys to find the one that it is after. If you need to have these large keyrings (e.g. because you cannot count on being able to contact the keyservers to look up new keys), the solution to this dilemma is to maintain 2 public key rings (See How do I create a secondary key file?
Can a PGP key be used as an SSH key?
I use a 4096 byte RSA PGP key; since SSH also uses the RSA standard, is it at all possible to use the PGP key as an SSH key without installing additional software on the server (and as little as possible on the client)? There are several ways, which may or may not work:
Is the passphrase for the SSH key valid?
The passphrase is not just a key to unlock private SSH key, but a part of encryption mechanism. One part is your SSH key, other – the passphrase entered manually. Only if both parts are correct the composite key generated from them on the fly will be valid.
Is it good to have a PGP passphrase?
PGP is a very valuable tool to encrypt your communications, but it comes with the never ending hassle of key management. I have now four takeaways for the next time:
Why is my passphrase not working in GnuPG 2.1?
This means that with GnuPG 2.1 adding –passphrase on the command line will no longer work out of the box. If you really don’t want a passphrase (you have it in a script or the command line history anyway) It is suggested to remove the passphrase from that key.
Why is GnuPG not always set to the correct users Directory?
When launched from the Task Scheduler %APPDATA% is not always set to the correct users directory. (If you launch it with system privileges it is another place altogether). GnuPG as a result is unable to find the Keys or configuration in the directory Windows provides. This is a known Windows bug.
Why does GnuPG try to lock the memory?
GnuPG tries to lock memory so that no other process can see it and so that the memory will not be written to swap. If for some reason it’s not able to do this (for instance, certain platforms don’t support this kind of memory locking), GnuPG will warn you that it’s using insecure memory.