- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
Yesterday
Fri, Jan 23
I don't think that we will implement that any time soon. Today we too often require more mlock-able memory than available and in this case Libgcrypt resorts to allocating new memory arenas which are not locked. This is not as worse as one might think: the majro advantage with secmem is that a free() on secmem allocated memory will also wipe that memory. A better solution has always been to use an encrypted swap/paging file. 25 years ago, it was not easy to configure but today there should be no problem and hopefully already the default.
Please run with --debug 0 which should show you which confiration files are read in which order. Is there anything in a common.conf file? A log-file statement tehre would overwrite the command line option.
While key generation works now with an expiry date up to 2106-02-04, the representation on the command line is a bit ugly.
Current state needs to be tested
@ikloecker: Is this fixed?
Current state needs to be tested as soon as T7509: gpg4win: Make the AppImage build work with the new Docker-based build script is resolved
@werner: Is this resolved?
We need to test the current state
this seems obsolete
Thu, Jan 22
Fixed and backported for VSD 3.4
Backported for VSD 3.4
I have split out the "Tab navigation in the Smartcard Dialog is broken" issue because it's unrelated to this ticket: T8051: Kleopatra: Tab navigation in smartcard table is broken
Backported for VSD 3.4
I think this is a very good idea. Go ahead an backport, I'll change the ticket description accordingly.
Re-opened because a regression is reported.
Wed, Jan 21
We need to retest this with vsd34 as @ikloecker backported some tab related things after the 3.3.4 release.
Backported for VSD 3.4
I'll wait for feedback before I backport this.