Key keeps showing unknown trust

[MFPA]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



On Thursday 12 February 2015 at 12:26:57 PM, in
<mid:87d25fz566.fsf at vigenere.g10code.de>, Werner Koch wrote:



> Nope.  You will never find a secring.kbc.  2.1 uses
> secring.gpg only in this ways:

> If secring.gpg exists and the file .gpg-v21-migrated
> does not exist, the secret keys from secring.gpg are
> imported to private-keys-v1.d/ and .gpg-v21-migrated is
> created.

> The migrated keys are stored in a special intermediate
> format below private-keys-v1.d/ and converted to the
> final format as soon as you use that key and thus have
> to enter the passphrase (which is needed for
> re-encryption).

Thanks for the correction. I was confusing secret and public keyring
files.

- --
Best regards

MFPA                    mailto:2014-667rhzu3dc-lists-groups at riseup.net

The problem is not that we're paranoid;
it's that we're not paranoid enough.
-----BEGIN PGP SIGNATURE-----

iQF8BAEBCgBmBQJU3fA0XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwYOUIAK72KDYIHggs/XpuncfBA/xd
LSX7HcbSXitVVjDX3tkdG8YLxHDZcA/X3cp5rh2idUWVQ/yJv0mFs1Cvoqvrj6ov
rhCxMJmPklkXhFDTsTiYI7H2Z3/EVAMoPjU1Bf/RmzmCMla8HOSu9fPughxCEQCL
FovqNbKPPCYKzTpf9MFB8kP6R2OfuAsIFydaY7WBEAq3P417B8S8xSPu2jCg6SHC
DF/E5y3fDIdFHAogoBZNHRU6ZSbZ2sEdRWrjHfwLv750D6cScYyYAnTUGMYdnTdP
FSE5SsBFUQ1KQCP7vBOd4XojmS7HuC/NrTtJj7bqAyR4IIuxDcts0bn1IA7FytqI
vgQBFgoAZgUCVN3wO18UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45B4AAQDtocKsGjtX6XxVOCa466S10Bjg
LMN7aNZksf/bM8l6zQEAqcGDOJ9x2zLm+oZDIGqv/sGNoRMAnVVQSNLS1imWBAo=
=xIda
-----END PGP SIGNATURE-----