We recently upgraded the server we use to gpg encrypt files with public key encryption.
Old server had gnupg version 1.2.6. On the new server, gnupg version 2.0.18, we imported our gpg keyring from the old server.
On our old server we have a clients public key that encrypts with ELG-E/CAST5 (shown by enabling verbose mode when encrypting files.
On our new server, the same public key uses ELG/CAST5 when encrypting files. gpg --version on the new server also only shows ELG, not ELG-E.
Is there any way to enable ELG-E on our new server? Should we ask for a newer public key from this client?
-bash-3.00$ gpg --version gpg (GnuPG) 1.2.6 Copyright (C) 2004 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Home: ~/.gnupg Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH Hash: MD5, SHA1, RIPEMD160, SHA256 Compression: Uncompressed, ZIP, ZLIB, BZIP2
-bash-4.1$ gpg --version gpg (GnuPG) 2.0.18 libgcrypt 1.4.5 Copyright (C) 2011 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: ~/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2