Re: private-keys-v1.d

2017-03-13 Thread Daniel Kahn Gillmor
On Thu 2017-03-09 13:44:19 -0500, Long Si wrote: > Before migrating to a new system, I exported my GPG secret keys and > then imported them. what version of gpg did you have on the old system? what version on the new system? the steps you took sound reasonable to me, as long as the new system

Re: Security doubts on 3DES default

2017-03-13 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Monday 13 March 2017 at 11:02:48 PM, in , Robert J. Hansen wrote:- > I don't > know how you'd > come up with a real-world case where you'd need a > common hash algorithm > set for

Re: Security doubts on 3DES default

2017-03-13 Thread Robert J. Hansen
>> Again, required per the spec, and this can be >> prevented by having one person >> on the list use a DSA-2048/-3072 key, which forbids >> SHA-1 usage. > > Really? many of the messages to the PGPNET discussion group [0] have > SHA-1 signatures. Messages are signed and encrypted to about 30

Re: Security doubts on 3DES default

2017-03-13 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Monday 13 March 2017 at 3:17:07 PM, in , Robert J. Hansen wrote:- > Again, required per the spec, and this can be > prevented by having one person > on the list use a DSA-2048/-3072 key,

Re: Interleaving issue

2017-03-13 Thread Werner Koch
On Sun, 12 Mar 2017 17:36, r...@sixdemonbag.org said: > sig!31DCBDC01B44427C7 2015-07-16 Robert J. Hansen 14 good signatures This is a diagnostic which goes to stderr. The former is fully buffered, the latter is line

Re: Security doubts on 3DES default

2017-03-13 Thread Kristian Fiskerstrand
On 03/13/2017 01:47 PM, Ryru wrote: > Is my understanding correct or do I miss an important fact? What are > your thoughts about this behaviour? See section 13.2 of RFC4880, fyi the behavior changes in the context of RFC6637. My thoughts; concerns about 3DES are premature. The focus on

RE: Security doubts on 3DES default

2017-03-13 Thread Robert J. Hansen
> According to the gpg2 man page, 3DES is added always as kind of least > common denominator: This is required behavior per RFC4880. Your concern should be addressed to the IETF OpenPGP working group, not to GnuPG. > In my opinion this design decision can lead to serious security troubles. If >

Security doubts on 3DES default

2017-03-13 Thread Ryru
Hello List I'm new to this list and joined because I have some security doubts regarding encryption preferences (setpref/showpref). According to the gpg2 man page, 3DES is added always as kind of least common denominator: 8<--- When setting preferences, you should list the algorithms in the

[Solved] Re: Error searching key from keyserver in gpg 2.1.19

2017-03-13 Thread Alexander Strobel
Am 11.03.2017 um 12:40 schrieb Werner Koch: > On Fri, 10 Mar 2017 10:26, alexander.stro...@giepa.de said: > >> What's the problem here? > > [Troubleshooting advisory] D'oh The problem was sitting before the monitor. GnuPG 2.1 was blocked by my firewall. GnuPG returns the key from