OpenPGP vs inline PGP

[John B]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 10 July 2003 18:03, Robin Lynn Frank wrote:
> On Thursday 10 July 2003 15:22, Neil Williams wrote:
> > > > Variety is the spice of life.
> > >
> > > We don't share the same view.  To me, it works or it doesn't.  Its
> > > secure or it isn't, etc.   I think I'll wait until this has been iron=
ed
> > > out a bit more before trying to deploy it.
> >
> > You need a challenge. Go to it!
> >
> > Don't you enjoy this admin lark anymore?
>
> I have a real-world job function as well.  This has become the second 16
> hours of each workday.
>
> I don't need a challenge.  I need results.  The only reason I even
> attempted this was to have a way to verify these @#$%&!& detached
> signatures.  I shouldn't really clutter up this list with this any furthe=
r.

  Now you're just getting nasty. What makes you think you're the only one w=
ith=20
a "real-world job function"? There's plenty of folk tackling this situation=
=20
you have, on their own, and sticking with it, who also have jobs. Hell...*I=
*=20
have absolutely no experience doing admin work, but since I'm the *only*=20
person that uses this home system with SuSE 8.2 on it, I had to figure out=
=20
how to get the opengpg plug-in to work on my kmail by myself...and a few=20
questions in an SuSE mailing list. One thing no one seemed to know about=20
(including myself of course), was that I was always trying to make the=20
plug-in 'active', plus I'd never typed in a 'name' (all this in the kmail=20
security setup section, gui), so I tried once more with a name and didn't=20
activate it...HA! I now have openpgp compatibility. (I was rather proud of=
=20
myself for doing it on my own, heh)

  John=20
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/DhujH5oDXyLKXKQRAhKXAJ9Fj2l1zmAXjruy6xV75MnDNTNWtwCcDzUq
gEMCVYLF12MEgg7zJ3LJ6io=3D
=3DckmW
=2D----END PGP SIGNATURE-----