possible security hole
Mon, 4 Dec 2000 19:23:01 -0800 (PST)
-----BEGIN PGP SIGNED MESSAGE-----
>briefly explain encoding to base64
It takes binary (and text) input and uses A-Za-z0-9 and = to encode the
data in one long string. It is equivalent to uuencoding. It is a clean
way to bandy about 'dirty' strings. PHP has a function base64_encode()
and base64_decode() to handle this. I recommend you encode the data as
such before handing it off to gpg. Decoding can be done with any number
of tools, one being 'mimencode -u' under linux. uudecode -m can probably
do it too.
> > shell can be tricked depending on $sensitiveinfo to do things you don't
> > intend. Maybe if you base64 encode $sensitiveinfo first you'll be
> > more-or-less immune from shell exploits. From a purely crypto point of
> > view; I don't see anything wrong with this if we assume that
> > $sensitiveinfo is guarenteed to have shell-safe values.
> > > "echo $sensitiveinfo|gpg --homedir /my/home/dir --always-trust -ear
> > > to\@me.com"
> > >
> > > the script runs as nobody
> > > the secret key has never seen the server
> > > the script only encrypts
> > > I don't care who the message comes from I only want the $sensitiveinfo
Cats have nine lives - but sleep through eight of them.
Fingerprint:3B07 518C D76E 572F 7DAA 88A5 9763 835A EA95 4813
finger firstname.lastname@example.org for key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
Filter: gpg4pine 4.1 (http://azzie.robotics.net)
-----END PGP SIGNATURE-----
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to email@example.com