-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[Sorry last should have gone to list only)
Hello Werner,
Sunday, November 29, 2009, 4:52:32 PM, you wrote:
> On Sun, 29 Nov 2009 12:10:35 +, Sean Rima wrote:
>> I am playing with auto-key-locate (as per
>> http:/
On Nov 29, 2009, at 5:13 AM, Werner Dittmann wrote:
All,
to set-up configuration script I use the libgcrypt-config command
to determine parameters about libgcrypt. During tests I get a
confusing result :-) when checking available algorithms:
To check the availabe algorithms I do:
libgcrypt-co
On Sun, 29 Nov 2009 12:10:35 +, Sean Rima wrote:
> I am playing with auto-key-locate (as per
> http://gushi.livejournal.com/524199.html) however this is under
> Vista. Does the Windows port not have pka lookup enabled during the
> build, I see ldap works
Hi!
On Sun, 29 Nov 2009 11:13:01 +0100, Werner Dittmann wrote:
> Message digest algorithms: crc md4 md5 rmd160 sha1 sha256 sha512 tiger
> whirlpool
The names are actually those of the source files.
> Thus is it save to assume if SHA512 is avaliable then SHA384 is also
> available?
Right, SHA3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Gnupg-users,
I am playing with auto-key-locate (as per
http://gushi.livejournal.com/524199.html) however this is under
Vista. Does the Windows port not have pka lookup enabled during the
build, I see lda
All,
to set-up configuration script I use the libgcrypt-config command
to determine parameters about libgcrypt. During tests I get a
confusing result :-) when checking available algorithms:
To check the availabe algorithms I do:
libgcrypt-config --algorithms
Symmetric cipher algorithms: arcfour
