- User Since
- Mar 27 2017, 4:48 PM (339 w, 4 h)
Aug 15 2023
Jul 28 2023
Oct 18 2022
Thanks for the report, since you are using it on the command line and it works I assume that trust-model is set to tofu+pgp? Because in the Test code there is no context flag for tofu+pgp trust model.
Oct 6 2022
Apr 4 2020
Apr 27 2018
@aheinecke maybe recheck with GNUPG 2.2.6 or 2.2.7.
I'm using the kdepim-docker for tests, that is based on KDE Neon, that is based on Ubuntu xenial (16.04), so the version for GnuPG2 is 2.1.11-6ubuntu2. Good to know, that the GnuPG version also matters for this stuff.
Apr 22 2018
Nov 22 2017
Nov 17 2017
data.gpg is fine and data2.gpg shows this wired behaviour. The difference is at the end of file last two bytes : 0040 vs. 0a40.
Initally i took data.gpg to create the base64 encoded version for the message.
Oct 29 2017
Oh sorry i mixed my explanation. I create a normal encrypted file with gpg --encrypt and this file can be decrypted successfully with "gpg -d".
But if I give that encrypted file to gpgme i get the described error, instead of GpgME::Error(0 (Success))).
Oct 27 2017
Oct 10 2017
I think with the SRV entry, I can configure the server in the way I want to....
thanks for the links to documents.
we've setup submisson-address and policy links.
Oct 9 2017
okay, I see. Than I havn't found the documentation for this feature. This is enough for defining a different sever.
I know, that I can't handle all WKD request under one domain for multiple once. But i could make sure, that autoconfig.<domain> would result under another IP adresse so I can handle all of the WKD request at another server. Add a own VirtualHost entry etc.