-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have an older gnuPG (v1.4.6) that is apparently mis-configured.
When signing a message, it fails with a note about what a bad idea
IDEA is, and quits. gpg is called from an email program to perform
security services. There is no command opti
Hi all,
after a recent upgrade to Kubuntu 14.10, gpg started to show that warning
message about Gnome Keyring hijacking it. After adding the following lines to a
startup script:
killall gpg-agent
killall gnome-keyring-daemon
gpg-agent --daemon --enable-ssh-support --write-env-file
"${HOME}/.gp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On 07.12.14 21:36, Lucas Verney wrote:>
> Le 07/12/2014 21:25, Ludwig Hügelschäfer a écrit :
>> Hi,
>>
>> On 07.12.14 21:09, Lucas Verney wrote:
>>
>>> In Arch, with Thunderbird 31.2 and Enigmail 1.7.2, I can't get
>>> Enigmail to use Seahor
The Arch linux GnuPG package 2.1.0-6 is unable to connect to HKPS. The package
maintainer is currently unable or unwilling to build GnuPG against GnuTLS.
For further information you can follow: https://bugs.archlinux.org/task/42739
I attempted to convince the package maintainer that the current
-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
On Wednesday, 2014-12-10 19:01:25 Kristian Fiskerstrand wrote:
> See https://bugs.archlinux.org/task/42739?opened=6005&status%5B0%5D=
Well lo and behold. When I rebuilt the package with GnuTLS as a dependency and
killed the running dirmngr process HKPS works.
I understand that the GnuPG package
On Wed, 10 Dec 2014 18:10, kristian.fiskerstr...@sumptuouscapital.com
said:
> The SNI issue last discussed in [0] springs to mind. But I still
> experience this on gpg (GnuPG) 2.1.1-beta67
I have not yet tracked this down. For easier debugging I added some
more debug output. Forgot to push the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/10/2014 06:44 PM, Kristian Fiskerstrand wrote:
>
> ...
>
>> Individual keyserver should be no issue as long as you don't hit
>> the SNI issue, are you sure gnupg is built with gnutls / hkps
>> support? I know that at least earlier builds of
On Wednesday, 2014-12-10 12:10:28 Daniel Kahn Gillmor wrote:
> > Can you provide more detail (or a link to a bug report) about the
> > problem with hkps in 2.1.0 ?
On upgrade to 2.1.0 looking up keys from a keyserver stopped working for me. I
tracked down the following comment from Hugo Hinterber
On 12/10/2014 12:26 PM, Samir Nassar wrote:
> On Wednesday, 2014-12-10 12:10:28 Daniel Kahn Gillmor wrote:
>>> Can you provide more detail (or a link to a bug report) about the
>>> problem with hkps in 2.1.0 ?
>
> On upgrade to 2.1.0 looking up keys from a keyserver stopped working for me.
> I
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
...
> Individual keyserver should be no issue as long as you don't hit
> the SNI issue, are you sure gnupg is built with gnutls / hkps
> support? I know that at least earlier builds of arch did not
> include gnutls support, which caused some headac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/10/2014 06:26 PM, Samir Nassar wrote:
> On Wednesday, 2014-12-10 12:10:28 Daniel Kahn Gillmor wrote:
>>> Can you provide more detail (or a link to a bug report) about
>>> the problem with hkps in 2.1.0 ?
>
> On upgrade to 2.1.0 looking up keys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/10/2014 06:10 PM, Daniel Kahn Gillmor wrote:
> On 12/10/2014 12:02 PM, Samir Nassar wrote:
>> It is my understanding that 2.1.0 has a problem with hkps
>> keyservers (such as the hkps SKS pool) and that this is only
>> fixed in the betas for 2.
On 12/10/2014 12:02 PM, Samir Nassar wrote:
> It is my understanding that 2.1.0 has a problem with hkps keyservers (such as
> the hkps SKS pool) and that this is only fixed in the betas for 2.1.1. If
> this
> understanding is correct and 2.1.1 fixes the hkps issues, I'd vote to release
> 2.1.1
On Wednesday, 2014-12-10 17:41:21 Werner Koch wrote:
> Hi!
>
> it is now more than a month since the 2.1.0 release and I am asking
> myself whether it is time to do another release. There are about 50
> commits including
It is my understanding that 2.1.0 has a problem with hkps keyservers (such
On 12/10/2014 11:41 AM, Werner Koch wrote:
> However, there are still open bugs and new bugs are also detected every
> few days. I think it is better to do a 2.1.1 now instead of trying to
> get all new bugs fixed - it would delay things into the next year.
>
> I plan to look into the learn card
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Hugo,
yes, I am sorry: it seems to be like this assumption, but only if you are
using other quotation marks than standard "something".
Regards, Chris
> -Original Message-
> From: Gnupg-users [mailto:gnupg-users-boun...@gnupg.org] On Beh
Hi!
it is now more than a month since the 2.1.0 release and I am asking
myself whether it is time to do another release. There are about 50
commits including
* gpg: Detect faulty use of --verify on detached signatures.
* gpg: New import option "keep-ownertrust".
* gpg: Fixed regression in -
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
On Wed, 10 Dec 2014 08:52, karda...@gmail.com said:
> article, but currently it allows just one subkey while generating key pair.
> What I want is a little bit different: I want to generate just sub-keys
> without user interaction.
It might be usefull to add a
--quick-gen-subkey FINGERPRINT AL
Hi Hugo,
I did make some test with your last post:
Outlook-incoming as Content-Transfer-Encoding: base64 Content-Type: text/plain;
charset="utf-8"; Format="flowed"
If signing “something” (your choice) and resending, signature is broken.
If signing „something“ and resending, signature is broken.
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
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
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
24 matches
Mail list logo
