Re: Beta for 2.1.1 available

2014-12-11 Thread Hugo Hinterberger
Hi MFPA, Hi, I am still trying to find a working solution It is more likely you will find help if you start your own thread, with a subject like that matches what you are talking about. I am currently not actively trying to get a working environment. I am exploring the current state of affa

Re: Beta for 2.1.1 available

2014-12-11 Thread Hugo Hinterberger
Hi Johan, The default encoding of my messages should be UTF-8, the message format is set to MIME with no special text encoding (neither quoted printable nor base64), and I allow 8-bit characters in headers. I think we have the culprit. If you do things like that, your "text" will probably be s

Re: Beta for 2.1.1 available

2014-12-10 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wednesday 10 December 2014 at 8:57:30 AM, in , Hugo Hinterberger wrote: > Hi, > I am still trying to find a working solution It is more likely you will find help if you start your own thread, with a subject like that matches what you are tal

Re: Beta for 2.1.1 available

2014-12-10 Thread Johan Wevers
On 10-12-2014 9:57, Hugo Hinterberger wrote: In anorther post you write: > The default encoding of my messages should be UTF-8, the message > format is set to MIME with no special text encoding (neither quoted > printable nor base64), and I allow 8-bit characters in headers. I think we have the

Re: Beta for 2.1.1 available

2014-12-10 Thread Hugo Hinterberger
Hi, I am still trying to find a working solution to verify incoming files and messages with GnuPG on Windows … and I want the solution to be able to handle PGP/MIME messages read through Gmane using elliptic curve based keys. I just have started to try signing messages. A misunderstanding o

Re: Beta for 2.1.1 available

2014-12-09 Thread Johan Wevers
On 09-12-2014 10:02, Hugo Hinterberger wrote: > I just tried the Clipboard - Sign feature in GPA and noticed that when I > copy the signed message to the clipboard that an empty line is inserted > after each line generated for the signature, but not for the original > message or modified lines (es

Re: Beta for 2.1.1 available

2014-12-09 Thread Hugo Hinterberger
On Tue, 09 Dec 2014 10:02:48 +0100, Hugo Hinterberger wrote: Hi, On Mon, 24 Nov 2014 09:24:28 +0100, Werner Koch wrote: Bug reports please to the gnupg-users. I just tried the Clipboard - Sign feature in GPA and noticed that when I copy the signed message to the clipboard that an empt

Re: Beta for 2.1.1 available

2014-12-09 Thread Hugo Hinterberger
Hi, On Mon, 24 Nov 2014 09:24:28 +0100, Werner Koch wrote: Bug reports please to the gnupg-users. I just tried the Clipboard - Sign feature in GPA and noticed that when I copy the signed message to the clipboard that an empty line is inserted after each line generated for the signature,

Re: Beta for 2.1.1 available

2014-11-26 Thread Hugo Hinterberger
Hi, On Mon, 24 Nov 2014 09:24:28 +0100, Werner Koch wrote: Bug reports please to the gnupg-users. While executing a gpgsm --list-keys i noticed the following: fingerprint: 9C:E2:38:44:6A:8E:gpgsm: conversion from 'utf-8' to 'CP850' failed: Illegal byte sequence 4A:63:18:93:7C:41:62:7B:

Re: Beta for 2.1.1 available

2014-11-25 Thread Hugo Hinterberger
Hello Werner, On Mon, 24 Nov 2014 09:24:28 +0100, Werner Koch wrote: Bug reports please to the gnupg-users. When I try to open the Card Manager in GPA the program freezes. according to Process Manager there is something (not much, almost nothing) going on, but the UI does not respond any

Re: Beta for 2.1.1 available

2014-11-25 Thread Hugo Hinterberger
On Tue, 25 Nov 2014 10:57:34 +0100, Kristian Fiskerstrand wrote: On 11/25/2014 10:50 AM, Hugo Hinterberger wrote: Hi Kristian, On Mon, 24 Nov 2014 21:40:22 +0100, Kristian Fiskerstrand wrote: For 2.1 you need the following in dirmngr.conf: hkp-cacert /path/to/sks-keyservers.netCA.pem

Re: Beta for 2.1.1 available

2014-11-25 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/25/2014 10:50 AM, Hugo Hinterberger wrote: > Hi Kristian, > > On Mon, 24 Nov 2014 21:40:22 +0100, Kristian Fiskerstrand > wrote: > >> For 2.1 you need the following in dirmngr.conf: hkp-cacert >> /path/to/sks-keyservers.netCA.pem >> ...

Re: Beta for 2.1.1 available

2014-11-25 Thread Hugo Hinterberger
Hi Kristian, On Mon, 24 Nov 2014 21:40:22 +0100, Kristian Fiskerstrand wrote: For 2.1 you need the following in dirmngr.conf: hkp-cacert /path/to/sks-keyservers.netCA.pem instead of keyserver-options ca-cert-file="C:/Users//AppData/Roaming/gnupg/sks-keyservers.netCA.crt" OK, so: sks-keys

Re: Beta for 2.1.1 available

2014-11-24 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/2014 03:37 PM, Hugo Hinterberger wrote: > Hi, Hi Hugo, ... > I am still not able to load (receive) keys from key servers. On > the command line I get the error "keyserver receive failed: No > keyserver available". in GPA I get the warning

Re: Beta for 2.1.1 available

2014-11-24 Thread Hugo Hinterberger
Hi, On Mon, 24 Nov 2014 09:24:28 +0100, Werner Koch wrote: GnuPG changes in 2.1.1-beta35 I noticed that for malformed PGP messages there is no notification of the user in GPA. When verifying a malformed PGP message an empty verification result windows is shown (see attached image). *

Re: Beta for 2.1.1 available

2014-11-24 Thread Werner Koch
On Mon, 24 Nov 2014 17:39, patr...@enigmail.net said: > All fixed indeed! I created the first GnuPG build that did not require a > single patch on OS X :-) Yeah! Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. _

