BZIP2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 What is the reason for the Windows build of 1.4.10 (both the pulled and fixed binaries) not supporting BZIP2? D:\Testgpg --version gpg (GnuPG) 1.4.9 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: d:/Profiler/GnuPG Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2 D:\Testgpg --version gpg (GnuPG) 1.4.10 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: d:/Profiler/GnuPG Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB D:\Test - -- $\hbar$ -- http://www.facebook.com/barkmanstein -- OpenPGP 0x60D02095 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iGUEAREKACUFAkqhaKYeGGhrcDovL3Bvb2wuc2tzLWtleXNlcnZlcnMubmV0AAoJ EEGwNGJg0CCVx3IAoKGn/M2Iugy6iGfjTslHy84BuL2BAJwP7zNobY4lGZya2pqK QXKv6F0ptw== =TxU6 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Key updating and preferred keyservers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a way to run refresh-keys WITHOUT honoring preferred keyserver records? Every now and then I need to update an entire keyring from one specific keyserver, and since some of the keys involved has preferred keyserver records it usually turns into running refresh-keys followed by locating the un-updated key ID's in the scrollback, and then run recv-keys for those keys. Something like gpg --keyserver company.keyserver --refresh-keys - --no-preferred-keyserver would make this procedure much easier. - -- $\hbar$ -- http://skenbe.net/h-bar/ -- OpenPGP key ID 0x60D02095 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3rc2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEKZYVQbA0YmDQIJURAgLsAJ9yYJN6h7CDfKESZ2gq+fkgA18w2wCgl7n/ b3zitJlsrzCxo3e3LMrxTks= =5HZT -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: PGP global directory cruft in keyservers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To my knowledge, the PGP GD doesn't sync with anyone. It would be interesting to know how/where these signatures are leaking into the keyserver net. Probably some PGP users who are automagically synchronising their entire keyrings with multiple keyservers, leaking keys that their owners would rather not have on the keyservers in the process :( That would have to be very zealous users, since I once found PGP GD signatures on one of my keys when I checked it on the SKS network. At the time, that key was known only by me, the SKS servers and the PGP GD. What users would download keys at random? - -- $\hbar$ -- http://skenbe.net/h-bar/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDHwWtQbA0YmDQIJURAr/1AKDMRnrldVIXflsE0V49HB6KQDUeIwCfWcyp jKE0IuwyLm9ma58R0OmDxWM= =SRF3 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
