Laurent Wacrenier writes:
> Sam Varshavchik wrote:
>
>> I'm pretty sure that this is a valid option in my version of GnuPG 1.0.4.
>> Double check your version. I know it's not documented, so I didn't use it,
>> initially. When I tried to import a secret key, though, it refused to do
>> so, telling me to provide this option. So I did, and it worked.
>
> I havn't found any trace of this option greping the source code of
> released GPG.
>
> I've also looked in the anonymous GPG repository :
>
> - on STABLE-BRANCH-1-0, --allow-secret-key-import is a documented
> new option and shall be used to import secret keys.
> - on HEAD (gnupg 1.1 experimental), theyre is no trace of this
> options
>
> Here is some output from my installation, using FreeBSD freshly
> updated ports :
>
> % LANG=C gpg --version
> gpg (GnuPG) 1.0.4
> Copyright (C) 2000 Free Software Foundation, Inc.
> This program comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions. See the file COPYING for details.
>
> Home: ~/.gnupg
> Supported algorithms:
> Cipher: 3DES, CAST5, BLOWFISH, RIJNDAEL, RIJNDAEL192, RIJNDAEL256, TWOFISH
> Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG
> Hash: MD5, SHA1, RIPEMD160
> % LANG=C gpg --import --no-tty --allow-secret-key-import
> gpg: Invalid option "--allow-secret-key-import"
Ok, so I must be running a newer STABLE-BRANCH build, which has this option.
Does your build take private keys just with --import and --no-tty?
--
Sam