Re: Beta for 2.1.1 available

2014-11-24 Thread Werner Koch
On Mon, 24 Nov 2014 16:22, jo...@netpage.dk said: > I cannot get it to work with my OpenPGP card. > The card works fine with GPG 2.0 > If I try anything needing a secret key, it just outputs "No > secret key" This is known. As a worrkaround use gpg-connect-agent learn /bye Salam-Shalom,

Re: Beta for 2.1.1 available

2014-11-24 Thread Patrick Brunschwig
On 24.11.14 09:24, Werner Koch wrote: [...] > > GnuPG changes in 2.1.1-beta35 > - > [...] > * Fixed build problems on Mac OS X All fixed indeed! I created the first GnuPG build that did not require a single patch on OS X :-) -Patrick ___

Re: Beta for 2.1.1 available

2014-11-24 Thread Josef Schneider
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I cannot get it to work with my OpenPGP card. The card works fine with GPG 2.0 If I try anything needing a secret key, it just outputs "No secret key" D:\>gpg --detach-sign barstick.rar gpg: NOTE: THIS IS A DEVELOPMENT VERSION! gpg: It is only

Re: Beta for 2.1.1 available

2014-11-24 Thread K. Raven
Hi Kristian, > I reproduced this on a VM running $ gpg --version > gpg (GnuPG) 2.1.1-beta40 > libgcrypt 1.7.0-beta122 I have tried it with gpg --version gpg (GnuPG) 2.1.1-beta35 libgcrypt 1.6.2 and had no problems: gpg: sende Schlüssel 0x5A1796454623BA84 auf den hkps-Server hkps.pool.sks-keyse

Re: Beta for 2.1.1 available

2014-11-24 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/2014 04:01 PM, Werner Koch wrote: > On Mon, 24 Nov 2014 15:03, > kristian.fiskerstr...@sumptuouscapital.com said: > >> I reproduced this on a VM running $ gpg --version gpg (GnuPG) >> 2.1.1-beta40 libgcrypt 1.7.0-beta122 > > Are you using

Re: Beta for 2.1.1 available

2014-11-24 Thread Werner Koch
On Mon, 24 Nov 2014 15:03, kristian.fiskerstr...@sumptuouscapital.com said: > I reproduced this on a VM running $ gpg --version > gpg (GnuPG) 2.1.1-beta40 > libgcrypt 1.7.0-beta122 Are you using libgpg-error 1.15 ? That one has a bug commit c307e1f801cd9a25c4a5b9a90073362219d52ee6 Author: W

Re: Beta for 2.1.1 available

2014-11-24 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/2014 01:43 PM, Werner Koch wrote: > On Mon, 24 Nov 2014 10:55, > kristian.fiskerstr...@sumptuouscapital.com said: > >> Is this limited to GPA? I seem to also encounter issues directly >> from CLI to this effect. > ... > $ grep zimmerman

Re: Beta for 2.1.1 available

2014-11-24 Thread Werner Koch
On Mon, 24 Nov 2014 10:55, kristian.fiskerstr...@sumptuouscapital.com said: > Is this limited to GPA? I seem to also encounter issues directly from > CLI to this effect. Yes. The thing is that GPA makes direct use of the gpgkeys_foo helpers and bypasses gpg for keyserver access. Now with 2.1 we

Re: Beta for 2.1.1 available

2014-11-24 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/2014 09:24 AM, Werner Koch wrote: > Hi, > > mainly to test the fixes to the Windows installer, I did a quick > beta last Friday. However, while testing it I found that in GPA > the export of keys to the keyserver does still not work. Inst

Beta for 2.1.1 available

2014-11-24 Thread Werner Koch
Hi, mainly to test the fixes to the Windows installer, I did a quick beta last Friday. However, while testing it I found that in GPA the export of keys to the keyserver does still not work. Instead of delaying a test release even more I have published that installer anyway. Thus most things sho