Might there be a relation to T7842? But I would have thought that then all signed messages would be unaffected.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Wed, Oct 22
Tue, Oct 21
Mon, Oct 20
We need to check what the current status here is. This has been in the 5.0 Betas for a while, so testing with 5.0-Beta369 will work
Fri, Oct 17
With a GNUPG-Home on another Partition (on the VMs shared folder with the host) the auto refresh after deletion additionally doesn't work for public keys or S/MIME certificates.
Thu, Oct 16
Wed, Oct 15
We had considered and rejected adding below the above configuration a marked section (like e.g. with a frame) showing the options in the order they appear in the sign/encrypt window:
- Sign as
- Encrypt for me
- Encrypt for others
- Encrypt with password
- Encrypt / Sign each file separately
We discussed this and decided that this would not be useful, as
Fri, Oct 10
This does not occur any more in Gpg4win-5.0.0-beta369
Thu, Oct 9
The latter is also the case for deleted softkeys.
Might be related to T7836?
Might this be related to T4953?
I was asked to test this again with a newer version. With Gpg4win-5.0.0-beta369 not much has changed, you still can choose "Certify" on the only secret key and the certify window only allows "Cancel". Difference is only that now the "Certify with" line is empty:
Wed, Oct 8
Mon, Oct 6
Thu, Oct 2
Wed, Oct 1
As this was finished more than a year ago, this should be included (and testable) in vsd