Feed Advanced Search

Jul 19 2019

Valodim added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

So, what about this? If I recall correctly, we had agreed in the call to merge this patch, at least into master?

Jul 19 2019, 4:52 PM · gnupg (gpg23), Feature Request

Jul 10 2019

Valodim updated subscribers of T4617: Odd behavior for HTTP(S) scheme in --keyserver config.

Ah, that makes sense, good catch. Seems this is just an issue of documentation, then.

Jul 10 2019, 6:20 PM · Documentation, Keyserver, dirmngr
Valodim created T4617: Odd behavior for HTTP(S) scheme in --keyserver config in the S1 Public space.
Jul 10 2019, 4:52 PM · Documentation, Keyserver, dirmngr
Valodim added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

We should put it of the agenda od the Brussesl summit in 3 weeks. I have a few ideas what we can do in gpg.

Jul 10 2019, 4:36 PM · gnupg, Keyserver

Jul 5 2019

Valodim added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

and from my understanding they are sending the self-signatures anyway.

Jul 5 2019, 3:31 PM · gnupg (gpg23), Feature Request

Jul 2 2019

Valodim added a comment to T4597: Support GCM modes for ntbtls..

Done. Hopefully this works now :)

Jul 2 2019, 5:39 PM · Feature Request, ntbtls
Valodim added a comment to T4597: Support GCM modes for ntbtls..
Which is a bad idea because CBC is still a very common cipher mode.
Jul 2 2019, 4:02 PM · Feature Request, ntbtls

Jun 24 2019

Valodim added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

It's been a while, any word on this? I sent the DCO as requested. Are there any technical concerns left to address?

Jun 24 2019, 12:48 PM · gnupg (gpg23), Feature Request

Jun 21 2019

Valodim added a comment to T4493: Default to HKPS, not HKP.

A possible exception here is that .onion TLDs should stick with HKP by default

Jun 21 2019, 11:16 AM · dirmngr, Feature Request

May 10 2019

Valodim created T4493: Default to HKPS, not HKP.
May 10 2019, 2:13 PM · dirmngr, Feature Request

Apr 5 2019

Valodim added a comment to T4448: Add "Autocrypt" key-origin.

I disagree that it's conceptionally the same, unless you also consider any key on an HTTP server to be "conceptionally the same" as WKD.

Apr 5 2019, 4:34 PM · Feature Request
Valodim added a comment to T4448: Add "Autocrypt" key-origin.
Certain origins do have special treatment but in general the key origin is meta data for the frontend.
Apr 5 2019, 10:56 AM · Feature Request

Apr 4 2019

Valodim added a comment to T4448: Add "Autocrypt" key-origin.

I'm a bit confused. The origin of Autocrypt keys is clearly different from keyservers ("ks"), why would they use the same value? I was aware that origin values are mapped to integers, but your description seems to imply that these integers have significant ordering in terms of trust. The documentation in the man page is a bit bare bones, but my interpretation of "key-origin" was that it simply stated the method of discovery for a key, leaving any implications of trust to the client. Is this incorrect?

Apr 4 2019, 7:23 PM · Feature Request
Valodim renamed T4448: Add "Autocrypt" key-origin from Add "Autocrypt" origin to Add "Autocrypt" key-origin.
Apr 4 2019, 11:06 AM · Feature Request
Valodim created T4448: Add "Autocrypt" key-origin.
Apr 4 2019, 11:05 AM · Feature Request

Nov 8 2018

Valodim added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

Fair enough. Let's wait and see what others think.

Nov 8 2018, 1:24 PM · Not A Bug, OpenPGP, gnupg

Oct 29 2018

Valodim added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

The same *cannot* be said for a subkey that is marked specifically for certification or signing, and not for decryption.

Oct 29 2018, 7:57 PM · Not A Bug, OpenPGP, gnupg

Oct 27 2018

Valodim created T4235: GnuPG doesn't respect key flags when decrypting.
Oct 27 2018, 10:24 PM · Not A Bug, OpenPGP, gnupg

Aug 29 2018

Valodim added a comment to T3277: decrypting data symmetrically doesn't reliably convey confidentiality property.

I'm sorry but the explanation you give does not address the original issue I described, and which dkg then clarified. The discussion about AE is tangentially related, but the issue I described relates to the gpg interface:

Aug 29 2018, 2:01 PM · Feature Request, gnupg (gpg22)

Feb 1 2018

Valodim added a comment to T3766: GnuPG should reject keys that are subkeys of itself.

Sorry, I don't understand. Can you describe your use case in more detail?

Feb 1 2018, 12:47 PM · gnupg (gpg22), Feature Request

Jan 31 2018

Valodim added a comment to T3766: GnuPG should reject keys that are subkeys of itself.

