secring.gpg: file open error

[Treutwein Bernhard]

Hola Noel,

thanks for your clarification.=20

What I wanted to poit out is: If gpg creates the directory .gnupg
from the scratch, as logged to the screen, it might be prepared
that secring.gpg, which is expected in directory .gnupg cannot=20
exist.

[...]
> gpg: /home/treutwei/.gnupg: directory created
> gpg: new configuration file `/home/treutwei/.gnupg/gpg.conf' created
> gpg: keyblock resource `/home/treutwei/.gnupg/secring.gpg': file open =
error
> gpg: keyring `/home/treutwei/.gnupg/pubring.gpg' created
> >=20
> > Is this a bug or a feature ?
> >=20
[...]
>=20
> I think it is totally correct. The program can't lock a file=20
> which don't
> exist. After the first secret key creation or import, all=20
> will be as the
> silk.
>=20


--
	Bernhard Treutwein, IuK, Ref. III A 3
	Bernhard.Treutwein@verwaltung.uni-muenchen.de