1997-05-27 - CRACKIT.DAT increased to 50,000 bytes.

Header Data

From: DataETRsch@aol.com
To: 3umoelle@informatik.uni-hamburg.de
Message Hash: 2d719567459dd62518e0a2ace877536c4043dd9ad8f69a8373b628357e2113e6
Message ID: <970527174952-1062248409@emout10.mail.aol.com>
Reply To: _N/A

UTC Datetime: 1997-05-27 22:30:35 UTC
Raw Date: Wed, 28 May 1997 06:30:35 +0800

Raw message

From: DataETRsch@aol.com
Date: Wed, 28 May 1997 06:30:35 +0800
To: 3umoelle@informatik.uni-hamburg.de
Subject: CRACKIT.DAT increased to 50,000 bytes.
Message-ID: <970527174952_-1062248409@emout10.mail.aol.com>
MIME-Version: 1.0
Content-Type: text/plain


In a message dated 97-05-26 19:38:43 EDT, you write:

<< The test file is only 836 bytes long.  Could you please post a file
 consisting of, say, 50.000 space characters encrypted with the same
 key? >>

50,000 with the same key? Sure. A new file will be posted under the same name
as the previously posted one. The same key will be used to encrypt the file
before posting. Contest details will be reposted. By the way, a simple
VSA2048 decryption program will be released soon so that there will not exist
a need to develop one to decrypt the file. Also, the contest expiration date
has been extended to July 1st, 1997. Good luck!

Again, random XOR is *not* the only method used to encrypt data. In fact,
random XOR could be left out. Consider examining VSACMInternal (in
INTUNIT.PAS) and VSACMProcessOperation in LIBUNIT.PAS for additional
information.

Regards,

Jeremy Yu-Ramos
DataET Research






Thread