Re: Using gpg-groups in gnome?
Ingo Klöcker schrieb: On Thursday 27 August 2009, debianfeed wrote: Hello does anybody here know a possibility to use gpg key-groups under gnome? groups defined in the gpg.conf (e.g. group mygroupname = 0x9DB0 0x9540) do not show up in nautilus' seahorse extension. kgpg is capable of dealing with groups, but as it is a KDE-application it ist not usable via the nautilus context menu. I doubt very much that kgpg cannot be added to the Nautilus context menu. I'm pretty sure any application can be added to the Nautilus context menu. Thanks Ingo. Yes, you can use nautilus-actions or nautilus-scripts for kgpg, but in reality used this way kgpg crashes five times a day, forgets its settings like use untrusted keys and so on. That is not acceptable in a productive enviroment with 80+ Users. I hoped someone would have an idea about a more stable solution. Mark ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Signing with a key on a smart card
Hello, anyone that could explain me how gpg chooses which secret key to use or how I could tell gpg which one to use ? Or maybe a way I can tell gpg not to use the smart card while on a certain computer. I still don't get why it doesn't manage to use the proper secret key and google is definitely not my friend. Thanks Le mardi 04 août 2009 à 22:01, Jérôme Blanc jerome.bl...@nerim.net a écrit : Hello, I'm currently toying with an OpenPGP smart card, but I meet some difficulties getting how this works. I have the Smart Card properly set up (at least I do think so ;-)) : [gem...@gemini ~]$ gpg --card-status gpg: detected reader `Gemplus GemPC Twin 00 00' […] Signature key : 5898 DBEA 1139 733B ACFD 7880 E8B6 F7C5 2B20 7AEF created : 2009-08-02 11:34:17 Encryption key: A52C FAAC D39F 252D A2C4 0149 2B0F 7310 7C9E D800 created : 2009-08-02 11:37:25 Authentication key: D179 47D8 3B01 87A3 3C86 1AB0 2E8D 6DE6 F8D5 6EFC created : 2009-08-04 19:22:04 In the keyring, I have 3 private master keys, for handling 3 different identities. In the gpg.conf, the default key is the master key that generated the subkeys that are on the smart card. I can cipher and decipher using the keys on the smart card. However, when I try to sign a file, then I have the following : [gem...@gemini ~]$ gpg --sign -u 2B207AEF test.txt Le fichier `test.txt.gpg' existe. Réécrire par-dessus ? (o/N) gpg: detected reader `Gemplus GemPC Twin 00 00' gpg: la signature a échoué: mauvaise clé secrète utilisée gpg: signing failed: mauvaise clé secrète utilisée which means = signing failed: wrong secret key used Signing works with the two other master keys. As well, using the same card on another computer works, with an empty gpg keyring but the public keys related to it. Does this mean I have no other choice but to remove master keys of that identity in order to be able to use the card with my computer ? Thanks ! Regards, -- Jérôme Blanc OpenPGP : 1024D/F44DB96C signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Signing with a key on a smart card
On Wed, 2 Sep 2009 10:55, jerome.bl...@nerim.net said: anyone that could explain me how gpg chooses which secret key to use or how I could tell gpg which one to use ? Without an option, gpg uses the first available secret key for signing. This is usually not desired, thus you can use default-key in gpg.conf to select a different one. If you want to use another than the default key, you may give it on the command line with -u USERID. You may even give several -u options to sign the data with several keys. An OpenPGP keys consists of a primary key and optionally several subkeys. Gpg uses the latest subkey capable of signing to create a signature, if no such subkey is available, the primary key is used. This happens even if you speicify the keyid of a subkey. If you want to force the use of a specific signing subkey, you need use the ! suffix to the keyid. Example: pub 1024D/5B0358A2 created: 1999-03-15 expires: 2011-07-11 usage: SC sub 2048R/B604F148 created: 2004-03-21 expired: 2005-12-31 usage: E sub 2048R/C3680A6E created: 2006-01-01 expired: 2007-12-31 usage: E sub 1024D/3D52C282 created: 2007-12-31 expires: 2010-07-11 usage: S sub 2048R/F409CD54 created: 2007-12-31 expires: 2011-07-10 usage: E sub 2048R/12345678 created: 2009-06-30 expires: 2010-07-10 usage: S Using: -u 0x5B0358A2 == Subkey 0x12345678 is used. -u 0x12345678 == Subkey 0x12345678 is used. -u 0x3D52C282 == Subkey 0x12345678 is used. -u 0x3D52C282! == Subkey 0x3D52C282 is used. Due to the key expiration, this will chnage in one year to: -u 0x5B0358A2 == Primary key 0x5B0358A2 is used. -u 0x12345678 == Primary key 0x5B0358A2 is used. -u 0x3D52C282 == Primary key 0x5B0358A2 is used. -u 0x3D52C282! == Primary key 0x5B0358A2 is used. Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 1.4.10rc1 vs. OS X 10.6
I tried compiling 1.4.10rc1 on Mac OS X 10.6 without success. I can recreate this bug on 1.4.9 and 1.4.10rc1 on a MacBook Pro running Snow Leopard. I can also confirm that John's fix of passing --disable-asm to the configure script works. Can we get an #ifdef for Darwin to replace the ASM blocks with compiled code? Happy compiling! ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 1.4.7 packages for OS X
Robert J. Hansen wrote the following on 3/6/07 10:06 AM: I've taken the liberty of packaging up 1.4.7 for OS X. (I apologize to Benjamin if I'm stepping on his toes here; by my recollection, he's doing packages for 2.0.x, not 1.4.x, so I _should_ be safe.) I believe you are. Using the recent release of 1.4.9, I have just compiled from source 1.4.9 with IDEA for MacOSX 10.5.8.(straightforward in Terminal). I guess that when I upgrade to 10.6 (a couple of weeks from now), I may be in from some surprises, according to what I have read in this list. So far, so good. Thank you Robert. Charly $ gpg --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: ~/.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 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 1.4.7 packages for OS X
Charly Avital wrote the following on 9/2/09 9:14 AM: Robert J. Hansen wrote the following on 3/6/07 10:06 AM: I've taken the liberty of packaging up 1.4.7 for OS X. (I apologize to Benjamin if I'm stepping on his toes here; by my recollection, he's doing packages for 2.0.x, not 1.4.x, so I _should_ be safe.) I apologize to the list, to Robert and to Benjamin. I just picked up an old post, and reacted knee-jerk (emphasis on jerk - yours truly). I'll be back to 1.4.10RC1. Sorry again. Charly ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 1.4.10rc1 vs. OS X 10.6
On Sep 2, 2009, at 12:47 AM, Joseph Oreste Bruni wrote: I tried compiling 1.4.10rc1 on Mac OS X 10.6 without success. 10.6 ships with a newer version of the compiler toolchain that is giving a few headaches here and there. Until we work out the issue, just compile with --disable-asm. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Secret Key replacement
On Sep 1, 2009, at 1:51 PM, Seidl, Scott wrote: We use gnupg in an automated mode within the organization to encrypt/ decrypt documents exchanged between companies. The Key Pair we have is expiring soon and I am replacing it with a new key pair. This new key would be provided to the other companies before the other expires. I have a couple questions about the existing public keys we have imported to our key ring. 1 – it’s my belief that I have to sign/trust each of the keys with the new secret key, is that correct? It depends. Many uses of GPG in an automated mode use --trust-model always or --always-trust, since there is no need for a web of trust in their setup. If you are using one of those options, then there is no need to sign anything. If you are not using one of those options, you probably need to make some signatures. 2 – Is there any command to do a mass sign or must I do a gpg –u XXX --edit-key YY for each key? No mass sign ability, but you can do some shell magic like: for i in (the keyids here) do gpg -u XX --lsign $i done This assumes you don't have a passphrase on the key (otherwise you'd have to type it multiple times as the shell loop ran), but no passphrases is also a common setup for automated use. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Secret Key replacement
On Wednesday, September 02, 2009, at 08:18AM, David Shaw ds...@jabberwocky.com wrote: No mass sign ability, but you can do some shell magic like: for i in (the keyids here) do gpg -u XX --lsign $i done This assumes you don't have a passphrase on the key (otherwise you'd have to type it multiple times as the shell loop ran), but no passphrases is also a common setup for automated use. David To expand on David's script, the portion found in '(the keyids here)' can be extracted using the following: $ gpg --with-colons --list-keys | grep -e '^pub' | cut -d: -f5 -Joe ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
[Announce] GnuPG 1.4.10 released
Hello! We are pleased to announce the availability of a new stable GnuPG-1 release: Version 1.4.10. The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication and data storage. It is a complete and free replacement of PGP and can be used to encrypt data and to create digital signatures. It includes an advanced key management facility, samrtcard support and is compliant with the OpenPGP Internet standard as described by RFC-4880 (the update of RFC-2440). Note that this version is from the GnuPG-1 series and thus smaller than those from the GnuPG-2 series, easier to build and also better portable. In contrast to GnuPG-2 (e.g version 2.0.12) it comes with no support for S/MIME or other tools useful for desktop environments. Fortunately you may install both versions alongside on the same system without any conflict. Getting the Software Please follow the instructions found at http://www.gnupg.org/download/ or read on: GnuPG 1.4.10 may be downloaded from one of the GnuPG mirror sites or direct from ftp://ftp.gnupg.org/gcrypt/ . The list of mirrors can be found at http://www.gnupg.org/mirrors.html . Note, that GnuPG is not available at ftp.gnu.org. On the mirrors you should find the following files in the *gnupg* directory: gnupg-1.4.10.tar.bz2 (3331k) gnupg-1.4.10.tar.bz2.sig GnuPG source compressed using BZIP2 and OpenPGP signature. gnupg-1.4.10.tar.gz (4636k) gnupg-1.4.10.tar.gz.sig GnuPG source compressed using GZIP and OpenPGP signature. gnupg-1.4.9-1.4.10.diff.bz2 (189k) A patch file to upgrade a 1.4.9 GnuPG source. Select one of them. To shorten the download time, you probably want to get the BZIP2 compressed file. Please try another mirror if exceptional your mirror is not yet up to date. In the *binary* directory, you should find these files: gnupg-w32cli-1.4.10.exe (1531k) gnupg-w32cli-1.4.10.exe.sig GnuPG compiled for Microsoft Windows and OpenPGP signature. This is a command line only version; the source files are the same as given above. Note, that this is a minimal installer and unless you are just in need for the gpg binary, you are better off using the full featured installer at http://www.gpg4win.org . 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 trusted version of GnuPG installed, you can simply check the supplied signature. For example to check the signature of the file gnupg-1.4.10.tar.bz2 you would use this command: gpg --verify gnupg-1.4.10.tar.bz2.sig This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by that signing key. Make sure that you have the right key, either by checking the fingerprint of that key with other sources or by checking that the key has been signed by a trustworthy other key. Note, that you can retrieve the signing key using the command finger wk ,at' g10code.com or using a keyserver like gpg --recv-key 1CE0C630 The distribution key 1CE0C630 is signed by the well known key 5B0358A2. If you get an key expired message, you should retrieve a fresh copy as the expiration date might have been prolonged. NEVER USE A GNUPG VERSION YOU JUST DOWNLOADED TO CHECK THE INTEGRITY OF THE SOURCE - USE AN EXISTING GNUPG INSTALLATION! * If you are not able to use an old version of GnuPG, you have to verify the SHA-1 checksum. Assuming you downloaded the file gnupg-1.4.10.tar.bz2, you would run the sha1sum command like this: sha1sum gnupg-1.4.10.tar.bz2 and check that the output matches the second line from the following list: fd1b6a5f3b2dd836b598a1123ac257b8f105615d gnupg-1.4.10.tar.bz2 0db579b2dc202213424f55243906b71228dd18d1 gnupg-1.4.10.tar.gz 4a6b9f8b15d9849307a90f2b35bde8fd2d111331 gnupg-1.4.9-1.4.10.diff.bz2 c4383992b4815311e523d2f12684d47b7a552fca gnupg-w32cli-1.4.10.exe What's New === * 2048 bit RSA keys are now generated by default. The default hash algorithm preferences has changed to prefer SHA-256 over SHA-1. 2048 bit DSA keys are now generated to use a 256 bit hash algorithm * Support v2 OpenPGP cards. * The algorithm to compute the SIG_ID status has been changed to match the one from 2.0.10. * Improved file locking. Implemented it for W32. * Fixed a memory leak which made imports of many keys very slow. * Many smaller bug fixes. * Support for the Camellia cipher (RFC-5581). * Support for HKP keyservers over SSL (HKPS). Internationalization GnuPG comes with support for 28 languages. Due to a lot of new and changed strings some translations are not entirely complete. The Chinese (Simple and
Re: 1.4.10rc1 and v2 OpenPGP cards/3072 bit keys
On Sun, 30 Aug 2009 18:07, ds...@gefira.pl said: However, I cannot decrypt a message encrypted with a 3072b key, also generated on-card. I'm 100% sure I'm entering a correct PIN but still I can confirm that. It seems there are actually two problems: One bug in gpg and afaics a bug in the card. I track the problem at https://bugs.g10code.com/gnupg/issue1114 Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 1.4.10rc1 vs. OS X 10.6
2009/9/2 Robert J. Hansen r...@sixdemonbag.org: Can we get an #ifdef for Darwin to replace the ASM blocks with compiled code? I tested it as part of my Universal Binary build, and the ASM blocks make little difference with fast processors. Ben ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Install GnuPG 2.0.12 on AIX 5.3 Maintenance (Technology) Level 3
I am boldly trying to get GnuPG 2.0.12 installed, even though I don't really need S/MIME or desktop support. So while this request for help festers a bit, I will download the 1.4 version and see if I can get that to go. When I configure GnuPG 2.0.12, it tells me that linassuan-1.0.4 (minimum) nor Pth are installed. I initially tried libassuan 1.0.5, but it gave me several problems, so I went back to 1.0.4. GnuPG wants libassuan-1.0.4 (API 1), but I can only find 1 version of 1.0.4, so I presume that is API 1. I had issues installing Pth-2.0.7, arising from fdsetsize, but I worked around that with the help of the Pth users (Ken, specifically) by doing the configure with -with-fdsetsize=1024. Both libassuan-1.0.4 and pth-2.0.7 did install into /usr/local/lib, in the end, with no errors. Does anyone have any hints what options I may need to change on my configure, or other advice? ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
GnuPG-1.4.9 Install on AIX 5.3 Maintenance (Technology) Level 3
After doing a CFLAGS=-g -02 -mcpu=powerpc ./configure, the following is reported: configure: WARNING: pthread.h: present but cannot be compiled configure: WARNING: pthread.h: check for missing prerequisite headers? configure: WARNING: pthread.h: see the Autoconf documentation configure: WARNING: pthread.h: section Present But Cannot Be Compiled configure: WARNING: pthread.h: proceeding with the preprocessor's result configure: WARNING: pthread.h: in the future, the compiler will take precedence configure: WARNING: ## ## configure: WARNING: ## Report this to bug-gn...@gnu.org ## configure: WARNING: ## ## Has anyone seen this before and have a workaround? ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GnuPG-1.4.9 Install on AIX 5.3 Maintenance (Technology) Level 3
2009/9/2 Bob Wyatt bwyatt_...@comcast.net: After doing a CFLAGS=”-g -02 –mcpu=powerpc” ./configure, the following is reported: I think you mentioned that pthreads was installed under /usr/local/ try: ./configure --with-pth-prefix=/usr/local/ For further options, take a look at ./configure --help Ben ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 1.4.7 packages for OS X
Charly Avital wrote: Thank you Robert. I did builds for only a very brief period of time: once he got 1.4.7 packages built, I stopped. He does a great job with MacGPG, and I've got no desire to duplicate work that's already being done well. Thanks, Benjamin, for all your work. The Mac users really appreciate it. :) ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
