Try this that is documented:
gpg --homedir /path/to/your/dir --import secring.skr
--
--------------------------------------------
IDG New Media Einar Bordewich
Development Manager Phone: +47 2336 1420
E-Mail: eibo(at)newmedia.no
Lat: 59.91144 N Lon: 10.76097 E
--------------------------------------------
----- Original Message -----
From: "Sam Varshavchik" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 19, 2001 11:38 PM
Subject: Re: sqwebmail 20010318
> Laurent Wacrenier writes:
>
> > Mr. Sam wrote:
> >> Encryption and decryption is implemented by running GnuPG,
appropriately.
> >> Encryption support requires GnuPG 1.0.4, other versions of GnuPG may or
> >> may not work.
> >
> > I'm testing this and had two comments about gpg :
> >
> > * GPG is localized for a dozen of languages, it could be launched
> > with the LANG environment variable set to the content to the LOCALE
> > template file to output localized messages.
>
> Yeah, I need to export that variable. Note that GnuPG's localization is
not
> complete -- it only supports iso-8859-1 and iso-8859-2 charsets for its
> output messages. So, even under other locales you're going to get output
> messages in iso-8859-1. To make things simple, I'm hardcoding --charset
> iso-8859-1, until GnuPG can handle UTF-8 output.
>
>
> > * With gpg 1.0.4, when I try to "Import private encryption key"
> > from a mail, I got the errror :
> > gpg: Invalid option "--allow-secret-key-import"
> > I've never used gpg before, I don't know what's the right option.
>
> 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.
>
> Is anyone else unable to import private keys?
>
>
>
>
> --
> Sam
>
>
