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 and
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
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.
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.
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:
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.txt and
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
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 for
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 the past
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
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
-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
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
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 as the
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 work
-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 better. When
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 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 error
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.
When
-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 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 #
kdns
21 matches
Mail list logo
