NewPG is now GnuPG 1.9
Adrian 'Dagurashibanipal' von Bidder
avbidder@fortytwo.ch
Sat Aug 9 07:08:04 2003
--Boundary-02=_MIIN/54vRkjtEjN
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline
On Friday 08 August 2003 23:09, J=FCrgen Botz wrote:
> Werner Koch wrote:
> > gpg2 has been changed to use libgcrypt but secret key management is
> > still done by itself and not by gpg-agent. However, --use-agent is
> > the default now and we support the new OpenPGP smartcards.
>
> Could you explain what you mean by this for those of us who are
> not very familiar with the code base? I mean, superficially this
> statement doesn't make sense, if key management isn't done by the
> agent what good is the agent?
As far as I understand it, the agent at the moment takes care of requesting=
=20
the password from the user. Which will probably break all application using=
=20
secret key operations and managing the pw themselves.
I think --passphrase-fd should automatically imply --no-use-agent. (Or do y=
ou=20
already do this?). When the agent does secret key handling: is there a way =
to=20
continue using --passphrase-fd (and have gpg supply the pw to the agent)?
greetings
=2D- vbi
=2D-=20
featured product: GNU Privacy Guard - http://gnupg.org
--Boundary-02=_MIIN/54vRkjtEjN
Content-Type: application/pgp-signature
Content-Description: signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iKcEABECAGcFAj80ggxgGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h
aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjUmbWQ1c3VtPTVkZmY4NjhkMTE4NDMyNzYw
NzFiMjVlYjcwMDZkYTNlAAoJEIukMYvlp/fW5LoAn0L3yqrM/6QpeuXtV3tvbtFt
lTAaAKCR8nBwHmIEs2jxTsZF1Pj3GXay0w==
=VPQM
-----END PGP SIGNATURE-----
Signature policy: http://fortytwo.ch/legal/gpg/email.20020822?version=1.5&md5sum=5dff868d11843276071b25eb7006da3e
--Boundary-02=_MIIN/54vRkjtEjN--