COMPLETE SUCCESS.
I had to add the *-program argument to both the gpg and gpg-agent
config files. Below is very very crude shell script to show others
how it was done. The script wasn't tested as is, but rather was a
notepad I had open to try to record the steps as I did them. It is
almost guar
You'll need to set the path to pinentry in gpg-agent.conf Something like:
pinentry-program /home/xyz/pinentry-mac.app/Contents/MacOS/pinentry-mac
-Patrick
On 29.08.15 19:13, Dan Bryant wrote:
> OK, this worked in getting the binaries extracted and by setting PATH
> and DYNLD_LIBRARY_PATH I can ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Friday 28 August 2015 at 3:02:44 PM, in
,
Dionysis Zindros wrote:
> You can have multiple public/private key pairs for your
> public identities. Then you can maintain a secret
> public/private key pair that links your identities
> together.
On 22/08/15 17:25, Dongsheng Song wrote:
> Now I want to create my new key like this:
>
> sec rsa4096/93D374EB 2015-08-22 [C]
> uid [ultimate] example
> ssb rsa2048/466D08E1 2015-08-22 [S]
> ssb rsa2048/AD92E667 2015-08-22 [E]
> ssb rsa2048/07DEFA25 2015-08-22 [A]
> ssb ed25519/
> I think it's a good idea to stress you're talking about the block size,
> not about the key size. Something like "a cipher with a 64 bit block size".
Good point; thank you!
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mai
On 27/08/15 23:11, Robert J. Hansen wrote:
> For a 64-bit cipher, you'll probably wind up [...]
> A 128-bit cipher will begin to repeat after [...]
I think it's a good idea to stress you're talking about the block size,
not about the key size. Something like "a cipher with a 64 bit block size".
