On Wednesday, July 4, 2018 2:25:41 PM CEST Werner Koch wrote:
> We should not try to fix bugs for Cygwin
> given that Cygwin is not offically supported.
I think that you have spent already way too much time with this thread. ;-)
IMO even a
#ifdef __CYGWIN__
# error No you don't
#endif
in a cen
Hello,
Is it possible to verify a signature with critical notations that I
recognize?
I created the signature with:
echo x | gpg --sign --sig-notation !t...@metacode.biz=node-1 > f.sig
Now when I pass this file to gpgme_op_verify I get only summary
GPGME_SIGSUM_RED and status GPG_ERR_BAD_
Hi!
Are you setting the homedir in your code also for the Assuan context?
That might explain the behaviour.
Shalom-Salam,
Werner
--
# Please read: Daniel Ellsberg - The Doomsday Machine #
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpGNpv0Jj7Xp.pgp
Description: PGP si
On Wed, 27 Jun 2018 22:50, tookm...@gmail.com said:
> I have two gpgme contexts, one for openpgp and another for assuan
> commands to the smartcard. Pinentry triggered by the openpgp context
> works perfectly, but any pinentry launched in service of the assuan
> context fails with the error in the
On Wed, 4 Jul 2018 09:11, gni...@fsij.org said:
> The patch is: Don't try to look the error code, but fallback TOR_PORT2
> always.
I don't like this patch because it is not specific enough.
If Cygwin really returns EPERM, than this is a bug in the Cygwin
emulation because all Unix systems (and
On 7/4/2018 9:11 AM, NIIBE Yutaka wrote:
Hello,
john doe wrote:
I'm willing to confirm that but I'm not sure how I would do that!?
I am considering a patch like following. If you can build GnuPG for
Cygwin, you can try. Or, you can ask Cygwin's package maintainer for
GnuPG.
The patch is:
Hello,
john doe wrote:
> I'm willing to confirm that but I'm not sure how I would do that!?
I am considering a patch like following. If you can build GnuPG for
Cygwin, you can try. Or, you can ask Cygwin's package maintainer for
GnuPG.
The patch is: Don't try to look the error code, but fallb
