With VS-Desktop-3.1.90.277-Beta the generated key is the default RSA 3072.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 13 2023
Nov 10 2023
For an OpenPGP group it looks now like this:
No sending possible.
When I remove the offending key (which could be made more intuitive for the user but thats not in the scope of this ticket):
Sending is possible.
This is both as planned IMHO.
When testing with the viktor-gnupg testcertificate I get the new warning message instead of the not very helpful "no name" error in 3.1.26.
But it takes at least 30 seconds to get to that message (the error message in 3.1.26 came up much faster). And when acknowledging the warning it again takes almost as long as before until the message is sent. And in 2 out of 3 tries the Compose Window remained open, so that it looked like the message was not send. Clicking again on Send did not make anything happen, though. And checking the mailbox showed that the mail was sent already.
works. "archive (1).tar.gpg" is now the suggestion on Windows, too. Tested with VS-Desktop-3.1.90.267-Beta
ok, then I'll add the tag for the VSD release after the upcoming one. It is of course relevant for Gpg4win also, but we do not have a dedicated workboard for that (at least not yet)
Nov 9 2023
The nonfunctonal "no date" is gone now in VS-Desktop-3.1.90.267-Beta
But I wonder if we should not address https://dev.gnupg.org/T6683#176429, the text there is not changes in this Beta version.
In GnuPG-VS-Desktop-3.1.90.267-Beta-Standard it works, aside from T6805:
You do not get the new "no x509" message wrongly any more even when quickly sending a mail after restart of Outlook.
But it correctly appeares if no X509 is available.
And the message is configurable via the registry setting HKLM/HKCU \Software\GNU\GpgOL\smimeNoCertSigErr (although I do not know how to add line breaks there, but that is not important).
with VS-Desktop-3.1.90.267-Beta when trying to send a secured mail to the expired Berta X509 testkey I get the confirmation dialog but now the OK button is greyed out:
Nov 8 2023
So should we at the moment only change our backup/migration recommendations? Add %LOCALAPPDATA%/kleopatra and %LOCALAPPDATA%/*rc to the backup?
for comparison, the command without compliance enabled:
Nov 7 2023
On Windows, the notifications are currently configured in kleopatra.kmessagebox, or more accurately, the wish not to notify is configured there:
Nov 6 2023
Nov 3 2023
Works, the confirmation is asked in all 3 cases.
It works for the standard use case where we have keys with one user ID.
For comparison, this is the debugview output if I don't give the passwort on import of a X.509 certificate, were the ü is displayed correctly:
with VS-Desktop-3.1.90.258-Beta the ü is still broken for "Zeitüberschreitung" in the error window which occurs in the context of keytocard:
This may be related to the output PIN retry counter : 3 0 3, i.e. the PUK counter is 0. No idea what this means.
Nov 2 2023
as this really bugs me, I raise the prio.
And add the Kleo tag, as Werner said it might be that Kleopatra is responsible.
Oct 31 2023
works with VS-Desktop-3.1.90.258-Beta
With VS-Desktop-3.1.90.258-Beta I ran again into the last issue with "Wrong PIN". I had not realized that I had entered the PIN wrong before (as you have to enter the PIN several times anyway when generating a new key on a card and you do not get an error message on wrong PIN but instead only a new pinentry window...).
works
with VS-Desktop-3.1.90.258-Beta, CSR creation is now greyed out for RSA2048, while it is offered and works for other algorithms
CSR creation works now (tested with VS-Desktop-3.1.90.258-Beta, Yubikey and OpenPGP card)
Oct 30 2023
hmm, almost. With VS-Desktop-3.1.90.258-Beta I do not get an error any more, a key is generated. But the "vaild until" date is off by one day, it is one day later as the one given at key generation.
works, the secret part is now imported, too, tested with VS-Desktop-3.1.90.258-Beta
works: my brainpool X509 testcertificate is shown as compliant
For the VSD branch it works, VS-Desktop-3.1.90.258-Beta
In VS-Desktop-3.1.90.258-Beta it is "no space left on device" now in the encrypt/verify window.
Oct 23 2023
Oct 20 2023
At the moment we have a green background for the results of a decryption and/or verification, if it was successful.
This does not work with high contrast mode.
and it is also confusing that you can choose the key for signing in Kleopatra, it is displayed with a green check mark but then you run into an error:
Oct 19 2023
yes, fixed
Oct 18 2023
The original issue was to unclear to analyse and it was likely meanwhile fixed. For the other issue see the follow up ticket.
Oct 17 2023
The debug/workaround option works: When the option is checked, opening the msg file will not change its date.
With VS-Desktop-3.1.90.246-Beta I can not import the secret part of the edward.tester@demo.gnupg.com.p12 Testkey (ECC brainpool).
I do not see any error message.
works: installed VS-Desktop-3.1.90.246-Beta with
Oct 16 2023
it was decided to write the encrypted archive with ending .part and only rename it at the end. In this way the users can't think they have a valid encrypted archive
Oct 13 2023
Well I have looked at this ticket and posted a comment. We should talk about if there is anything left to do or not. I suspect that the gpg side is done and I should open one (or probably better several) ticket(s) for the kleopatra side.
works now with VS-Desktop-3.1.90.246-Beta
The error message in Kleo is now (with VS-Desktop-3.1.90.246-Beta) "Broken pipe". But in the linked error protocol you can find the gpg error message "no space left on device". So I would find this message acceptable.
As what I see is similar as what Andre saw, I'll describe it here. Please check if this is relevant.
After the above mentioned Ticket was resolved, I tried the exact same encryption in Kleopatra on the same Test-VM.