On GPG4WIN .. only GPG 2.0 btw ... gpg --version ...
gpg (GnuPG) 2.0.30 (Gpg4win 2.3.1) libgcrypt 1.6.5 Copyright (C) 2015 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: C:/Users/andrewm/AppData/Roaming/gnupg Supported algorithms: Pubkey: RSA, RSA, RSA, ELG, 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, BZIP2 Is this good? ... gpg.conf ... ###+++--- GPGConf ---+++### utf8-strings keyserver-options http-proxy=http://192.168.0.201:8118 keyserver hkp://keys.gnupg.net auto-key-locate local debug-level 0 ###+++--- GPGConf ---+++### 06/13/15 16:52:09 AUS Eastern Standard Time # GPGConf edited this configuration file. # It will disable options before this marked block, but it will # never change anything below these lines. default-key B7EFE2FB # Default cipher is CAST5-128, AES256 is much better cipher-algo AES256 # This forces "the use of encryption with a modification detection code". force-mdc # /extra/ torproject suggestions #utf8-strings -- already have this by default no-emit-version no-comments throw-keyids I know the main key I'm using on mailing lists is just 2048 RSA bits; not real concerned about that. Besides, it sort of gives an opportunity to use the argument that it is weak so it is deniable; not that I think I have any reason to have to use that arguement. Cheers AndrewM
signature.asc
Description: OpenPGP digital signature
_______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
