RE: Facing issue while installing GnuPG 2.0.27 on AIX 7.1
Additional details on the trail mailkindly look into the same. It errors out even when creating a key : Note - anything that calls gpg-agent gets dumped ( you may want to mention this in your email to support) sdlux09:# ./GnuPG/gnupg-2.0.27/g10/gpg2 --gen-key gpg (GnuPG) 2.0.27; Copyright (C) 2015 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Please select what kind of key you want: (1) RSA and RSA (default) (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) Your selection? 1 RSA keys may be between 1024 and 4096 bits long. What keysize do you want? (2048) 1024 Requested keysize is 1024 bits Please specify how long the key should be valid. 0 = key does not expire n = key expires in n days nw = key expires in n weeks nm = key expires in n months ny = key expires in n years Key is valid for? (0) 1 Key expires at Thu Jul 2 06:43:39 UCT 2015 Is this correct? (y/N) y GnuPG needs to construct a user ID to identify your key. Real name: Jayesh Email address: jayesh.koth...@accenture.commailto:jayesh.koth...@accenture.com Comment: Test You selected this USER-ID: Jayesh (Test) jayesh.koth...@accenture.commailto:jayesh.koth...@accenture.com Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O You need a Passphrase to protect your secret key. ( didn't let met enter anything) gpg: signal 11 caught ... exiting Segmentation fault [cid:image001.png@01D0B3FC.0A9A9DE0] From: Navin Mehta, Manan Sent: Wednesday, July 01, 2015 11:31 AM To: 'Werner Koch'; 'gnupg-users@gnupg.org'; 'gnupg-de...@gnupg.org' Cc: DiEnno, Michael F.; Dawane, Shailendra S.; Sharma, Pramod; Zingade, Swati; Karmakar, Sanjiv; Kothari, Jayesh Subject: RE: Facing issue while installing GnuPG 2.0.27 on AIX 7.1 Hi Werner/GnuPG Team, Greetings..!! Need your expert advice/suggestions..!! After upgrading the Compiler and having all the required Lib files, it seems that GnuPG has been installed, PFB excerpt from the log which we got after triggering below command: Also, PFA config.log which automatically gets generated and GnuPG_log which has logs copied from screen after running below command. Request you to look into it and check whether GnuPG has been installed correctly or not and kindly also let us know if any post steps are required.. Command used: ./configure; make; make install GnuPG v2.0.27 has been configured as follows: Revision: 8d47e6e (36167) Platform: AIX (powerpc-ibm-aix7.1.2.0) OpenPGP: yes S/MIME:yes Agent: yes Smartcard: yes (without internal CCID driver) Gpgtar:no Protect tool: (default) Default agent: (default) Default pinentry: (default) Default scdaemon: (default) Default dirmngr: (default) Warning: Mismatches between the target platform and the to be used libraries have been detected for: libgpg-error libgcrypt Please check above for more warning messages. make all-recursive Making all in m4 Target all is up to date. Thanks a lot in advance :) [cid:image001.png@01D0B3FC.0A9A9DE0] From: Navin Mehta, Manan Sent: Friday, June 05, 2015 3:16 PM To: 'Werner Koch' Cc: gnupg-users@gnupg.orgmailto:gnupg-users@gnupg.org; gnupg-de...@gnupg.orgmailto:gnupg-de...@gnupg.org; DiEnno, Michael F.; Dawane, Shailendra S.; Sharma, Pramod; Zingade, Swati; Karmakar, Sanjiv; Kothari, Jayesh Subject: RE: Facing issue while installing GnuPG 2.0.27 on AIX 7.1 Hi Werner, Thanks for your reply. Sure, we will check with our Unix team for the availability of the C compiler and get it installed. Request you to address one more query: ? As you have mentioned in the trail mail that You need to have a compiler and all related tools (the toolchain) to build software , can you please give more details on toolchain ? What all other tools will be required (other than installing C compiler) for successful installation of GnuPG software. Thanks again :) Thanks, Manan N Mehta Accenture | SAP BASIS Admin Email: manan.navin.me...@accenture.commailto:manan.navin.me...@accenture.com -Original Message- From: Werner Koch [mailto:w...@gnupg.org] Sent: Friday, June 05, 2015 2:03 PM To: Navin Mehta, Manan Cc: gnupg-users@gnupg.orgmailto:gnupg-users@gnupg.org; gnupg-de...@gnupg.orgmailto:gnupg-de...@gnupg.org; DiEnno, Michael F.; Dawane, Shailendra S.; Sharma, Pramod; Zingade, Swati; Karmakar, Sanjiv Subject: Re: Facing issue while installing GnuPG 2.0.27 on AIX 7.1 On Thu, 4 Jun 2015 09:04, manan.navin.me...@accenture.commailto:manan.navin.me...@accenture.com said: Below are the OS level details: [cid:image006.png@01D09EBE.3BD6EBA0] Sorry, I can't view the images as they are only available in the HTML rendered version.
Secure Private Key Synchronization (RFC)
Hi, I'm Tankred from Whiteout (https://whiteout.io). Me, Werner and other PGP projects discussed a secure way to synchronize a user's private key between devices during the OpenPGP summit in April (https://www.gnupg.org/blog/20150426-openpgp-summit.html). The goal was to formalize and hopefully standardize a very simple protocol that allows interoperability between mail user agents. We've already gotten feedback from other vendors using OpenPGP.js such as Mailvelope and 11, and we would also like to hear what the GPG community has to say about it. Here is our current proposal: https://github.com/whiteout-io/mail-html5/wiki/Secure-OpenPGP-Key-Pair-Synchronization-via-IMAP Thanks for any feedback! Kind regards, Tankred -- Whiteout Networks GmbH c/o Werk1 Grafinger Str. 6 D-81671 München Geschäftsführer: Oliver Gajek RG München HRB 204479 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: [Announce] GnuPG 2.1.6 released
Hi, At least with gpg2 2.1.4-1 and gpgme 1.5.5-2 the passphrase callback does not work. When enabled I get the secret key unusable error, and without the callback (enter passphrase via agent) it works fine. If I remember correctly you stated that you need gpg2 v2.1 or better for that to work: https://lists.gnupg.org/pipermail/gnupg-devel/2015-May/029872.html On Wed, Jul 01, 2015 at 03:19:19PM +0200, Werner Koch wrote: Hello! The GnuPG Project is pleased to announce the availability of a new release of GnuPG modern: Version 2.1.6. The GNU Privacy Guard (GnuPG) is a complete and free implementation of the OpenPGP standard which is commonly abbreviated as PGP. GnuPG allows to encrypt and sign data and communication, features a versatile key management system as well as access modules for public key directories. GnuPG itself is a command line tool with features for easy integration with other applications. A wealth of frontend applications and libraries making use of GnuPG are available. Since version 2 GnuPG provides support for S/MIME and Secure Shell in addition to OpenPGP. GnuPG is Free Software (meaning that it respects your freedom). It can be freely used, modified and distributed under the terms of the GNU General Public License. Three different branches of GnuPG are actively maintained: - GnuPG modern (2.1) is the latest development with a lot of new features. This announcement is about this branch. - GnuPG stable (2.0) is the current stable version for general use. This is what most users are currently using. - GnuPG classic (1.4) is the old standalone version which is most suitable for older or embedded platforms. You may not install modern (2.1) and stable (2.0) at the same time. However, it is possible to install classic (1.4) along with any of the other versions. Noteworthy changes in version 2.1.6 === * agent: New option --verify for the PASSWD command. * gpgsm: Add command option offline as an alternative to --disable-dirmngr. * gpg: Do not prompt multiple times for a password in pinentry loopback mode. * Allow the use of debug category names with --debug. * Using gpg-agent and gpg/gpgsm with different locales will now show the correct translations in Pinentry. * gpg: Improve speed of --list-sigs and --check-sigs. * gpg: Make --list-options show-sig-subpackets work again. * gpg: Fix an export problem for old keyrings with PGP-2 keys. * scd: Support PIN-pads on more readers. * dirmngr: Properly cleanup zombie LDAP helper processes and avoid hangs on dirmngr shutdown. * Various other bug fixes. A detailed description of the changes found in the 2.1 branch can be found at https://gnupg.org/faq/whats-new-in-2.1.html. Please be aware that there are still known bugs which we are working on. Check https://bugs.gnupg.org, https://wiki.gnupg.org, and the mailing list archives for known problems and workarounds. Getting the Software Please follow the instructions found at https://gnupg.org/download/ or read on: GnuPG 2.1.6 may be downloaded from one of the GnuPG mirror sites or direct from its primary FTP server. The list of mirrors can be found at https://gnupg.org/mirrors.html. Note that GnuPG is not available at ftp.gnu.org. On ftp.gnupg.org you find these files: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.6.tar.bz2 (4802k) ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.6.tar.bz2.sig This is the GnuPG source code compressed using BZIP2 and its OpenPGP signature. ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.6_20150701.exe (2577k) ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.6_20150701.exe.sig This is an installer for Windows without graphical frontends except for a basic Pinentry tool. Please de-install an installed Gpg4win version before trying this installer. Note that on Window TLS access to keyservers is not yet available. The sources used to build the installer can be found in the same directory with an .tar.xz suffix. Checking the Integrity == In order to check that the version of GnuPG which you are going to install is an original and unmodified one, you can do it in one of the following ways: * If you already have a version of GnuPG installed, you can simply verify the supplied signature. For example to verify the signature of the file gnupg-2.1.6.tar.bz2 you would use this command: gpg --verify gnupg-2.1.6.tar.bz2.sig gnupg-2.1.6.tar.bz2 This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by one or more of the release signing keys. Make sure that this is a valid key, either by matching the shown fingerprint against a trustworthy list of valid release signing keys or by checking that the key has been
Re: Secure Private Key Synchronization (RFC)
Will the proposal require support private subkey stubs generated from gpg --export-secret-subkeys? Daniel On Thu, Jul 2, 2015 at 6:48 AM, Tankred Hase tank...@whiteout.io wrote: Hi, I'm Tankred from Whiteout (https://whiteout.io). Me, Werner and other PGP projects discussed a secure way to synchronize a user's private key between devices during the OpenPGP summit in April (https://www.gnupg.org/blog/20150426-openpgp-summit.html). The goal was to formalize and hopefully standardize a very simple protocol that allows interoperability between mail user agents. We've already gotten feedback from other vendors using OpenPGP.js such as Mailvelope and 11, and we would also like to hear what the GPG community has to say about it. Here is our current proposal: https://github.com/whiteout-io/mail-html5/wiki/Secure-OpenPGP-Key-Pair-Synchronization-via-IMAP Thanks for any feedback! Kind regards, Tankred -- Whiteout Networks GmbH c/o Werk1 Grafinger Str. 6 D-81671 München Geschäftsführer: Oliver Gajek RG München HRB 204479 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: [Announce] Pinentry 0.9.5 released
On Wed 2015-07-01 19:27:23 -0400, Rex Kneisley wrote: I have been experimenting with installing GnuPG from scratch and also by using the Debian packages. is the purpose of these experiments to build skills with software compilation or other system management? Now I want to install pinentry-0.9.5. one approach is to wait a couple days for one of us to get around to packaging it for debian :) In the past I downloaded all of the tar-balls (GnuPG, Libgpg-error, Libgcrypt, etc) to a folder in my home directory which I named Software I then unpacked them, cd'ed in to each directory and then ran ./configure, make, make install) I'm older and wiser now. Should I unpack the Pinentry-0.9.5.tar.bz2 in to the /usr/local folder and then perform the ./configure,make,make install steps? there should be no reason to do the build in /usr/local explictly. How would I put the libraries in /usr/local/lib and the headers in /usr/local/include? Do they go there automatically when I run the installation? (naive assumption) by default, pinentry doesn't install any shared libraries or development headers at all. --dkg ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpa and gpgex in gpg 2.1.x releases for windows.
As a gpg user, I've been using the gpg 2.1.x releases for a while. as of 2.1.1, gpg for windows included gpa and gpgex. I used them. newer releases didn't remove these features, but didn't upgrade or include them either. Now it's difficult if not impossible to install gpa and gpgex with gnupg 2.1.x series. Can we get these nearly essential features added back into the 2.1.x releases going forward please? If not, can we have them made into an add-on package so that downloading them is easy? Even if they're not fully or properly supported, the existing functionality like clipboard, and basic key use are quite important for day to day use of gpg on windows. Not everybody uses a dedicated e-mail client, or cares to install one. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
