> You are testing a modern tool that aims to be standards-compliant
> against an unmaintained, known-broken program that was out of date
> before the standards were even settled. When you found an
> incompatibility, you reported the problem against the modern,
> standards-compliant tool.
I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Monday 1 December 2014 at 9:53:18 AM, in
, gnupgpack wrote:
> But where to get old freeware version
A search for "old version downloads" (without quotes) might be a
reasonable place to start.
- --
Best regards
MFPAm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Monday 1 December 2014 at 10:33:49 AM, in
, gnupgpack wrote:
> Hello,
>> I suggest that you stop deleting the In-reply-to and
>> the References header.
> Ok, i'll give it a try ;)
There, that worked. (-:
> Some of the cleaned header e
On 01/12/14 18:27, Duplicity Mailing List wrote:
> I bought a GPG smartcard, but, I'm having issues using it. I first
> tested it out on my desktop and messed around with it a little
> generating a few keys, now I've populated my keyring with a bunch of
> keys I have no idea how to delete, any help
I bought a GPG smartcard, but, I'm having issues using it. I first
tested it out on my desktop and messed around with it a little
generating a few keys, now I've populated my keyring with a bunch of
keys I have no idea how to delete, any help?
>$ gpg2 --delete-secret-key ${KEYID}
>
>sec rsa2048/$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.12.14 11:33, gnupgpack wrote:
> Hello,
>
>> I suggest that you stop deleting the In-reply-to and the
>> References header.
>
> Ok, i'll give it a try ;)
Now it works. Thank you, this improves reading your posts in context
much easier!
Ludwi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.12.14 13:13, Dave English wrote:
> I have though what looks like the same problem trying to build
> 1.4.18 from source on Mac OS X 10.10, according to the howto
> Version 4.26 (1 July 2014):
>
> http://macgpg.sourceforge.net/docs/howto-build-
On 01/12/14 15:47, Daniel Kahn Gillmor wrote:
> When you found an incompatibility, you reported the problem against
> the modern, standards-compliant tool.
I think you're being a bit harsh. He asked if this was a known problem,
and how to work around it; he didn't report a bug.
Peter.
--
I use
>> 6.5.8 is about sixteen years old now and has many known security
>> problems. Please stop using it.
>
> (Yes, intended only for testing...)
Then ensure you're testing it correctly by adding "pgp6" to your
gpg.conf file, or "--pgp6" to the command line, whenever doing anything
that involves PGP
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
On 01-12-2014 15:47, Daniel Kahn Gillmor wrote:
> You are testing a modern tool that aims to be standards-compliant
> against an unmaintained, known-broken program that was out of date
> before the standards were even settled. When you found an
> incompatibility, you reported the problem against
On 12/01/2014 04:53 AM, gnupgpack wrote:
>> 6.5.8 is about sixteen years old now and has many known security
>> problems. Please stop using it.
> (Yes, intended only for testing...)
You are testing a modern tool that aims to be standards-compliant
against an unmaintained, known-broken program th
> On 8 Nov 2014, at 18:04, Patrick Brunschwig wrote:
>
> On 07.11.14 06:41, Ramsey Dow wrote:
>> Hello, I am having a build failure with GnuPG 2.1.0 on OS X 10.10 using
>> Xcode 6.1's compiler tools.
>>
>> I have successfully compiled and installed all of the prerequisite libraries
>> (npth 1
Hello,
> I suggest that you stop deleting the In-reply-to and the References
> header.
Ok, i'll give it a try ;)
>> X-MSMAIL-PRIORITY:
> Given that you set this on a per-message basis as High/Normal/Low,
> it's not a security/privacy issue at all. Deleting it just means all
> your messages defa
Hello,
> 6.5.8 is about sixteen years old now and has many known security
> problems. Please stop using it.
(Yes, intended only for testing...)
> - From (possibly inaccurate) memory, PGP was up to somewhere around
> version 8.x before it supported signing subkeys.
First PGP version supporting W
15 matches
Mail list logo
