[Announce] GPGME 1.1.6 released
Alon Bar-Lev
alon.barlev at gmail.com
Sat Jan 12 20:28:49 CET 2008
On 1/12/08, Werner Koch <wk at gnupg.org> wrote:
> On Sat, 12 Jan 2008 10:21, alon.barlev at gmail.com said:
>
> > All I ask is to stop breaking the interface.
>
> As Marcus already explained, there is no interface break. gpg2 is an
> entirely different program and we have always declared that it is only
> _mostly identical_ to the standalone gpg.
>
> This is one of the reasons why we promised to maintain both programs.
> (The other reason is that GnuPG-1 is easier to build and more portable
> to older and pre-POSIX systems).
I don't understand what you are talking about, from gpg2 man page:
--passphrase-fd n
Read the passphrase from file descriptor n. Only the
first line will be read from file
descriptor n. If you use 0 for n, the passphrase will be
read from stdin. This can only
be used if only one passphrase is supplied. Note that
this passphrase is only used if
the option --batch has also been given. This is
different from gpg.
--passphrase-file file
Read the passphrase from file file. Only the first line
will be read from file file.
This can only be used if only one passphrase is
supplied. Obviously, a passphrase
stored in a file is of questionable security if other
users can read this file. Don't
use this option if you can avoid it. Note that this
passphrase is only used if the
option --batch has also been given. This is different from gpg.
--passphrase string
Use string as the passphrase. This can only be used if
only one passphrase is supplied.
Obviously, this is of very questionable security on a
multi-user system. Don't use this
option if you can avoid it. Note that this passphrase
is only used if the option
--batch has also been given. This is different from gpg.
So unless you release gpg3, removing these parameters breaks your interface.
Alon.
More information about the Gnupg-devel
mailing list