OK in VS-Desktop-3.2.94.478-Beta
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Tue, Jan 7
Doesn't crash with VSD-beta-478 either
Works correctly in the last beta!
Also works in VSD-beta-478
works as expected with beta 478
works with VS-Desktop-3.2.94.474-Beta, too
removing the gpgcom tag as its only relevant for vsd and is already backported
Backported for VSD 3.3
As discussed offline we continue in this ticket.
Please resize to content when the search results are shown, for the first time only.
Should I close this ticket again and make a new one for the width of the result?
Seems I did not test this sufficiently. This is how the very first Search on a new installation looked with VS-Desktop-3.2.94.474-Beta:
Note that that Beta uses a 64 bit Kleopatra but the GnuPG engine was accidentally build for 32 bit. This will be fixed with the next Beta. That might increase the confusion a bit.
All applied.
Mon, Jan 6
Backported for VSD 3.3
GpgEX requires/uses Kleopatra so that only GnuPG would be left if you could deselect Kleopatra. And that's exactly what the simple installer installs because the simple installer is included in the Gpg4win installer.
FYI usually these are my install options:
No problem. I can stay on 4.4.x. Just thought I should give the beta a try and let you guys know.
Thanks for your feedback. Maybe the "minimal" install is missing a file. It's a beta version for a reason. We'll make sure to fix it for the stable release.
This is ok in VS-Desktop-3.2.94.474-Beta but in the EN version the SecOPs are missing because of a missing file during build.
-> Check again with the next build
it would be best to add an API to gpgrt to iterate over registry entries.
None. I just use the command line tools and always perform a "minimal" install. @aheinecke: I already tested it on cmd.exe. Same result. Also I do not have QT installed, or a QT_PLUGIN_PATH set up. The bottom line for me is still:
Sun, Jan 5
Fri, Jan 3
Change the encryption code to only allow 256 bit session keys with Kyber regardless of the preferences, iff --require-pqc-encryption is set. […] We could as well also encforce AES-256 also without that option.
What if we encrypt to several recipients, only some of them having a Kyber encryption key? Should we still enforce AES-256 in that case regardless of the preferences, and assume that by now everybody should support AES-256?