Dear all,
Apologies for the thread break - I was reading via the archives and have
only just subscribed.
I debugged this issue a few days ago. I've posted a patch for testing and
hopefully incorporation into a future GnuPG 2.1 build at
https://bugs.g10code.com/gnupg/issue1792
With this patch, hk
On Wednesday, March 18, 2015 06:18:53 PM Daniel Kahn Gillmor wrote:
> It looks to me like you're using the server's certificate as the CA
> certificate. I don't think that's going to work. Maybe you want to use
> the Addtrust root cert (attached here)
Ahem. You are so very right. Somehow it esca
On Wed 2015-03-18 18:03:11 -0400, Samir Nassar wrote:
> On Wednesday, March 18, 2015 10:40:57 PM Kristian Fiskerstrand wrote:
>> try renaming /home/snassar/.gnupg/myriapolis.net.crt to
>> /home/snassar/.gnupg/myriapolis.net.pem
>
> Done.
It looks to me like you're using the server's certificate a
On Wednesday, March 18, 2015 10:40:57 PM Kristian Fiskerstrand wrote:
> try renaming /home/snassar/.gnupg/myriapolis.net.crt to
> /home/snassar/.gnupg/myriapolis.net.pem
Done.
> if that doesn't help , can you increase debug verbosity in
> dirmngr.conf and set the logfile?
> $ cat dirmngr.conf
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/18/2015 10:33 PM, Samir Nassar wrote:
> On Wednesday, March 18, 2015 10:14:53 PM Kristian Fiskerstrand
> wrote:
>> gpg-connect-agent --dirmngr 'KEYSERVER --help' /bye S # Known
>> schemata: S # hkp S # hkps S # http S # finger S #
>> kd
On Wednesday, March 18, 2015 10:14:53 PM Kristian Fiskerstrand wrote:
> gpg-connect-agent --dirmngr 'KEYSERVER --help' /bye
> S # Known schemata:
> S # hkp
> S # hkps
> S # http
> S # finger
> S # kdns
Same.
When I set the keyserver to: hkp://keyserver.myriapolis.net everything works.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/18/2015 10:08 PM, Samir Nassar wrote:
> On Wednesday, March 18, 2015 09:21:08 PM Kristian Fiskerstrand
> wrote:
>> 11371 is expected to be for HKP, so requiring this to be TLS is
>> bad practice.
>
...
> gpg: DBG: chan_4 <- ERR 1 General err
On Wednesday, March 18, 2015 09:21:08 PM Kristian Fiskerstrand wrote:
> 11371 is expected to be for HKP, so requiring this to be TLS is bad
> practice.
Oh oops. Fixed now.
> > gpg-connect-agent --verbose --dirmngr 'keyserver
> > hkps://keyserver.myriapolis.net:11371' 'ks_get 1e42b367' /bye
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/18/2015 09:13 PM, Samir Nassar wrote:
> On Wednesday, March 18, 2015 08:54:47 PM Kristian Fiskerstrand
> wrote:
>> Hmm, I didn't notice that it was a wildcard cert, that should
>> also support holdfast.myriapolis.net in the cert matching,
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wednesday 18 March 2015 at 8:09:30 AM, in
, Werner Koch wrote:
>
> created: 2015-03-18 expires: never
Just wondering why we want keys to never expire by default.
Why is that better than a default validity period of "X" years?
- --
Best
On Tuesday, March 17, 2015 03:48:54 PM Paulo Lopes wrote:
> Hello,
>
> I've been using my gpg card with success in Ubuntu for a while but as
> everyone knows the init system is switching from upstart to systemd as it
> is happening on Debian and the vast majority of other distributions.
>
> In th
On Wednesday, March 18, 2015 08:54:47 PM Kristian Fiskerstrand wrote:
> Hmm, I didn't notice that it was a wildcard cert, that should also
> support holdfast.myriapolis.net in the cert matching, however it
> results a redirect and404 for [0]. If you add this as a vhost I
> suspect it will w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/18/2015 08:39 PM, Samir Nassar wrote:
> On Wednesday, March 18, 2015 07:28:31 PM Kristian Fiskerstrand
> wrote:
>> Likely related to the PTR issues[0, 1], its already in the
>> roadmap[2]
>
> Thank you Kristian,
>
> So I understand this bette
On Wednesday, March 18, 2015 07:28:31 PM Kristian Fiskerstrand wrote:
> Likely related to the PTR issues[0, 1], its already in the roadmap[2]
Thank you Kristian,
So I understand this better. When using non-encrypted connections GnuPG
doesn't have a problem, but when I am using a wildcard certifi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/18/2015 03:54 PM, Samir Nassar wrote:
> Hello,
>
> I originally posted this on the sks-devel mailing list, but after
> thinking about it, I believe this might be something I am doing
> wrong on the GnuPG side.:
>
> I set up a keyserver at key
On Mar 16, 2015, at 8:55 PM, MFPA <2014-667rhzu3dc-lists-gro...@riseup.net>
wrote:
> I would urge you to
> reconsider your decision to drop the angle brackets. At
> least one MUA (the MUA I am using to write this message)
> sends the email address enclosed in angle brackets as the
> search string
Hello,
I originally posted this on the sks-devel mailing list, but after thinking
about it, I believe this might be something I am doing wrong on the GnuPG
side.:
I set up a keyserver at keyserver.myriapolis.net.
What I have done so far:
Installed sks (1.1.5) from wheezy-backports
SKS is beh
Thanks so much for the help everyone. I believe I have this working as I need
it.
Mark Walter
Business to Business Data Integration Specialist
Certified IBM System i Specialist
Paragon Consulting Services, Inc.
mwal...@paragon-csi.com
717-764-7909 ext. 20
-Original Message-
From: Gnup
On 18/03/15 12:18, Mark Walter wrote:
> Hello all.
>
> I'm having issues with encrypt and decrypt and I know it's something I'm
> doing wrong. I created a key with Kelopatra. Imported it into GNU Privacy
> Assistant. It shows up as Fully Valid.
>
> Next, to test, I created the text file test.tx
No, Only the Private keys show up. What I tried to create and test was a public
key to give to a partner for encrypting files sent to us.
Thanks.
Mark Walter
Business to Business Data Integration Specialist
Certified IBM System i Specialist
Paragon Consulting Services, Inc.
mwal...@paragon-csi.
On Wed 2015-03-18 08:18:11 -0400, Mark Walter wrote:
> I'm having issues with encrypt and decrypt and I know it's something
> I'm doing wrong. I created a key with Kelopatra. Imported it into GNU
> Privacy Assistant. It shows up as Fully Valid.
>
> Next, to test, I created the text file test.txt a
Hello all.
I'm having issues with encrypt and decrypt and I know it's something I'm doing
wrong. I created a key with Kelopatra. Imported it into GNU Privacy Assistant.
It shows up as Fully Valid.
Next, to test, I created the text file test.txt and used the following command
to encrypt it.
gpg
On 03/18/2015 01:34 AM, Robert J. Hansen wrote:
I think this shouldn't be supported; CAST5 should only be used if (a) it's in
the
recipient's key prefs and (b) it's explicitly listed in
default-cipher-prefs.
I don’t think that ignoring the recipient’s preferences should be the
default behavio
On Tue, 17 Mar 2015 20:44, r...@sixdemonbag.org said:
> Given that 2.1 introduces a lot of new capabilities (mostly with respect
> to ECC), I think now, early on in the 2.1 series, would be a good time
> to discuss changing the defaults for newly-generated certificates.
Let's do a quick check of t
24 matches
Mail list logo