a key that is signed as its own subkey, in a construct where the key and subkey have the same fingerprint? what ever could be a valid use case for such a scenario?

Jan 31 2018, 8:06 PM · gnupg (gpg22), Feature Request
Valodim added a comment to T3766: GnuPG should reject keys that are subkeys of itself.

uploaded the offending key for reference:

Jan 31 2018, 4:27 PM · gnupg (gpg22), Feature Request
Valodim created T3766: GnuPG should reject keys that are subkeys of itself.
Jan 31 2018, 4:26 PM · gnupg (gpg22), Feature Request

Nov 7 2017

Valodim added a comment to T3488: support specialized numeric9x4 format for symmetric passphrase.

Well, I gues it's complex enough to warrant strategic discussion, which can be done in this ticket :)

Nov 7 2017, 1:31 PM · Feature Request
Valodim created T3488: support specialized numeric9x4 format for symmetric passphrase.
Nov 7 2017, 11:48 AM · Feature Request

Jul 19 2017

Valodim added a comment to T3203: gpg chokes on empty UserId.

Hm. Could you elaborate on that? Why do you think it's dangerous?

Jul 19 2017, 5:36 PM · Feature Request, gnupg (gpg22)
Valodim added a comment to T3203: gpg chokes on empty UserId.

Isn't it much nicer if we semantically convey that a key doesn't have associated user id information, compared to just listing such keys between "Andre" and "Arnold"? I'd much rather special case the empty string in the key list than an arbitrary string that may or may not have a universally obvious meaning.

Jul 19 2017, 4:22 PM · Feature Request, gnupg (gpg22)
Valodim added a comment to T3203: gpg chokes on empty UserId.

I think "anonymous" user ids are a valid use case, since openpgp doesn't allow "no" user ids. Disallowing zero-length user ids will just cause implementations that intend to use anonymous user ids to use another type of "empty", like a single space character. And the effect of that will be that it's no longer trivially defined what an "anonymous" user id is for special handling, e.g. showing a localized "anonymous key" placeholder. Please don't restrict zero-length user ids.

Jul 19 2017, 11:24 AM · Feature Request, gnupg (gpg22)

Jul 13 2017

Valodim renamed T3277: decrypting data symmetrically doesn't reliably convey confidentiality property from decrypting data symmetrically doesn't preserve authentication property to decrypting data symmetrically doesn't reliably convey confidentiality property.
Jul 13 2017, 7:15 PM · Feature Request, gnupg (gpg22)
Valodim added a comment to T3277: decrypting data symmetrically doesn't reliably convey confidentiality property.

Well, yes, it's not general authentication like AE provides, didn't think this through entirely. However, handing encrypted data to gnupg and then not being sure if it was actually decrypted with a passphrase makes even the confidentiality property questionable.

Jul 13 2017, 6:53 PM · Feature Request, gnupg (gpg22)
Valodim created T3277: decrypting data symmetrically doesn't reliably convey confidentiality property.
Jul 13 2017, 6:31 PM · Feature Request, gnupg (gpg22)

Jun 23 2017

Valodim added a comment to T3203: gpg chokes on empty UserId.

seems this was fixed along the way, then. I only tested with 2.1.18.

Jun 23 2017, 7:05 PM · Feature Request, gnupg (gpg22)

Jun 17 2017

Valodim added a comment to T3203: gpg chokes on empty UserId.

here's a public key version of the same key. it was available easier and should reproduce the bug just as well

Jun 17 2017, 1:17 AM · Feature Request, gnupg (gpg22)

Jun 13 2017

Valodim added a comment to T3203: gpg chokes on empty UserId.

user ids with length 0 do conform with rfc4880, though

Jun 13 2017, 12:47 PM · Feature Request, gnupg (gpg22)
Valodim added a comment to T3203: gpg chokes on empty UserId.

The key was created programmatically by my standard approach, which is bastardizing openkeychain unit tests. good question about the passphrase - I don't remember exactly, but I'm guessing it's either empty or "x". doesn't really matter in the context of this particular bug I guess :)

Jun 13 2017, 12:25 PM · Feature Request, gnupg (gpg22)

Jun 12 2017

Valodim updated the task description for T3203: gpg chokes on empty UserId.
Jun 12 2017, 6:56 PM · Feature Request, gnupg (gpg22)
Valodim added a comment to T3203: gpg chokes on empty UserId.

-----BEGIN PGP PRIVATE KEY BLOCK-----

Jun 12 2017, 6:54 PM · Feature Request, gnupg (gpg22)
Valodim created T3203: gpg chokes on empty UserId.
Jun 12 2017, 6:53 PM · Feature Request, gnupg (gpg22)