Re: Continue Work on the One-Time Pad? - adacrypt



On Wed, 25 Jul 2007 07:39:40 -0700, AdaCrypt
<austein.obyrne@xxxxxxxxxxxxxx> wrote:

My question is fair and unselfish. Is there a case for continuing
Major Joseph Mauborgne's work on the one time pad so as to get this up
and running as a modern realisation of what he and Vernam had in
mind. I think it is incumbent on us all in Sci crypt to cooperate
towards that end given that we are the beneficiaries of today's
technology that they did not have. There is no technical problem
whatever to doing this but it is realised that many readers may
mistake the motive as being plagiaristic on my part and object to the
idea out of sentiment.

That alone will not stop it going ahead but it would be better if
everybody chipped in with their personal crypto experience in a joint
effort. The final cipher can be renamed by the group in a way that
will retain the original identity.

The basics of a one time pad are trivially easy to implement in modern
technology: output = input XOR bytestream. Its problems are nothing
to do with the basic implementation, they are things like:

- the secure generation of large quantities of true random data.
- the secure distribution of that data.
- the secure erasure of that data after use.

For instance, the third one requires that any possible copies of the
OTP data be erased from all memory, swap files, system backups,
archives, CDs, DVDs and so forth. That is a far from trivial task in
many operating systems and has very little to do with the basic
operation of the OTP itself.

As with much cryptography the devil is in the details, which in this
example involves things like digging into exactly how Windows, Linux,
MacOS etc. operate their swap files and how to securely erase data
from them.

I will do the work of creating the cipher as a vector based (it is
already nearly complete in fact) and will present it to the readership
for ongoing refinement and approval. - Adacrypt
I would advise against using your vector based idea. We know that it
triples the size of any cyphertext and it should be clear to you by
now that new cyphers proposed by amateurs do not have an easy time.
Experience has shown that amateurs are prone to make amateurish
mistakes and in cryptography any mistakes are a source of weakness.

The OTP is provably strong. You have not yet shown us that your
vector idea is actually an OTP; if it isn't then it will almost
certainly be weaker.

rossum

.



Relevant Pages

  • Re: Erasing an OTP file on a SD card.
    ... I implemented One Time Pad under AES 256 bits CBC ... In our system you can't use OTP alone. ... secure than other systems, but in the worst case it has no advantage ...
    (sci.crypt)
  • Re: ensuring total security
    ... The algorithm itself is secure, ... your one time pad will (very ... you get to if you think about 100% security. ... of the encryption tools out there will provide all the security you need. ...
    (comp.security.misc)
  • Re: Total protection for your software against crack
    ... engineer or pirate it! ... one time pad to decrypt the original program and run it. ... secure and impossible to reverse engineer. ... Secure, and Intractable; by the time your application starts (or ...
    (sci.crypt)
  • Re: Hardware True Random Number Generator design / concept
    ... >>That is not one time pad. ... >>with unlimited computing power that OTP offers. ... Nobody can crack a properly used one-time pad, even with infinite ... resources and infinite time. ...
    (sci.electronics.design)
  • Re: Use of Pseudo Random Generators for One Time Pad?
    ... can it be used to create One Time Pad. ... > The following link demonstrates the use of YARROW for OTPs. ... I don't know why you insist on calling this OTP. ... just a poorly implemented stream cipher. ...
    (sci.crypt)

Quantcast