On Mon, 30 Jul 2012 21:15, ciprian.crac...@gmail.com said:
* implement your own fake `gpg-agent` which I have no ideea what
actually implies;
Don't do this.
* implement your own fake `pinentry` which would be much simpler
as it only has to implement the assuan protocol; but you'll
On Tue, 31 Jul 2012 12:54, ciprian.crac...@gmail.com said:
Not a good idea, because GnuPG 2.1 requires the gpg-agent and won't see
any private key stuff.
Not necessarily if you use the `--batch`, `--no-use-agent`, or
`--no-tty` (or a mix of the I'm not sure right now, but the manual
On Tue, Jul 31, 2012 at 6:35 PM, Werner Koch w...@gnupg.org wrote:
On Tue, 31 Jul 2012 12:54, ciprian.crac...@gmail.com said:
Not a good idea, because GnuPG 2.1 requires the gpg-agent and won't see
any private key stuff.
Not necessarily if you use the `--batch`, `--no-use-agent`, or
On Tue, 31 Jul 2012 17:53, ciprian.crac...@gmail.com said:
First of all I would really have liked the tool to not just ignore
the `--no-user-agent` flag and bail out...
That would make migration for user of 2.0 to 2.1 too complicate. We try
to do the migration as smooth as possible.
Hell all,
I am trying to pipe my passphrase to unlock the key. my problem is
like this, when I use git
to sign a tag gnupg ask for the passphrase and i need to pipe the passphrase.
I try
echo my long passphrase | git tag -s 1.0.0.42 -m 'version 1.0.0.1'
however it did not work.
i also try
