Do you mean something like this
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 15 2022
Mar 14 2022
because libexpat does contain vulnerabilties
gpgol/doc/gpl.texi (line 9)
gpgol/COPYING-ICONS (line 52)
What are the other to places?
And updated scd_validate2.py:
Wrote a pam module which interacts a user for auth:
When I greped for links to the FSF page (grep with string "fsf" I found out that there is one link to https://emailselfdefense.fsf.org/en/infographic.html in line 722 of src/ribbon-callbacks.cpp. Is that the link that was meant?
A simple first step would be to install pinentry-gtk only in the GPA variant.
I agree. @cklassen can you make a suggestion?
Thanks for you patches. Most of them applied cleanly despite that I delayed processing them for half a year.
Mar 12 2022
@mieth sorry for the delay. meanwhile I adjusted the ciphersuite of the WKD gateway to include an AES-CBC suite. would be interested if it works now on the setup you tested before.
Mar 11 2022
I think this is because we install pinentry-gtk, too. So we have that GTK dependency.
Thank you for your comment.
Mar 10 2022
Gook luck on Solaris with this suggestion ;-)
Gook luck on Solaris with this suggestion ;-)
For the record, the typical response to "it doesn't work" support requests for keys.o.o still comes down to killall dirmngr.
I write a prototype in Python using pyassuan:
Mar 9 2022
Reagarding the OpenPGP specs: there is a new draft with LOTS of changes to already agreed upon formats and conducted interop tests. Almost everything we implemented in GnuPG and RNP has had rough consensus in the WG. Minor things like AEAD chunk size were the contested pieces. However, now they want to change everything with the possible outcome of discretization the long established trust in the stability and durability of the PGP data and key format.
Great, thank you very much!
Thanks for notifying. Will be fixed in the next release (mid Apri).
Sorry. While v5 things in the specification is still in flux, from the viewpoint of the implementation, this patch is 100% valid and it makes sense.
Fixed in master and 2.2 branch.