IMDMP: SOURCE CODE RELEASE ANNOUNCEMENT

[Mullen Patrick]

DataETRsch at aol.com sez:
>Comment: "Why the hell is the file size limit 258 bytes off? What, are keys
>kept in file headers?"
>Reply: Keys are NOT stored in headers. The 258 (actually 256) byte header is
>used to store certain IMDMP special security option settings. The header is
>itself secured using a 128-bit encryption code.

[My apologies in advance for not having looked at your web site]
What security option settings are in the header?  What kind of security would
be lost by knowing its contents?  I assume there is some sort of risk, hence
the encryption of the header.  When is the header decrypted?  Where is it
decrypted to?  If it is decrypted into memory before use, one could read
the plaintext straight from memory.  Is the key for the header static (same
for all files), or changing?

I assume that when the source code becomes available, you will disclose the
structure of the file header...

How will the source code be distributed?

Thank you for your time.

Patrick Mullen

Patrick.Mullen at gsc.gte.com (preferred email for non-list email)





_______________________________________________________________________________
From: DataETRsch at aol.com on Fri, Jan 10, 1997 0:46
Subject: IMDMP: SOURCE CODE RELEASE ANNOUNCEMENT
To: cypherpunks at toad.com

Hello,

In compliance with the large volume of source code requests DataET Research
has been receiving, the undocumented Pascal source code of UDCM (containing
the IMDMP encryption algorithm) will be released in approximately one month.
Also, the shareware version of UDCM completely complies with ITAR since only
56-bit keys are allowed. The registered version allows 2048-bit keys. The
registered version can only be sold within the U.S. and Canada. Also:

IN RESPONSE TO THE FLAME MAIL DATAET RESEARCH HAS RECEIVED:

A "comment:" is from a flame mail. A "reply:" is DataET Research's reply to
the comment.

Comment: "What do you mean by 'extensive research'."
Reply: Benchmark tests. Source code comparisons. Documentations of other
algorithms. "Applied Cryptography".

Comment: "Yah, okay, since when is a DLL not royalty-free?!"
Reply: Read some component catalogs. Go search the Internet.

Comment: "That stupid line about 140 function bloats your ad."
Reply: Is this constructive criticism or what?

Comment: "What the hell does DLL size have to do with cost-effectiveness?"
Reply: Upload time. Disk creation time. Minimal archive size increase.

Comment: "I've never even heard of IMDMP before. Is this a joke?"
Reply: UDCM (IMDMP) came out January 1st, 1997. How do you think successful
companies start anyway, with millions of dollars upfront? DataET Research is
a relatively new company.

Comment: "What kind of industry standard is IMDMP above?"
Reply: 128-bit encryption. Average DES is 128. PGP tops 1024. IDEA goes at
128. RSA the same. Full security IMDMP is 2048-bit. Any other questions?

Comment: "Any bonehead can tell that 256 bytes is 2048 bits."
Reply: Does anybody out there feel insulted?

Comment: "Why does IMDMP need sub-algorithms? Is there something wrong?"
Reply: Sub-algorithms of IMDMP are basically algorithm modes. There is
nothing wrong with IMDMP's structure. Why don't you see what sub-algorithms
are for yourself? Go try out UDCM:
http://members.aol.com/dataetrsch/udcm.html.

Comment: "What algorithm doesn't process both binary and ASCII?"
Reply: Go search the Internet for one. You'll find many dinky ones.

Comment: "What algorithm doesn't allow multiple encryption layers?"
Reply: Go search the Internet for one. You'll find many dinky ones.

Comment: "Who says IMDMP doesn't have any back-doors or magical keys?"
Reply: What more do you want us to prove? The source code will be out in
about a month.

Comment: "Why is there a dumb 2,147,483,390 file size limit?"
Reply: It has do with 2^32 DOS file pointer long integer variables. You
developers should know that.

Comment: "Why the hell is the file size limit 258 bytes off? What, are keys
kept in file headers?"
Reply: Keys are NOT stored in headers. The 258 (actually 256) byte header is
used to store certain IMDMP special security option settings. The header is
itself secured using a 128-bit encryption code.

Comment: "What the do you mean by 'file specific unique encryption'."
Reply: For the idiot who sent this message to us: Why don't you download UDCM
V2.0 and view its documentation for yourself?

Comment: "Isn't IMDMP illegal?!"
Reply: The version of UDCM (IMDMP) being distributed on the Internet, the
shareware version, allows only 56-bit keys. The registered version allows
2048-bit ones. The registered version is only sold within the U.S. and
Canada.

Comment: "I want the damn source code to IMDMP now. How do we know for sure
that IMDMP is better than DES and all the others you mentioned?"
Reply: Wait one month please.

Jeremy K. Yu-Ramos
President
DataET Research
Data Engineering Technologies

------------------ RFC822 Header Follows ------------------
Received: by mail.ndhm.gtegsc.com with SMTP;10 Jan 1997 00:46:36 -0400
Received: from toad.com by delphi.ndhm.gtegsc.com with SMTP;
          Fri, 10 Jan 1997 5:45:24 GMT
Received: (from majordom at localhost) by toad.com (8.7.5/8.7.3) id RAA20172 for
cypherpunks-outgoing; Thu, 9 Jan 1997 17:15:06 -0800 (PST)
Received: from emout18.mail.aol.com (emout18.mx.aol.com [198.81.11.44]) by
toad.com (8.7.5/8.7.3) with ESMTP id RAA20163 for <cypherpunks at toad.com>; Thu,
9 Jan 1997 17:14:52 -0800 (PST)
From: DataETRsch at aol.com
Received: (from root at localhost)
	  by emout18.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0)
	  id UAA11665 for cypherpunks at toad.com;
	  Thu, 9 Jan 1997 20:14:20 -0500 (EST)
Date: Thu, 9 Jan 1997 20:14:20 -0500 (EST)
Message-ID: <970109201419_1207964145 at emout18.mail.aol.com>
To: cypherpunks at toad.com
Subject: IMDMP: SOURCE CODE RELEASE ANNOUNCEMENT
Sender: owner-cypherpunks at toad.com
Precedence: bulk