Re: New Encryption Idea

<a.manansala@attbi.com> wrote in message
news:1119017644.683004.147190@g44g2000cwa.googlegroups.com...
> Well, using the current system your "private keys" likely rests on
> someone else's hardware.

Still wrong. Repeating the same lie will never make it truth.

> The problem of distributing files is equivalent to that of distributing
> credit cards, serial numbers, etc.

Wrong. With credit card if the number is leaked there is noticable usage not
by the owner. With serial number leakage the same. With the leakage of these
recovery can be performed. With the leakage of a cryptographic key the
information protected will leak, an entirely different problem.

>
> However, it is possible to use one file to create a completely new file
> privately after the hardware has been received by the user.
>
> Basically it goes like this, the user enters in some data. The program
> uses the data to determine a random number. The random number is used
> with the old file to generate an entirely new random file.

This would immediately break the randomness of the file, and drop any
security you pretended to have completely through the floor.

>
>> > The key is basically information you have to type in anyway for
>> > authentication.
>>
>> ... AES is usually not used for authentication outside of a MAC
>> construction. Public Key algorithms are typically what you use to
>> authenticate transactions for they have something MACs do not...
>>
>>
>
> Well there is only one key that is "typed" in in my system and that is
> the authentication key.

the rest of the keys in the system are free for the taking.
                Joe
Received on Thu Sep 29 21:44:32 2005