1995-01-12 - Knowing Something’s Encrypted

Header Data

From: Jeff A Licquia <jalicqui@prairienet.org>
To: cypherpunks@toad.com
Message Hash: 5d89a4244f9fe319f87e07c21332047cc97662b28cf151967a93afb5e829d7a5
Message ID: <Pine.3.89.9501120950.B3383-0100000@firefly.prairienet.org>
Reply To: N/A
UTC Datetime: 1995-01-12 15:16:58 UTC
Raw Date: Thu, 12 Jan 95 07:16:58 PST

Raw message

From: Jeff A Licquia <jalicqui@prairienet.org>
Date: Thu, 12 Jan 95 07:16:58 PST
To: cypherpunks@toad.com
Subject: Knowing Something's Encrypted
Message-ID: <Pine.3.89.9501120950.B3383-0100000@firefly.prairienet.org>
MIME-Version: 1.0
Content-Type: text/plain


Maybe I'm missing something here.  If I am, please bonk me.

Here's a simple method for knowing that some data you received is encrypted:

1.  Require a specific method (we'll use PGP in this example).

2.  When a message comes in, check for a PGP format message.  If you 
really wanted to get fancy, you could parse the PGP header a bit to make 
sure the data was really encrypted.

It's true that this isn't "cryptographic" in the sense of testing the 
ciphertext itself, but it should work for the practical goal of enforcing 
a "must be encrypted" rule.

----------------------------------------------------------------------
Jeff Licquia (lame .sig, huh?)   |   Finger for PGP 2.6 public key
jalicqui@prairienet.org          |   Me?  Speak for whom?  You've got
licquia@cei.com (work)           |     to be kidding!






Thread