User Details
- User Since
- Mar 27 2017, 4:48 PM (422 w, 6 d)
- Roles
- Administrator
- Availability
- Busy Busy until Sep 9 2030.
Yesterday
Heiko, I told you already in T7106 that it is not a good idea to re-open a ticket. If you really want to discuss stuff, take that to a mailing list.
Fri, May 2
Yes, this is related to T7547. With my last fix for that I overlooked that we use PUBKEY_USAGE_CERT to internally request the primary key but that one is not set because in general USAGE_SIG means the same (except for some case in PGP7 mode).
> I'm not sure i understand why "the latest" should be preferred.
Wed, Apr 30
Tue, Apr 29
I also spend some time with this and the problem is described by this comment in trustdb.c:
Mon, Apr 28
No, it is not a bug and I beg you not to change the status again. Don't start the same trouble here as some of you guys did with the IETF WG!
I can't speak for C++ but I appreciate that you used the same flag values as in gpgme proper.
This is just one build of PGP and you would need to test all versions on Windows, macOS and Unix. You also need to test against all versions of GnuPG since 1998 (when we started with interop tests). We won't change this in GnuPG and risk regression. If you have a problem with that go and add a fix to your tool - name it bug compatibility or whatever. And please do not re-open this bug.
Sun, Apr 27
The report is correct but it does not make sense to fix it. If you want to use a concrete expiration date just enter the IS date at the prompt; use ? at the prompt for a short description.
Fri, Apr 25
Thu, Apr 24
Thanks for the patch but I think it is better to fix this in yat2m. I created a new tag for bugs related to it.
Wed, Apr 23
This is really a minor thing and and it is actually true if you also sign something.
Tue, Apr 22
BTW, fingerprints for X.509 are not well defined because you get a different one when changing the *unsigned" attributes. Not a common case but one should be aware of it.
No more octals .-)
Thu, Apr 17
Wed, Apr 16
Gpg4win is a community version and we may or may not apply Authenticode signatures. You can do that yourself, after having checked our OpenPGP release signature. You may however be interested in GnuPG Desktop, which comes with full support and also Authenticode signature.
Tue, Apr 15
Yes it does. I even tested it yesterday.
What is FlowCrypt?
Removing egrep from a Unix system will break all kind of stuff. I am not even sure whether old Unices support grep -E.
Mon, Apr 14
Fri, Apr 11
That error code is actually not an error code but it is the ERROR state from the Kleo SFM. We have seen that yesterday already.
Thu, Apr 10
Wed, Apr 9
This might also be related to rGa7ec3792c5 (cf. T2982)
There is no well defined pripority for the CRL DPs. The code enumarates the DP and tries one after the other until it founds one. If you use --ignore-http_dp http DPs are skipped and with --ignore-ldap-dp LDAP DPs are ignored.
1.53 has been released this morning.