1994-02-08 - Re: What’s a “real encryptor”?

Header Data

From: Matthew J Ghio <mg5n+@andrew.cmu.edu>
To: cypherpunks@toad.com
Message Hash: fffcfad1bd044948bff5f72783c2dda1666e386e86d89f521a5caf512293f3ed
Message ID: <ghK194200awHJYq0de@andrew.cmu.edu>
Reply To: <199402080814.AAA17429@mail.netcom.com>
UTC Datetime: 1994-02-08 22:32:01 UTC
Raw Date: Tue, 8 Feb 94 14:32:01 PST

Raw message

From: Matthew J Ghio <mg5n+@andrew.cmu.edu>
Date: Tue, 8 Feb 94 14:32:01 PST
To: cypherpunks@toad.com
Subject: Re: What's a "real encryptor"?
In-Reply-To: <199402080814.AAA17429@mail.netcom.com>
Message-ID: <ghK194200awHJYq0de@andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain


Xenon, you could make your point a lot clearer if you wouldn't detweil
so much in your posts.  But let me propose a technique that I think
would be what you meant to define as a "real encryptor".

Take a file and encrypt it by taking the first block of data and using
it as a key to encrypt the rest of the file.  Than take the beginning of
the file and encrypt it with RSA.  Therefore, since you need to know the
first block of plaintext to decode the rest of the file, you could only
decode the file if you first decoded the RSA block.  Perhaps some random
padding could also be added, and a random session key inside the RSA. 
The file would have no identifying markers to show what key it was
encrypted with, or what key was needed to decrypt it.  Is this what you
wanted?  I think I could hack that...

And a little flame: Before you put down our software, try writing some
of your own.





Thread