- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 10 2018
I will disable your account but destroying the account and all data is not possible because this has public interlinked content. The intro page at dev.gnupg.org clearly explains this as welll as the privacy policy linked from the side menu; excerpt
The pages of the Verein shall use a different layout than the general gnupg.org pages.
Please put
Done for gpgme.
Oct 9 2018
I believe this would be a good improvement in user experience
What are the next steps here? i confess i'm a little tired of doing regular checkins on this issue, and i'm sure other people are tired of me nagging. What can we do to move this along?
Done.
This is done now and can be accessed through the config dialog
I think with this warning and default off I can live with this option as it is now.
rev. 1b37aa01cc67d942de06c882fd9d30d39866b111 turns it off by default and even with it enabled only searches the X509 servers if there is no OpenPGP key for this address already available and S/MIME is not the preferred protocol.
Oct 8 2018
Editor fault. The browser's editor is not like Emacs and here o my laptop the backspace key does not work as intended. I guess I was about to write ".. a back signature's usage flag".
what does "back signature's usage tool" mean? can we make an addition to the test suite that ensures that bad signatures will be rejected?
The fix was not fully correct because it considered a back signature's usage tool.
Hi, Has anyone found a reason why that happens. I run into the same behavior on my Windows 10 1803 computer. I have Gpg4win version 3.1.3 freshly installed and dirmngr hangs. Thanks and best regards, Peter
Uhm. As far as I can see this has not moved the file.
Oct 7 2018
ok, feel free to close this ticket then. It's disappointing that there
seems to be no sane, simple, private multi-channel communication
mechanism avaiable cross-platform that GnuPG can rely on.
Oct 5 2018
I moved the location of config.h to a new "conf" subdirectory. This should solve the issue. Thanks for the report.
C++2a will have a <version> header, so some trunk libc++ headers now (indirectly) #include <version>, and on a case-insensitive file-system, when compiling a gpgme source file with "unlucky" -I../../.. switches against such trunk libc++, that can mean that such an #include <version> picks up gpgme's VERSION file.
Sorry, I am not sure whether I understand the problem. Sure we have a file VERSION in the top directory but from where and why is it included? Is that some libc++ includes a file "VERSION.h" and somehow the preprocessor includes the file "VERSION"? IS that specified in a new revision of a standard?