As expected it was a very clear bug. We assign a NULL pointer to a string and then use that string.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 19 2018
Thank you for the report and the logs! A minor note: For future reports please leave the priority on "Needs Triage" we use this as a marker for issues no developer has looked at previously.
To avoid releasing incomplete tarballs this release should also be built from the source package and no longer from the git tag.
Jun 18 2018
I'm seeing this as resolved. It's a design decision by the pinentry-gtk maintainer. pinentry-qt is the default pinentry for windows and there pasting works, as you have confirmed.
We did not have more reports about this so I'm resolving it here.
This is still true even after the latest changes to GpgOL not to require Kleopatra or GPA through the UIServer protocol. The details dialog / search still uses Kleopatra or GPA as a fallback.
I'm closing this as a duplicate of T3459
Two more reports in the Gpg4win forums. Still can't reproduce it. I've asked for debug output.
I'm closing this as duplicate of T3459
Has long been in testing. I think it is improved now and CRL's also work.
The fix for this was released with Gpg4win-3.1.1. Forgot to update this task.
I will try to figure out what exactly triggers the firewall. This should really be fixed as it leads to a bad "first contact" with Gpg4win, especially as we do more locate-keys nowadays so the question pops up randomly for the user.
I'm changing this to wishlist as I don't think anymore that we have something new here. When working with unsigned files the user has/had already the same problems as described in the issue.
(Wishlist does not mean that it will be ignored.)
The change was released with Gpg4win-3.1.2
The changes were released with Gpg4win-3.1.2.
Gpg4win-3.1.2 was released yesterday.
Forgot to comment. Yes what is in the video is also what I thought.
Fix is released in Gpg4win-3.1.2
Fix is released in Gpg4win-3.1.2
The problem is complicated because we would have to parse each multipart/mixed mail before we can know that the mime structure looks that way.
Jun 17 2018
Support was removed.
Jun 15 2018
This was released with Gpg4win-3.1.1
Jun 12 2018
Jun 11 2018
Here is what we have now. We decided explictly not to offer a "yes I want to do something less secure" button as we think that using Unsigned S/MIME Mails is avoidable. Also we want to be more secure by default then Outlook. From a User Experience standpoint a "Yes more convenient but less secure" button basically educates users to always select that button.
Jun 8 2018
Jun 7 2018
Jun 1 2018
Ok You could notice it because if the year changes there was no "blue" selected date in the current page.