- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 2 2018
Nov 1 2018
Oct 31 2018
The explicit check for a valid FD (in select) I mentioned above is commit 8173c4f1f8a145c4b1d454f6f05e26950e23d675
Oct 30 2018
Oct 29 2018
We need more testing.
We had this idea to have a label: or similar item in the extended-key-format which is displayed in addition to the other info. The user can then use an editor to put whatever she likes into this field.
It actually tries several servers but we need to set a limit because we need to cope with longer timeouts. Do you suggest to toggle between v4 and v6 addresses? That is if a v6 address fails, first try the next v4 address and it that fails, another v6 address, etc.
I don't see a problem. If you have the private key you can and will use it. I guess your concern is an oracle?
Oct 27 2018
Thanks.
Oct 26 2018
Fixed in master and 1.8.
@dkg: Thanks for the comments and your patience to convince me.
The next step is to release libgcrypt 1.8.4 :-)
Actually we plan to provide a more convenient way to perform the DH operation. See for example P7 for the non-elegant way which is required today.
Fixed in master and 1.8 by detecting a fork and re-opening the devices
Fixed in master and 2.2
Oct 25 2018
Oh, that is really old code dating back to dirmngr-1. There is only one user I will see whether I can replace it with the generic parser we have in http.c
Now that is funny c+p code. I vaporized it to just a few lines.
It seems that this part of the code was not finished. Unfortunately upstream of the dns code is unresponsive and thus we started to maintain the code base by ourselves. There is still an open question whether we should do that to the full extend, in which case we would integrate the code closer into the GnuPG framework with its own logging subsystems.
The correct technical term is OpenPGP Public Keyblock but I better shut up on the certificate vs. Public key(block) question.
Oct 24 2018
Thanks.
Thanks.
Thanks.
Thanks.
Thanks.
Thanks. May also happen if the first print_assuan_status fails.
Fixed in 1.8
Fixed in 1.8
yat2m updated. Thanks.
Thanks.