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: "key algorithm" in GnuPG's signature verification output

2014-12-10 Thread Hugo Hinterberger
Hi Chris, So, are you saying that my messages break your signatures of replies to my messages? Regards, Hugo ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users

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: "key algorithm" in GnuPG's signature verification output

2014-12-10 Thread Hugo Hinterberger
Hi Chris, Why break quotation marks "1AF778E4" and "good" or "bad" in OP signature verification while answering? I hope I understood you correctly. I use “"” when it is required. In regular text I try to follow typographical conventions for text. Nothing seems to be broken on my end. It mi

Re: "key algorithm" in GnuPG's signature verification output

2014-12-09 Thread Hugo Hinterberger
Hi, It seems that you (MFPA) changed your signing practice after I noted that I can't verify signatures created with your key “1AF778E4”. I did not know that one could sign a message with two keys in one signing block. I am wondering if there is a way to collapse the verification result for

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

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,

Mailvelope [OpenPGP.js] key size vs. GnuPG

2014-12-01 Thread Hugo Hinterberger
Hello, I created a key using Mailvelope (the key I intended to use did not work with Mailvelope) and I noticed that GnuPG shows rsa2048 for the [SC] primary key and rsa2047 for the [E] subkey. Mailvelope shows 2048 bits for both keys. My guess is that Mailvelope generates the keys and sho

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 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 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: Error message "Ohhhh jeeee: ... this is a bug"

2014-11-19 Thread Hugo Hinterberger
Hi, this should go to: "MFPA <2014-667rhzu3dc-lists-gro...@riseup.net>", sorry if it goes on the list "gmane.comp.encryption.gpg.user" too (minor user/MUA f-), although this might be interesting to Werner Koch also. I just tried to verify your message, but failed at importing your key. GPG