how to send an encrypted and signed message from the command line most efficiently without using keyrings

[Neil Williams]

--Boundary-02=_cZvE/7sG+EdOPDL
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Monday 14 Jul 2003 5:57 pm, Ralf Hauser wrote:
> I manage the keys in a database outside gpg's keyrings. What is the best
> format to hand them over to the gpg executable armoured or binary?

I too use a database to hold keys, but I found it useful to have a keyring =
so=20
that keys could be more easily updated from keyservers (revoked keys, new=20
expiry dates etc.) Are you sure that a keyring wouldn't be worth it?=20

It's just another form of storage - I now keep the keyid in the database an=
d=20
the key in a keyring because it's more efficient. No secret keys are requir=
ed=20
for the encryption, (signatures aren't used in my case), Perl (or PHP with=
=20
safe mode off) can access gpg and the keyring via that. Ownership/permissio=
n=20
problems can be overcome if the keyring is kept above the / folder of the=20
public area and suitable settings about warnings added to the gpg conf.

Just my 2p.

=2D-=20

Neil Williams
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
http://www.codehelp.co.uk
http://www.dclug.org.uk

http://www.wewantbroadband.co.uk/


--Boundary-02=_cZvE/7sG+EdOPDL
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA/EvZciAEJSii8s+MRAmjHAJ4ikb+aQwrgFFKi5gZJ70O9TUYc3QCg99WI
0bB9J9qCmqXucQ/xDQn+qn4=
=LGFg
-----END PGP SIGNATURE-----

--Boundary-02=_cZvE/7sG+EdOPDL--