trust keys

[David T-G]

--BfbbJsf3thGkpLcA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Andreas --

=2E..and then akorthaus@web.de said...
%=20
% Hallo!

Hi!  I hope you got some sleep last night ;-)


=2E..
%=20
% gzip -c zip.php | gpg -o data.gpg -a -e -r andreas
%=20
% gpg: Warning: using insecure memory!
% gpg: Datensicherung: skipped: public key not found
% gpg: [stdin]: encryption failed: public key not found

You really shouldn't have to use --default-recipient, so let's do some
digging.

What do you get when you run

  gpg --list-keys --with-colons

(better yet, when the web server does it, to avoid the sort of confusion
we had before; have you been editing the trust on the right copy of the
key?)?  That can help us see the trust level (well, I *think* it can :-)


I've done the same sort of thing with a key for backups only, but that
was under an older version of gpg, so I don't have much detail.


HTH & HAND

:-D
--=20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


--BfbbJsf3thGkpLcA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE8/gyvGb7uCXufRwARAkHEAKCA2cmHXAolUXDxXoghE8oB+KX3gACfTzP5
I15VS5cYSeXAMtztAbKc3/4=
=LZ9g
-----END PGP SIGNATURE-----

--BfbbJsf3thGkpLcA--