Slashdot Mirror


One-Time Pad From Caltech Offers Uncrackable Cryptography

zrbyte writes "One-time pads are the holy grail of cryptography — they are impossible to crack, even in principle. However, the ability to copy electronic code makes one-time pads vulnerable to hackers. Now engineers at the California Institute of Technology in Pasadena, have found a way around this to create a system of cryptography that is invulnerable to electronic attack. Their solution is based on a special kind of one-time pad that generates a random key through the complexity of its physical structure, namely shining a light through a diffusive glass plate."

192 comments

  1. Impossible? by Sockatume · · Score: 2, Insightful

    Couldn't you just steal the plate?

    --
    No kidding!!! What do you say at this point?
    1. Re:Impossible? by barlevg · · Score: 4, Informative

      That's generally the only way to crack a true one-time pad: steal the pad.

    2. Re:Impossible? by Sockatume · · Score: 1

      Yeah, that's supposed to be what this problem solves, though, if I'm reading it right. Haven't they just taken a step back to having a physical OTP on your desk/in your shoe?

      --
      No kidding!!! What do you say at this point?
    3. Re:Impossible? by barlevg · · Score: 4, Informative

      Right: it sounds like it's TWO MATCHED OTPs (or, rather, one-time slabs), so Eve would need both Alice's slab AND Bob's slab to crack the communication. And if Alice and Bob are both in physical possession of the slabs, then Eve is better off using $5 cryptography to get at the message. The issue, of course, is that one-time pads aren't exactly practical, because, by definition, they're one-use-and-then-destroy. If you use an OTP more than once, it becomes vulnerable to cracking.

    4. Re:Impossible? by Hans+Adler · · Score: 5, Informative

      Who would have thought that the f... article addresses this devilishly ingenious workaround?

      "And even if Eve steals the glass, they estimate that it would take her at least 24 hours to extract any relevant information about its structure.

      This extraction can only be done by passing light through the glass at a rate that is limited by the amount of heat this creates (since any heating changes the microstructure of the material). And the time this takes should give the owners enough time to realise what has happened and take the necessary mitigating actions."

    5. Re:Impossible? by Anonymous Coward · · Score: 0

      That's $5 cryptanalysis you insensitive clod!

    6. Re:Impossible? by L4t3r4lu5 · · Score: 4, Informative

      Eve is better off using $5 cryptography to get at the message.

      Rubber Hose Cryptanalysis Just FYI.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    7. Re:Impossible? by Sockatume · · Score: 1

      Right, it's difficult, not impossible. You need a sufficiently large time window to steal both pads and duplicate them.

      --
      No kidding!!! What do you say at this point?
    8. Re:Impossible? by rherbert · · Score: 5, Funny

      What if you drop the glass plate? You're sure to crack it then.

    9. Re:Impossible? by Corbets · · Score: 1

      That said, I think this light-based encryption solution is brilliant in the lab.

    10. Re:Impossible? by bugnuts · · Score: 1

      Just one of them is sufficient.

      At least it's not the size of a manuscript anymore, so you don't need a guy with a handcuffed briefcase on one hand and a SMG on the other.

    11. Re:Impossible? by Sockatume · · Score: 1

      I suppose my error here is letting the title's "uncrackable cryptography" override the summary's "invulnerable to electronic attack", which is absolutely true.

      --
      No kidding!!! What do you say at this point?
    12. Re:Impossible? by Anonymous Coward · · Score: 1

      Sarah Michelle Gellar?

    13. Re:Impossible? by slim · · Score: 4, Informative

      No, the two devices don't match. Each device contains a different several GB of random numbers (or I suppose, random transformations), encapsulated in the structure of the glass.

      The two owners meet, and using both their devices, produce a "combined key". The combined key can be stored in a public repository. The shared OTP can be extracted from the combined key using either device.

      The two parties exchange confidential data encrypted with bytes from the OTP until the OTP is all consumed. Then they must meet up again to create a new OTP.

      There's nothing novel about the cryptography. What might be novel is the physical properties of the device used to allow someone to carry their personal list of random numbers around.

    14. Re:Impossible? by Sockatume · · Score: 1

      If I'm reading it right (which is a shaky assumption) one pad is sufficient to decipher messages sent to that recipient, but both would be necessary to read messages going both ways.

      --
      No kidding!!! What do you say at this point?
    15. Re:Impossible? by mbone · · Score: 1

      Who would have thought that the f... article addresses this devilishly ingenious workaround?

      "And even if Eve steals the glass, they estimate that it would take her at least 24 hours to extract any relevant information about its structure.

      This extraction can only be done by passing light through the glass at a rate that is limited by the amount of heat this creates (since any heating changes the microstructure of the material). And the time this takes should give the owners enough time to realise what has happened and take the necessary mitigating actions."

      Right. Note that this implies that this technique should only be used for messages that have an effective lifetime of 1 day.

      "Attack at dawn" - yes

      "Attack on Sunday" - not so much

    16. Re:Impossible? by SuiteSisterMary · · Score: 1

      You could accomplish the same thing by having Alice's pad contain half of the full OTP, only the odd numbers, and Eve having only the even numbers.

      Even better, use a third person with a third OTP to determine if the next sequence goes to Alice or Eve (i.e. Bob's pad is a string of numbers; if the number is odd, the next digit comes from Alice's pad, if even, Eve's pad.)

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    17. Re:Impossible? by SpectreBlofeld · · Score: 1

      And it seems to me that things like the wavelength of light used would have to be matched exactly as well.

      Light of different wavelengths refract differently. Blue refracts more than red, for instance.

      The two communicating parties could agree on one (or several) exact wavelengths to use with their plates. Anyone who intercepts the plate, without knowing what wavelength was used, wouldn't be able to replicate the process used to generate the key, unless they tried them all, I guess - but even then they wouldn't know how many wavelengths were used.

    18. Re:Impossible? by slim · · Score: 2

      I don't think we share a vocabulary on this topic. None of that made sense.

    19. Re:Impossible? by slim · · Score: 1

      It's an implementation detail as to whether you use a different pad in each direction, though I don't really know why you would do.

      The principle is well understood -- if you both know a secret list of numbers that's as long as your plaintext, you can exchange messages confidentially.

      The challenge, which these guys claim to address, is how to get to the point where you both have the secret list of numbers, and can be confident that nobody else has it.

      Once you have that confidence, I don't see why you wouldn't use the same pad in both directions. In fact it's equivalent (since the numbers are random, having one list of length 2x is equivalent to having two lists of length x).

    20. Re:Impossible? by rot26 · · Score: 1

      It's only a One Time Pad if you use it only once. Just sayin'.

      --



      To ensure perfect aim, shoot first and call whatever you hit the target
    21. Re:Impossible? by slim · · Score: 1

      Sure, never use the same byte twice.

      But, using the same pad in both directions:

      > Hello Alice -- encrypts with pad[0..11]
      < Hello Bob -- encrypts with pad[12..21] ... and so on.

      Using two pads:
      > Hello Alice -- encrypts with pad[0][0..11]
      < Hello Bob -- encrypts with pad[1][0.9] ... and so on.

      Equivalent, in terms of the randomness, the one-time-ness of the numbers, and the necessity that both sides have access to all the pads.

    22. Re:Impossible? by bws111 · · Score: 1

      The 'one time' refers to the key, not the physical device. Just don't re-use the same portion of the data from the device.

    23. Re:Impossible? by Anonymous Coward · · Score: 0

      It doesn't imply that at all. It implies that you should check if the device is stolen at least every 24 hours, and that if you detect that the device is stolen, you should assume that the information is compromised and change plans.

      It is a large improvement over regular cryptography in these terms, as you now have a relatively simple way to detect if this is stolen (which you don't have with copying of keys), and you have 24 hours from theft to compromise, instead of instant compromise.

      This is, of course, assuming that their claims are correct, and there is no way to extract the structure faster, and the structure is truly completely random, with no bias. If the former fails, the 24 hours fail; if the latter fails, this is all bogus. I'd unfortunately find it more likely that there is some unknown structure in here (ie, not full randomness) than that there is a way to extract faster.

    24. Re:Impossible? by Jane+Q.+Public · · Score: 1

      "The issue, of course, is that one-time pads aren't exactly practical, because, by definition, they're one-use-and-then-destroy."

      First off, the kind of OTP situation discussed in TFA isn't even a very common concern: using forensic tech to recover the key from memory. Either you'd have to have some kind of computer with virtually no garbage collection of free memory, or the computer would have to be seized immediately after having sent the message. Just not something that is going to happen every day.

      But to address your own comment: you must keep in mind that almost ALL modern encryption has the problem that a key must be generated and distributed. Public-key or asymmetrical cryptography is great for certain things, but even that relies on keeping a key secret (although the secret key does not have to be distributed).

      The point is: as long as your OTP key remains secret (if the key is pretty random and of course if it is used only once), then it is inviolable. There are many extremely practical uses for such technology.

      For example: you can dispense with the "one time only" requirement if you simply want little more than a "keeping the kid sister's prying eyes off my email" level of security. You can dispense with the key distribution requirement if you have agreed upon a common external changing key source. And so on.

      The "not very practical" designation simply means you haven't been using your imagination. common kind of OTP, nor is it a very practical one. The subset they describe is made by adding characters to a message from a random source to obscure the message.

    25. Re:Impossible? by Jane+Q.+Public · · Score: 1

      Wow. I don't know how that sneaked in there. The final paragraph should simply have been:

      "The 'not very practical' designation simply means you haven't been using your imagination."

    26. Re:Impossible? by GumphMaster · · Score: 1

      This approach suffers badly in the face of lost messages or messages sent simultaneously in both directions. If a message from A to B is lost and not received by B then B will send their next message to A using the same part of the OTP as the lost message: an eavesdropper could then have two different messages encoded with the same key. Similarly, if A drafts a message to B, and B to A, at the same time then they will use at least part of the same key.

      --
      Patent litigation: A doctrine of Mutually Assured Destruction... in which everyone seems willing to push the button
    27. Re:Impossible? by Man+Eating+Duck · · Score: 1

      > Hello Alice -- encrypts with pad[0..11]
      < Hello Bob -- encrypts with pad[12..21] ... and so on.

      Using two pads:
      > Hello Alice -- encrypts with pad[0][0..11]
      < Hello Bob -- encrypts with pad[1][0.9] ... and so on.

      This is completely irrelevant to your point, but you have some zero-indexing errors and a fencepost one in your examples :)
      --
      Your friendly neighbourhood pedant

      --
      Are you a grammar Nazi? I'm trying to improve my English; please correct my errors! :)
    28. Re: Impossible? by Anonymous Coward · · Score: 0

      Who wouldn't love her one their arm for an evening of spying?

  2. Moon Runes by codemaster2b · · Score: 5, Funny

    So, the message can only be read by the light of a moon the same shape and season that the message was written on?

    --
    And over there we have the labyrinth guards. One always lies, one always tells the truth, and one stabs people who ask t
  3. Certs are complicated enough by Anonymous Coward · · Score: 1

    You try explaining to my computer illiterate relatives that they need to buy these special glass plates for their computer to communicate with the bank.

    1. Re:Certs are complicated enough by slim · · Score: 1

      Just embed the glass in a credit card sized gizmo, and put a reader in laptops.

    2. Re:Certs are complicated enough by Hentes · · Score: 1

      Exactly, the main problem with OTP isn't that you have to store the key in memory, but that sending it to the other party is complicated. These guys have completely missed the point.

  4. Obligatory XKCD by stewsters · · Score: 1
    1. Re:Obligatory XKCD by Anonymous Coward · · Score: 0

      Not applicable. One time pads are used for encrypting transmissions, not storage. If you transmit the key before the message, you can make sure that the key is not compromised and only then encrypt and send your message. The person or system transporting the key can not reveal the message and the person or system transporting the encrypted message can not reveal the message because the key is transmitted separately.

    2. Re:Obligatory XKCD by Anonymous Coward · · Score: 0

      Yeah, but they can throw a black bag over your head and take your glass plate. Once it works they no longer need you alive.

    3. Re:Obligatory XKCD by smallfries · · Score: 3, Funny

      This seems a little bit more appropriate.

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
    4. Re:Obligatory XKCD by NatasRevol · · Score: 1

      I think you guys broke xkcd.com

      --
      There are two types of people in the world: Those who crave closure
    5. Re:Obligatory XKCD by andy.ruddock · · Score: 1

      If you transmit the key before the message, you can make sure that the key is not compromised and only then encrypt and send your message.

      How do you make sure that the key is not compromised?

      --
      God: An invisible friend for grown-ups.
    6. Re:Obligatory XKCD by Immerman · · Score: 1

      Test it every 23 hours - supposedly it takes at least 24 hours with specialized equipment to duplicate the glass key without damaging it.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    7. Re:Obligatory XKCD by Anonymous Coward · · Score: 0

      Depends on the application and the attack scenarios that you want to protect against.

    8. Re:Obligatory XKCD by andy.ruddock · · Score: 1
      Except parent said

      One time pads are used for encrypting transmissions, not storage.

      which seems to be to be referring to OTPs in general, not this specific implementation.

      --
      God: An invisible friend for grown-ups.
  5. Fundamental problem by Anonymous Coward · · Score: 0

    If you know the clear text and the cypher text, you know the key and can reuse it. No system where the machine handling the clear text and the cypher text can be compromised is guaranteed to be secure, no matter how fancy your one time pad construction is.

    1. Re:Fundamental problem by barlevg · · Score: 1

      That's where the "one-time" part of the "one-time pad" comes in: you're only supposed to use an OTP cypher once before destroying it.

  6. Physical vulnerability by Anonymous Coward · · Score: 3, Funny

    Uncrackable glass plates? Forget cryptography, you should get into the windshield business!

  7. Re:Not too long until an iceberg attack is reveale by Sockatume · · Score: 5, Informative

    That's not the case with a properly used one-time pad. Normally you break a cipher by finding correlations due to the repeated use of a finite encryption key on different parts of a comprehensible plaintext. If either the message is random, or the encryption key is random and nonrepeating, then the message cannot be deciphered.

    Unless you steal the pad, or force the user to repeat it.

    --
    No kidding!!! What do you say at this point?
  8. Shades of WarGames... by Zelig · · Score: 1

    SIR! TURN YOUR KEY!

  9. SGI had something along these lines sometime ago. by auric_dude · · Score: 1

    SGI had something along these lines http://www.google.com/patents?vid=5732138 https://en.wikipedia.org/wiki/Lavarand but links http://lavarand.sgi.com/ don't work too well now.

  10. Re:Not too long until an iceberg attack is reveale by Joce640k · · Score: 5, Insightful

    Nope. The OTP is truly unbreakable.

    The only problem with it is that you need to secretly transmit the pad to the recipient. How do you do that? With a one-time-pad...?

    --
    No sig today...
  11. Got it backwards by Monty845 · · Score: 4, Insightful

    A one time pad is impossible to crack in theory, but may be crackable if the method for generating the pad is flawed. Creating true randomness is a tricky proposition, and I don't see why its safe to believe that "shining a light through a diffusive glass plate" will generate true randomness.

    1. Re:Got it backwards by Anonymous Coward · · Score: 3, Informative

      On a photon-by-photon basis, refraction, diffraction, and anything less than total reflection are all quantum mechanical processes. It doesn't get more random than that. Sending photons through a partially transparent mirror has been a standard trick for generating random bits quantum mechanically for at least a decade that I know of. It sounds like this is the same principle.

    2. Re:Got it backwards by ledow · · Score: 2

      But to be a useful one-time pad, don't you have to be able to repeat the results to decode the message?

    3. Re:Got it backwards by Corbets · · Score: 2

      But to be a useful one-time pad, don't you have to be able to repeat the results to decode the message?

      No. You have to distribute matched pads - one to the encoder, one to the decoder.

      Thus, if someone gets his or her hands on a copy of the pad, decryption is trivial.

    4. Re:Got it backwards by Anonymous Coward · · Score: 0

      Do they change the glass plate after every use?

    5. Re:Got it backwards by jittles · · Score: 1

      But to be a useful one-time pad, don't you have to be able to repeat the results to decode the message?

      No. With a proper random pad generation algorithm, you could never ever reproduce the exact same pad in two places, or at two separate times. You generate the pad once and use some other method (such as couriers) to deliver the pads to the people that need them. You also need a way to guarantee that the courier did not tamper with, sell, or copy the original pad. If you transmit via internet, you would use some previously arranged cryptographic exchange.

    6. Re:Got it backwards by slim · · Score: 1

      I don't think this is about quantum phenomena. The glass has a randomised construction, but it needs to be a repeatable source of randomisation.

      The process seems to be: Both parties meet, and feed some random data into a process which uses both their glasses and produces a few GB of "combined key". Alice's glass and Bob's glass are different. But either can be used to extract the OTP from the "shared key".

    7. Re:Got it backwards by hcs_$reboot · · Score: 1

      This remind me of an old Office file where the MS copyright text was encrypted thanks to a simple XOR value (a few bytes). (There is also that funny story at the time of a Linux tool that only needed the `-d` option to decipher a whole XLS, without providing any password...). Anyway, what was said at the time: while XOR encryption seems very week, if the key itself is as long as the text to be encrypted, and if the key is based on reliable random values (and the key is kept secret), it is indeed a very strong encrytion.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    8. Re:Got it backwards by JustinOpinion · · Score: 1
      This work seems to be based on this high-profile paper from 2002:
      Ravikanth Pappu, Ben Recht, Jason Taylor, Neil Gershenfeld Physical One-Way Functions Science 2002, 297 (5589), 2026-2030, doi: 10.1126/science.1074376

      Abstract: Modern cryptographic practice rests on the use of one-way functions, which are easy to evaluate but difficult to invert. Unfortunately, commonly used one-way functions are either based on unproven conjectures or have known vulnerabilities. We show that instead of relying on number theory, the mesoscopic physics of coherent transport through a disordered medium can be used to allocate and authenticate unique identifiers by physically reducing the medium's microstructure to a fixed-length string of binary digits. These physical one-way functions are inexpensive to fabricate, prohibitively difficult to duplicate, admit no compact mathematical representation, and are intrinsically tamper-resistant. We provide an authentication protocol based on the enormous address space that is a principal characteristic of physical one-way functions.

      Basically, they create a slab of epoxy with a bunch of glass micro-spheres randomly distributed within it. When you shine light through it, the multiple refractions/scattering events lead to a complicated path for the various light beams, which interfere to generate a complicated light-speckle pattern on the other side. This multiple-scattering process is of course deterministic, but in practice it is so complicated that it is not feasible to reverse-engineer the internal structure of such a material. (In fact, the method exploits coherent scattering, and because the light-detector can only measure the amplitude (and not the phase) of the scattered light, the problem is formally 'ill-posed': there is no way to invert the coherent scattering data to obtain the material structure. Instead such problems can only be approximately solved with iterative processes; this can be made arbitrarily difficult by increasing the number of scattering entities (glass beads in this case)...) This is analogous to mathematical one-way functions: in principle you can crack them, but it takes an infeasible amount of time.

      Ultimately the 'randomness' (uniqueness of a slab) comes from the inital preparation of the slab: you're basically 'freezing in' the random Brownian motion of the micro-particles. Thermal noise is a pretty robust source of randomness.

      These slabs are neat in the sense that you can use them to generate multiple pads. A different illumination condition (incident angle, or light pattern) generates a new one-time-pad (see the paper for a discussion of 'how different' the illumination condition needs to be in order to yield a uncorrelated/unique one-time-pad), so one idea is for people to carry a single physical token and use it to generate different OTPs for different communications channels they care about.

      These schemes are not without their downsides, of course, but it's a neat idea to use a physical structure (rather than mathematical function) to generate pseudo-random numbers. (Thes slabs don't require a battery to maintain their state; one could image secure ways of generating two identical slabs at fabrication time, and then giving them to the two parties; etc.)

    9. Re:Got it backwards by ledow · · Score: 1

      So at what point aren't "matched pads" repeats of the original pads, or devices which would repeat the results of the original pad?

      This is my point - these pads aren't "random", because if they were they'd perform differently in two different devices. In which case, their results are surely trivially capturable and, thus, reproducible if you digitally capture the performance of a single example?

      It's the old "if you can read it, so can anyone else with the same equipment, and so can you 'fake' it with sufficient knowhow" DRM problem

    10. Re:Got it backwards by Impy+the+Impiuos+Imp · · Score: 1

      Creating true randomness is a tricky proposition, and I don't see why its safe to believe that "shining a light through a diffusive glass plate" will generate true randomness.

      They claim it passes statistcal analysis tests for true randomness.

      I would imagine such tests would also be useful to SETI to detect data transmission distinguishible from random noise. In this way, no decoding is needed to tell if there is information there. A concerted effort could bury non-random bits here and there, one out of millions, and get away with it, but not a general encrypted blob, much less just encoded data nobody is trying to hide.

      In any case, it's 10gb, enough for a lifetime of text messages (the complete works of Shakespeare, IIRC, on Project Gutenberg, is only ~80 meg.)

      Which then suggests the need for a metric -- how long should they trust a provably secure mechanism against standard spy techniques? Even both ends being locked in silos might not warrant a 10 year lifespan, much less security-through-obscurity of a field agent. Hell, just transmitting large blocks of 100% mathematically random data is a red flag. "One-time pad in use! Something very interesting going on here!"

      --
      (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
    11. Re:Got it backwards by slim · · Score: 1

      On some device when the two glass owners meet:

      pad = generateRandomBytes(many GB)
      combinedKey = encodeToCombinedKey(pad, glass1, glass2)
      publishToInternet(combinedKey) // shared key i

      Later, to send a message:

      chunkOfPad = decryptSharedKey("http://repository/combinedKeyId", glassAlice)
      cipherText = xor(plaintext,chunkOfPad)

      To decode:

      chunkOfPad = decryptSharedKey("http://repository/combinedKeyId", glassBob)
      plaintext = xor(ciphertext,chunkOfPad)

      There may be some novelty in the way the combinedKey is constructed (probably not).
      The main novelty is in the properties of the glass (hence this being in an optics journal, not a cryptography journal).

    12. Re:Got it backwards by slim · · Score: 1

      Do they change the glass plate after every use?

      No, but once you've used a chunk of randomness, you don't reuse it, and eventually the glass plate is "finished".

      TFA:

      ... it ought to be possible to generate a terabit of randomness from a single cubic millimetre of diffusing glass with higher-resolution equipment.

      And even thought this can only be used once, the slabs can be easily reset by heating the glass to change its microstructure at which point Alice and Bob must meet again to create a new set of combined keys.

    13. Re:Got it backwards by SuiteSisterMary · · Score: 1

      The pads are randomly generated, not random. Each pad needs to be longer than your message. No part of the pad is ever reused; if you have the first half of a pad, you can decrypt anything encrypted with that half, but it tells you absolutely nothing about the second half of the pad, because it's all random, not an algorithm. If you have the cleartext, you could not reverse-engineer the pad from it, and even if you could, you couldn't use that to determine the rest of the pad.

      Here's how it works.

      You generate a random pad. In the old days, when the term originated, it was literally a pad of paper with random letters.

      The sender and receiver must have identical copies of each pad. For example, lets say you generate a pad for each day of a year, and distribute a copy to each embassy. So each pad has a master number, 1 through 365, and each embassy has it's own in that series.

      Each and every one of those copies must be physically secure. If they are, the communications are unbreakable. If they are not, the communications are not.

      In the above example, each day's pad might be on, in this day and age, a secure USB key, shink wrapped, with anti-tamper foil. If, in daily inspection, any key is missing, appears to have been altered in any way, the shrink wrap scratched or warped, whatever, every embassy is immediately directed to burn their copy of that pad. Once the pad is used, or at the end of the day, each copy is burned to prevent accidental reuse.

      It's part of a cryptographic system, not a complete methodology in and of itself. And it's no different than the idea that, say, public/private key encryption is secure until you misplace your private key.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    14. Re:Got it backwards by mbone · · Score: 2

      Creating true randomness is a tricky proposition, and I don't see why its safe to believe that "shining a light through a diffusive glass plate" will generate true randomness.

      They claim it passes statistcal analysis tests for true randomness.

      That is meaningless (there is no test for true randomness, just tests of whether or not various forms of non-randomness are present), and if they truly believe that passing various tests for randomness is sufficient then there may be no hope for them.

      Hell, just transmitting large blocks of 100% mathematically random data is a red flag. "One-time pad in use! Something very interesting going on here!"

      I have heard that certain locations send megabits / sec of random data continuously, at all times, just so that certain other locations can't tell when encrypted traffic is being sent. Certainly that technique is being used (at a lower bit rate) by the various "number stations" out there.

    15. Re:Got it backwards by Anonymous Coward · · Score: 0

      If you can securely distribute the pads, why not just distribute the message in the same manner?

    16. Re:Got it backwards by Solandri · · Score: 1

      Something like this was already tried 10 (15?) years ago. It was a bunch of crystals embedded into a plastic base. You shone a light onto it and depending on the angle, the pattern of crystal faces which reflected back would change. The inventors were marketing it as a replacement for the magnetic stripe on your credit card. The magnetic stripe on your card can easily be scanned and duplicated. The crystals were easy to scan, but near impossible to duplicate if you're comparing the reflection from multiple angles. So slap one on a credit card and you have a physically uncopyable unique identifier. They'd gotten as far as some credit card companies doing limited trials with it. I haven't heard about it since so I guess that means it failed for some reason.

    17. Re:Got it backwards by JesseMcDonald · · Score: 2

      You don't actually need to encrypt the shared key; a simple XOR of the pads from each piece of glass will do:

      combinedKey = xor(glassAlice, glassBob)
      publishToInternet("http://repository/combinedKeyId", combinedKey)

      For Alice to send a message:

      combinedKey = getFromInternet("http://repository/combinedKeyId")
      glassBob = xor(combinedKey, glassAlice)
      cipherText = xor(plaintext, glassBob)

      For Bob to decode:

      plaintext = xor(ciphertext, glassBob)

      The result of the XOR only tells you whether a given bit is the same or different between the two pads, which, by itself, doesn't tell you anything about either pad, so the XOR can be made public. Combined with one of the pads, however, it allows you to infer the value of the other so that you can send your message. Normally each party would just have a copy of the same pad, but this approach gets around the difficulty of creating two pieces of glass with precisely equal (random) optical properties.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    18. Re:Got it backwards by Jamu · · Score: 1

      Usually time constraints. Alice might want to communicate securely to Bob over an extended period while separated, but they can physically meet beforehand. For example, you want a secure link with a military drone.

      --
      Who ordered that?
    19. Re:Got it backwards by suutar · · Score: 1

      *shrug* Without tests, how can you assess the randomness of any bit source? If this passes the same tests as sources we currently accept, then it's at least as good given what we currently know. When we learn more stuff, it may change.

    20. Re:Got it backwards by suutar · · Score: 1

      probably decided the extra cost of making the cards outweighed the losses due to magstripe fraud.

    21. Re:Got it backwards by Carnildo · · Score: 1

      Hell, just transmitting large blocks of 100% mathematically random data is a red flag. "One-time pad in use! Something very interesting going on here!"

      In theory, there are three things that are 100% mathematically random:

      1) Random data, such as the output of a hardware random number generator.
      2) Encrypted data. One of the criteria for an encryption algorithm is that the output is indistinguishable from randomness. If you can tell the two apart, you can gather information about the plaintext.
      3) Compressed data. If you can tell it from a stream of random bits, that represents a redundancy you can use to compress it even further.

      In practice, you can tell the three apart, because compressed data usually comes with a header or other uncompressed structure, and almost nobody sends large random numbers around.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  12. Leaving traces by Anonymous Coward · · Score: 0

    Paper pads had the same problems that computers do today, that aren't so trivially dispensed with using the premise "when used correctly."

    It's nearly impossible to "use correctly" a one-time pad on any computer or other electronic device. The moment you put the key into RAM, or worse, FLASH, you are leaving remnants that can allow the key to be recovered. It's a relatively complex process to recover old, erased data from memory, but it is done, every day.

    You would need to create your ciphered data, then completely destroy the PC or electronic device used to create it, in order to have a perfectly unbreakable message.

    1. Re:Leaving traces by h4rr4r · · Score: 1

      You cannot recover old data from memory. Hard disk maybe, but RAM is volatile. Turn off the machine and within seconds it will be gone.

      Recovering data from a hard disk can also be made impossible. Simply encrypt the entire device. Without the key no recovery can occur.

    2. Re:Leaving traces by 50000BTU_barbecue · · Score: 1
      I thought so too.

      http://en.wikipedia.org/wiki/Cold_boot_attack

      Back in the day on my VIC-20, I could see that data stayed for a few seconds but that was probably 6T SRAM with humongous feature sizes.

      --
      Mostly random stuff.
    3. Re:Leaving traces by weilawei · · Score: 1

      Clearly, you've never used a can of compressed air held upside down and sprayed on the RAM to cool it down. Why, that might even allow someone to mount an attack! Don't spout off BS when you're several years behind the news...

    4. Re:Leaving traces by Anonymous Coward · · Score: 0

      Abstract Contrary to popular assumption, DRAMs used in most modern computers retain their contents for seconds to minutes after power is lost, even at operating temperatures and even if removed from a motherboard. Although DRAMs become less reliable when they are not refreshed, they are not immediately erased, and their contents persist sufficiently for malicious (or forensic) acquisition of usable full-system memory images. We show that this phenomenon limits the ability of an operating system to protect cryptographic key material from an attacker with physical access. We use cold reboots to mount attacks on popular disk encryption systems — BitLocker, FileVault, dm-crypt, and TrueCrypt — using no special devices or materials. We experimentally characterize the extent and predictability of memory remanence and report that remanence times can be increased dramatically with simple techniques. We offer new algorithms for finding cryptographic keys in memory images and for correcting errors caused by bit decay. Though we discuss several strategies for partially mitigating these risks, we know of no simple remedy that would eliminate them.

      Source: https://citp.princeton.edu/research/memory/

      There are some very illustrative videos there to show just what is possible. Enough to know that hard drive encryption is no cryptographic silver bullet.

    5. Re:Leaving traces by Anonymous Coward · · Score: 1

      Like most concepts in security, once you have physical access, all bets are off on keeping your information secure. The point of this technology is to protect the data while in transit to the recipient.

    6. Re:Leaving traces by Anonymous Coward · · Score: 0

      Delete and override each block (e.g. 512 bytes) of the OTP as soon as it has been used for decryption. Any cold boot attack which could restore partially used and hence not yet deleted keys would also reveal the decrypted message as it also would be still in memory.

    7. Re:Leaving traces by h4rr4r · · Score: 1

      Wow for a whole few seconds!

      You could just then over write ram on shutdown. That would get rid of that attack.

      Clearly you are just spouting BS you read without thinking.

  13. Grammar Police Alert by mamer-retrogamer · · Score: 0

    way round

    So just how round are these one time pads? Way round.

    --
    Schrödinger's cat is not amused—maybe.
  14. Is it new? by 140Mandak262Jamuna · · Score: 3, Interesting
    I thought there was a similar technique used in WWII for communication between Churchill and FDR. Identical pairs of phonograph records were kept on both sides. Both sides would play a pair simultaneously, or as nearly as they could. Then technicians would use electronic delay and tune it so that they both are synchronized. Then add voice communication to the recorded sounds and transmit. On the receiving side they subtract the phonograph record sound and get the voice alone back. Each pair of phonograph records would be a one time pad. The encryption and decryption was analog, not digital. But apart from that, adding a "noise" as encryption and subtracting identical noise for decryption would be very similar to what the article is describing.

    Was it really used? Or am I hazily recalling some spy novel stuff from Irwin Wallace or Alistair MacLean and mistaking it for real history?

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:Is it new? by barlevg · · Score: 1

      Looks like it was called POTUS-PRIME, but I haven't yet found any more information than what's on that page.

    2. Re:Is it new? by 140Mandak262Jamuna · · Score: 1

      It was real , my memory has not been addled. Not yet.

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    3. Re:Is it new? by mbone · · Score: 1

      That is indeed how the WWII "scrambler" phones worked, but that was not viewed as nearly as secure as a one time pad (required for all messages dealing with Enigma decrypts) and the Germans did decode at least some scrambler phone communications.

      The cryptographic trouble is that the inherent correlations of the human voice are still present, just overlaid by noise, and you can use that knowledge to extract the signal (the voice) from the noise. It did prevent idle eavesdropping, which I think was more the point.

    4. Re:Is it new? by slim · · Score: 1

      There's nothing new about one-time pads, and your story is plausible (I think I've heard it before).

      OTPs have definitely been used in real spycraft. People were literally issued with a book of random numbers, to be very closely guarded.

      What's new here is the way of storing OTPs so that they can't unobtrusively be copied.

    5. Re:Is it new? by 140Mandak262Jamuna · · Score: 1

      Yes, plain scrambler was insecure. I just read the wiki about the project. They did a lot more than simply adding noise. They did some pulse code modulation, frequency shifting etc.

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    6. Re:Is it new? by 140Mandak262Jamuna · · Score: 2

      In what way guarding a block of glass different from guarding a telephone book? Easiest one time pads are to get two copies of the same yellow pages. The caller specifies a page number. The receiver turns to that page. Ignore all alphabets and collect all the phone numbers write them down in sequence. You got a one time pad.

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    7. Re:Is it new? by AvitarX · · Score: 1

      It sampled every 20 milliseconds, and sent that as a number. I think you could call it digital.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    8. Re:Is it new? by bill_mcgonigle · · Score: 1

      POTUS-PRIME

      Great, now I have to imagine Roosevelt with Peter Cullen's voice saying, "Allied Forces, roll out."

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    9. Re:Is it new? by Anonymous Coward · · Score: 0

      Real or not, such a system is described in Cryptonomicon.

    10. Re:Is it new? by slim · · Score: 1

      In what way guarding a block of glass different from guarding a telephone book?

      You can trivially borrow a telephone book, copy what you need, then return it without the owner noticing.

      TFA:

      And even if Eve steals the glass, they estimate that it would take her at least 24 hours to extract any relevant information about its structure.

      This extraction can only be done by passing light through the glass at a rate that is limited by the amount of heat this creates (since any heating changes the microstructure of the material). And the time this takes should give the owners enough time to realise what has happened and take the necessary mitigating actions.

      ... and their abstract...

      Benefits of volumetric physical storage over electronic memory include the inability to probe, duplicate or selectively reset any random bits without fundamentally altering the entire key space

      Easiest one time pads are to get two copies of the same yellow pages. The caller specifies a page number. The receiver turns to that page. Ignore all alphabets and collect all the phone numbers write them down in sequence. You got a one time pad.

      "Easiest", but not unbreakably secure in the manner of a truly random OTP.

    11. Re:Is it new? by thoromyr · · Score: 1

      easy does not mean secure. First hint, your phone numbers do not represent a random distribution of numbers. Better than nothing? Sure. Would it prevent me from cracking the encrypted message? Yes, but I'm not a cryptographer. The lack of any meaningful randomness would permit analysis and cracking.

    12. Re:Is it new? by JaredOfEuropa · · Score: 3, Informative

      Those numbers aren't truly random and cryptanalysis can be applied to them. Especially if the attacker knows you're using the Yellow Pages (security through obscurity).

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    13. Re:Is it new? by david_thornley · · Score: 1

      What an interceptor would get was a very noisy conversation, which could be recorded and carefully listened to by multiple people multiple times. It wasn't very secure because people are very good at getting meaning out of noisy conversations. IIRC, the conversation wasn't really pleasant for FDR or Churchill, so adding too much noise would become impractical.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    14. Re:Is it new? by suutar · · Score: 1

      and so do I. Bastard :)

    15. Re:Is it new? by quarterbuck · · Score: 1

      A phonebook if it includes area codes would have a repeating pattern. Similarly, since numbers do not usually have multiple leading zeros, multiple 1s etc. that is an additional source of non-randomness.
      The resulting message wouldn't be truly random. So statistical attacks would decrypt such a message without ever needing this made-up one time pad.

      --
      http://slashdot.org/submission/1062723/Cheap-mobile-data-plan?art_pos=2
  15. Expansion/Contraction by Anonymous Coward · · Score: 0

    Hope they keep this glass plate at a constant temperature, lest it shrink/grow changing your OTP key.

    1. Re:Expansion/Contraction by Anonymous Coward · · Score: 0

      So I should not let one of those homeless windshield cleaner guys clean my OTP glass plate then huh.

  16. Re:Not too long until an iceberg attack is reveale by barlevg · · Score: 1

    The key here is that the OTP is a physical object (actually, TWO physical objects) that is not easily replicated (since it's surface imperfections that give rise to the randomness in the pad). So Eve would have to be in possession of Bob's pad at the time Alice was transmitting the message in order to decipher the message. If I'm understanding this correctly.

  17. "New Cryptography" - I don't think so. by bradgoodman · · Score: 2

    One time pads are uncrackable only if the pad is truly random and perfectly secretive. Everyone has known this for years. All they have done here was to create a new way to generate random numbers. Any new way of generating random numbers would/could be equally applied to OTP crypto.

  18. Nothing is impossible to crack... by Anonymous Coward · · Score: 0

    ... bruteforce still works (but, of course it could take a lot of time...)

    1. Re:Nothing is impossible to crack... by slim · · Score: 3, Informative

      No, against a one-time pad, bruteforce won't work, because the key is never re-used so you've no basis to know that any output from your decryption is more valid than any other.

      The first 1024 bytes of Hamlet, XOR'd with 1024 truly random bytes, is indistinguishable from random bytes.

      XOR that with the same bytes again, and you get 1024 bytes of Hamlet back.
      XOR it with most random streams of bytes, and you'll get something that looks equally random.
      XOR it with a particular different list of bytes, and you get 1024 bytes of Moby Dick.
      XOR it with another list of bytes, and you get a version of Hamlet in which "Bernardo" is replaced with "Slashdot". ... and as an attacker, you've no way of knowing which one of those, if any, was the original plaintext.

    2. Re:Nothing is impossible to crack... by damnbunni · · Score: 1

      Actually no, brute force specifically doesn't work against OTP cryptography.

      That's kind of the whole point of OTP.

      At most you can determine the maximum length of the message. However, if you determine it's an eight word message there is absolutely no way to determine WHAT those eight words are without the key.

      You also can't determine if the message is really eight words, or if it's five words banana popsicle meow.

      Even theoretically infinite computing power will not suffice to crack a one time pad if it's used properly.

    3. Re:Nothing is impossible to crack... by Anonymous Coward · · Score: 0

      That may not be the kind of brute force that the other AC had in mind.

    4. Re:Nothing is impossible to crack... by Anonymous Coward · · Score: 0

      Maybe I'm missing something but has otp key an infinite lenght? I don't think so. If key has a fixed length, you should use it multiple time to encode a long message so in a case you get full hamlet, in another case you get 1024 bytes of moby dick and then garbage.

      Am i wrong?

    5. Re:Nothing is impossible to crack... by slim · · Score: 3, Interesting

      You are wrong.

      The "one time" in "one time pad" means you never use a piece of key twice. The OTP needs to be as long (or longer than) the plaintext, and when you've used up your OTP, you need to get together and share a new one.

      You can make an OTP last longer by compressing before encrypting, or by using OTP encyption to exchange temporary keys, to be used with other encryption methods.

      Clearly you *could* re-use your OTP, perhaps starting from the beginning when you run out of bytes. But each time you do that you weaken your security.

    6. Re:Nothing is impossible to crack... by Anonymous Coward · · Score: 0

      OTP is even immune against brute-force.

      Brute-forcing works only when you can detect a successfull decryption. Your chances of finding "ATTACK AT DAWN" are exactly the same as "ATTACK AT DUSK" or any other meaningfull message and you can't decide which one is the original message.

    7. Re:Nothing is impossible to crack... by suutar · · Score: 1

      Sort of. The only form of brute force that works on a one time pad is the rubber hose kind; if the pad is actually random there is no indication whatsoever in the ciphertext whether it's a phone book or Hamlet; any message with the right number of bits is equally possible. So you have to get information not contained in the ciphertext.

    8. Re:Nothing is impossible to crack... by Anonymous Coward · · Score: 0

      If you re-use it, it's technically not a one-time pad anymore anyway.

  19. Re:Not too long until an iceberg attack is reveale by Joce640k · · Score: 2

    If you can meet up to exchange a piece of glass you can also exchange USB drives (or whatever) full of random numbers. It's just as secure as this method.

    The innovation here is that that nobody can make a copy of the piece of glass.

    Or is it...? If Bob can create a OTP using the glass then so can Eve. All she does is sneak into his hotel room when he's asleep, generate his pad using his crystal and make a copy of it.

    I fail to see how this is more secure than simply exchanging USB keys.

    --
    No sig today...
  20. Re:Not too long until an iceberg attack is reveale by smallfries · · Score: 5, Insightful

    The real key here is that there is no advantage to the device at all.

    In the cryptographic protocol that the authors (all physicists) believe to be novel, but which every cryptographer is aware of:
    1. The authors have a perfectly secure channel (separate from the one established in the protocol).
    2. They exchange as much information over that channel as the device stores.
    3. The later established channel can only use that number of bits.

    For real excitement they xor together their OTPs. Sorry guys but this is called a pre-shared key and the crypto world is quite aware of it. Good luck with the window dressing getting you past the PC of a physics venue.

    --
    Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
  21. I wonder... by Anonymous Coward · · Score: 0

    why they wouldn't use existing technologies (light-sensitive polymer inks, for instance) to make pairs of OTPs which both:
    a) Have to be registered at a central authority to "recognize" the other station, and,
    b) Destroy themselves as they're read, prohibiting copying.

    Alice and Bob both grab a disk at CIA headquarters, Bob is sent to the American Embassy in Elbonia, and registers his OTP from that location with the State Department. Then, it's locked to that terminal, with his credentials, and the OTP wipes itself out as he goes...

    Mallory would have to copy the OTP pad before first use, break into the VPN, and use Bob's credentials to send a forged message. Other than an over-the-shoulder camera or TEMPEST interception, I'm not sure how she could get snoop copies, other than HUMINT.

  22. The question is by nickol · · Score: 1

    The question is: how soon this diffusive glass will become a forbidden substance ?

  23. Random is hard. by DarthVain · · Score: 2

    I can't remember which book it was, maybe Cryptonomicon, but more likely The Ultra Secret, but it had some interesting stories about both the allies and axis having a hard time at this.

    They used various ideas to try and "make" randomness into their one time pads. However all of these things had to be done by a person, as this was more less before the advent of computers (well just before anyway). One such method had to do with using a deck of cards. However crackers were able to even find patterns among the people using (aka their tendencies in drawing cards or other such devices), so occasionally personnel would have to be "shuffled" themselves to different areas.

    If you think about it, a computer is generating it from an algorithm, which may be complex, but is essentially a set of rules that can be determined. I have heard of some that try to utilize some sort of seemingly random event that is naturally occurring. However even these can be modeled over time.

    The key really is to make it difficult enough so that the code breaker cannot really use the information obtained effectively. Unfortunately usually this involves additional overhead on the part of the cryptography as well, which of course reduces its usefulness as well.

    Which is exactly why the allies took such great pains to prevent the axis from finding out that their unbeatable code had been broken. As it was they got complacent and lazy, and had they known, they would have changed their codes, and the allies would have to start all over again.

    1. Re:Random is hard. by thoromyr · · Score: 4, Interesting

      I have heard of some that try to utilize some sort of seemingly random event that is naturally occurring. However even these can be modeled over time.

      A good post, but I'm not sure you understand hardware based random number generation. At least one way to do it is have a small amount of radiactive material. Although it decays predictably in the long term (half life) it is random in the short term. By measuring the radioactive decay truly random numbers can be obtained.

      Can you model this? Sure, but your model will either be a software based random number generator or it will be a hardware token. In either case it will *not* be the item in question at the time in question and will not allow you to determine what numbers were generated.

      No system is foolproof, but all the interesting cracks in cryptography that I'm aware of come through side channels or demonstration that a method was not truly random. Human card shuffling is certainly not random -- not only is the process controlled by the shuffler, but there are distinct non-random patterns to it that allow stage magicians to take a stack decked that is shuffled and still produce the desired result.

      I think my favorite side channel attack was picking up the attenuated signal from the unencrypted side of a cryptograpy machine -- the British didn't have to crack the encryption used by the French embassy, they just read the plain text!

      OTP are sexy and cool because they provide unbreakable encryption. As long as they are generated correctly (truly random) and distributed without tampering or exposure. The first is hard enough, but distribution on any scale means that not all of them will be free of tampering and exposure.

    2. Re:Random is hard. by Anonymous Coward · · Score: 0

      Your idea about random numbers is somewhat flawed.

      It can be used in OTP cases, but on the more common forms of cryptography you need a pseudo-random number generator, not a true random number gererator. Why ? Because the sequence of numbers generated must be reproduced in order to decrypt the message....

    3. Re:Random is hard. by DarthVain · · Score: 1

      I guess I was more referring to software not hardware random generation. Like when you call a random function to generate a number for you to use.

      I remember reading about two methods YEARS ago probably in some CS class or something. One involved weather patterns (i think), and another involved electrical current, and both involved slices of time, to produce values that were "seemingly" random. The point was, in both cases, you could over time figure out and model something to get most of the general weather phenomenon or the fluctuations of electrical current over whatever it was they were using. Never heard about the radioactive method. Presumably something not too exotic or hard to come by if it is to be used for anything reasonable.

      Anyway it is all pretty interesting stuff. It is pretty amazing they were able to do what they did back in the day without the aid of computers.

      That said, a OTP is pretty tough to beat no matter what. When I saw the headline, I smirked a bit. Ya, computers and the availability of electronic code *might* make it easier to crack. However that is more likely the fault of the implementation, not the actual code itself.

      Case in point. The WWII carrier pigeon letter that was found in an excavated chimney in England last year. It had a short code sequence. The Internets (including slashdot) were all a buzz with trying to crack it to see what it actually said. This went on for months, and no one could do it. People were speculating that it was a OTP, and thus "Impossible" to crack. When all it took was some dude in Peterborough, Ontario, Canada who dragged out an old RAF recon code book they had in their attic and translated the whole mess in about 20 minutes.

      Heck the fact that even in WWII the allies would parachute guys behind enemy lines with a bunch of CARRIER PIGEONS for recon and reporting still blows my mind. Gives signal interception a whole new ring (Hawks?)! Pretty soon you have an escalating Hawk war on your hands! LOL I read that manual even had references to signal redundancy, in that each message was sent twice, just in case it got eaten by a Hawk, or as in this case stuck in a chimney flu!

    4. Re:Random is hard. by Rich0 · · Score: 0

      A good post, but I'm not sure you understand hardware based random number generation. At least one way to do it is have a small amount of radiactive material. Although it decays predictably in the long term (half life) it is random in the short term.

      How do you KNOW that it is random in the short term? The fact that you cannot currently predict its behavior does NOT necessarily mean that it is random. If it were truly random, then why is there a long-term predictable behavior?

    5. Re:Random is hard. by Anonymous Coward · · Score: 0

      How do you KNOW that it is random in the short term? The fact that you cannot currently predict its behavior does NOT necessarily mean that it is random. If it were truly random, then why is there a long-term predictable behavior?

      Why? It is because they are truly random. Each single outcome is just as likely as every other, which means that in the long run, the outcomes will occur pretty much equally often (give or take).

    6. Re:Random is hard. by rot26 · · Score: 1

      Lava Lamp. Back in the day, all we had to look at on the web was the cambridge coffee pot, the SGI random-number-generating lava lamp and the application to date Sonic. Nostalgia.

      --



      To ensure perfect aim, shoot first and call whatever you hit the target
    7. Re:Random is hard. by Chris+Mattern · · Score: 1

      If you think about it, a computer is generating it from an algorithm, which may be complex, but is essentially a set of rules that can be determined.

      Absolutely true. That is why any rigorous discussion of random number generators will always call numbers produced by a deterministic process (such as a computer program) "pseudorandom". To get true random numbers you need a piece of hardware that measures a truly random physical process. The classic one is radioactive decay, which is guaranteed random by the laws of quantum physics. My physics isn't strong enough to tell whether this light through diffusive glass technique is correct.

    8. Re:Random is hard. by mbone · · Score: 2

      I have heard of some that try to utilize some sort of seemingly random event that is naturally occurring. However even these can be modeled over time.

      A good post, but I'm not sure you understand hardware based random number generation. At least one way to do it is have a small amount of radiactive material. Although it decays predictably in the long term (half life) it is random in the short term. By measuring the radioactive decay truly random numbers can be obtained.

      The decay may be random, but the implementation may not be. I have heard of two issues with actual radioactive random number generators.

      1.) The geiger tube (or solid state chip) used for detecting the decays will have imperfections (for example, a dead time so that it will miss a decay occurring too soon after another one), and these can introduce non-randomness into the output.

      2.) The early ones were simple accumulators (count for an interval delta-T, and if you get > Y decays, that is a 1, otherwise a zero), and that can be hacked if you
      can control the radioactive environment at the detector. I believe that to prevent that now--a-days the algorithm is simething like "count for an interval, and if you get an even number of decays, output a 1," but that might have radioactive hacks as well. (I don't know of any, but I don't have a large staff trying to break this, either.)

      The entropy per character of human languages is so low that it doesn't take much non-randomness before you can get into deep trouble.

    9. Re:Random is hard. by DarthVain · · Score: 1

      I just Goggled the "cambridge coffee pot". Too funny. Only programmers would invent technology to remotely determine accurate caffeine levels to avoid exercise. :)

    10. Re:Random is hard. by Anonymous Coward · · Score: 0

      Human card shuffling is certainly not random -- not only is the process controlled by the shuffler, but there are distinct non-random patterns to it that allow stage magicians to take a stack decked that is shuffled and still produce the desired result.

      Funny story... I once heard a story about a mathematician who had figured out a way to shuffle cards so that the order after shuffling was truly unpredictable. His method started like this: "Cut the deck in a random position..."

      I believe it was in a documentary on card counters in casinos back in the days when they used just one deck, and what the casinos did to prevent it. So in his defense, this was well before the time when computers were available. I suppose back then a casino dealer's ad-hoc choice of 'random' cut was still good enough.

    11. Re:Random is hard. by the_other_chewey · · Score: 1

      Case in point. The WWII carrier pigeon letter that was found in an excavated chimney in England last year. It had a short code sequence. The Internets (including slashdot) were all a buzz with trying to crack it to see what it actually said. This went on for months, and no one could do it. People were speculating that it was a OTP, and thus "Impossible" to crack. When all it took was some dude in Peterborough, Ontario, Canada who dragged out an old RAF recon code book they had in their attic and translated the whole mess in about 20 minutes.

      No he didn't.

    12. Re:Random is hard. by Anonymous Coward · · Score: 0

      That said, a OTP is pretty tough to beat no matter what. When I saw the headline, I smirked a bit. Ya, computers and the availability of electronic code *might* make it easier to crack. However that is more likely the fault of the implementation, not the actual code itself.

      You've got an error here. A properly used one-time pad is impossible to decrypt. Problem is, this has several tricky issues. The pad must be used once and never reused, the moment it is used a second time it is subject to cryptanalysis and information will be leaked. The pad must be randomly generated, any flaws with the random number generator will allow cryptanalysis of the generator and subsequently cryptanalysis of the message. If you get it right, then a OTP is perfect.

    13. Re:Random is hard. by Rich0 · · Score: 1

      Why? It is because they are truly random. Each single outcome is just as likely as every other, which means that in the long run, the outcomes will occur pretty much equally often (give or take).

      Each outcome cannot be equally likely. An atom of uranium at any moment has to be more likely to decay than an atom of carbon, since the former decays and the latter does not.

      Sure, radioactive decay certainly seems random on short terms. However, it is entirely possible that some day we'll come up with a way of describing its behavior and it will turn out not to be random.

    14. Re:Random is hard. by DarthVain · · Score: 1

      First off, argue one way or another, but one is an established publication (multiple actually), and you posted some blog on the interwebs to refute it. Not saying I disagree, just establishing source material. Suffice it to say, that perhaps there is still some contention around the decoding.

      Which, actually proves my point all the more (provided of course that it isn't all just random noise or a prank, which seems highly doubtful) as given the relation to this posted topic, shouldn't this have been solved eons ago using all our technological electronic wizardry? Even if it was a OTP (which I see in the comments section people were back to speculating, including some rotary coders etc...), according to this article it would seem that it is vulnerable. A OTP from the 40's should be child's play! Which I say is hokum. It isn't the code that is more easily broken, only the implementation, which will allow the decoder to "cheat".

    15. Re:Random is hard. by the_other_chewey · · Score: 1

      First off, argue one way or another, but one is an established publication (multiple actually), and you posted some blog on the interwebs to refute it.

      I posted actual facts to refute it, which should not be judged on where they are published

      If you look at all those "established publications", you'll notice that they all pretty much write
      the same thing, paraphrasing the content of some alleged decoding, but not actually citing it.

      My link (where at least some people actually seem to know what they're talking about) supplies
      the full "decoding", which to everyone even with just a little bit of background in crypto and its history
      and usage in WW2 is obvious nonsense. And that's even without considering the actual alleged
      message content, which just makes it even less plausible (at least half of it is useless gibberish).

    16. Re:Random is hard. by DarthVain · · Score: 1

      Hey not arguing that the publications might all be sourcing the same material (lazy), or that the content of your cite is without merit.

      However saying you posted facts and it shouldn't matter where they are published is horseshit and you know it. Who does that blog answer to? Professionally?

      While this is not a extreme example (though one might argue that anyone that contributes to a crypto blog on a regular basis other than an academic setting may indeed be a crackpot), but I bet if I got some "facts" about "Jews" from a "Neo-Nazi" (ewww Godwin already!) blog, you may just want to call those "facts" into question. I know this is a ridiculous example but it is to make a point. An established journalism source is where I cited my reference while you sourced from a some blog on the internet by some dude. I am not saying your "facts" are wrong, simply that you can't refute mine so simply. i.e. Wrong. This.

    17. Re:Random is hard. by thoromyr · · Score: 1

      Heck, *I* don't know it is random. But AFAIK it is generally accepted that the moment of decay (or timing between consecutive decays) is non-deterministic. Certainly, Einstein was in the non-random camp. But there certainly appears to be true randomness associated with quantum events and it is relatively easy to generate streams of 0s and 1s that are by current standards non-deterministic. How well does it translate from a lab to a device?

      I refer back to my favorite example of cracking cryptography. A flaw in the design can eliminate any advantage. Implementation of anything can be a bitch, and cryptography is much easier to get wrong than right.

      However, there is no inherent flaw in using hardware-based random number generation with a non-deterministic source of entropy.

    18. Re:Random is hard. by Rich0 · · Score: 1

      However, there is no inherent flaw in using hardware-based random number generation with a non-deterministic source of entropy.

      There isn't any flaw in using ANY method of generating random numbers if it involves a non-deterministic source of entropy. The problem is that nobody can prove that such a thing exists. You can only say that something looks random and that nobody has publicly disclosed that they've found a pattern in it.

      I agree that most physicists think that the timing of individual decay events is non-deterministic, along with many other quantum events. However, you're talking about an area of science that is hardly understood from first principles. We can't even describe how gravity works at the quantum scale, and yet we KNOW that gravity is real. Who is to say that somebody won't figure out that we're wrong about things being non-deterministic?

      The only time you can know anything with certainty is in the world of mathematical proofs, and you can only say that something in math is certain in the sense that it doesn't contradict any axioms that you have accepted. The problem is that this is all an abstraction - there is no way to prove that anything in the real world behaves in any particular way to mathematical certainty. You can only obtain increasing levels of confidence through science.

  24. Re:Not too long until an iceberg attack is reveale by barlevg · · Score: 2

    The breakthrough is the KIND of OTP that they're using: glass plates that, they believe, cannot be (easily?) duplicated, unlike a digital OTP would be.

  25. nothing new by stenvar · · Score: 1

    Random physical structures have been used for this purpose for decades.

    1. Re:nothing new by nsaspook · · Score: 1

      Random physical structures have been used for this purpose for decades.

      Yes, using PUF devices for OTP, challenge/response and key generation is old tech.

      All you really need is a large SRAM structure to generate unique random bits for each device. A simple microcontroller with a large SRAM block works nicely.
      http://trudevice.com/Workshop/program/13%20M.%20Platonov%20TRUDEVICE_2013.pdf

      --
      In GOD we trust, all others we monitor.
    2. Re:nothing new by SuiteSisterMary · · Score: 1

      One of my personal favourites was one that took digital pictures of four different colored lava-lamps and used that to generate the random stream.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    3. Re:nothing new by stenvar · · Score: 1

      That's not a useful key because it's not constant over time.

      Here is a history:

      http://en.wikipedia.org/wiki/Physical_unclonable_function

  26. Re:Not too long until an iceberg attack is reveale by JaredOfEuropa · · Score: 3, Funny

    All she does is sneak into his hotel room when he's asleep, generate his pad using his crystal and make a copy of it.

    Sounds like a metaphor for something kinky...

    --
    If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
  27. Completely impractical, i.e. worthless by gweihir · · Score: 2

    A secure one-time pad with classical means is easy to do. You just need to secure the system where the pad is applied adequately. You need to do the same thing with this hype-device. Hence it has zero advantages over other implementations of the one-time pad, but a lot of drawbacks.

    I would suggest that these people are not stupid and know of the severe drawbacks. I would also suggest they are just completely unethical lying scum and grant or investment money is the only thing counts for them.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Completely impractical, i.e. worthless by Anonymous Coward · · Score: 0

      I'm not an expert by any means, but is the interesting part of their work that "...extraction can only be done by passing light through the glass at a rate that is limited by the amount of heat this creates (since any heating changes the microstructure of the material). And the time this takes should give the owners enough time to realise what has happened and take the necessary mitigating actions." ?

  28. Re:Not too long until an iceberg attack is reveale by Anonymous Coward · · Score: 0

    The problem here is the OTP is not one-time.

  29. Re:Not too long until an iceberg attack is reveale by Big+Hairy+Ian · · Score: 1

    Oh thats easy just make sure the person you want to talk secretly to is called Eve!

    Problem solved :)

    --

    Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

  30. Re:Not too long until an iceberg attack is reveale by Anonymous Coward · · Score: 0

    See Wikipedia for the generic concept behind this "breakthrough": PUF.

  31. Re:Not too long until an iceberg attack is reveale by david_thornley · · Score: 2

    If the OTPs are in fact uncopyable, the authors don't need a perfectly secure channel. Alice sends plates to Bob. Eve intercepts the crate, and then what? If she can't copy the plates, she can either divert them or break them (in which case all we need is an authenticated, not secure, channel for Bob to report nondelivery), or let them proceed to Bob. If Bob doesn't report that he has the plates, then Alice sends another batch of plates until Bob reports that he has them. If Alice and Bob need to talk more than the shipped plates allow, Alice can ship more at any time. Eve can, if sufficiently diligent and successful, remove Alice and Bob's ability to communicate, but cannot intercept any message.

    Of course, if it's possible to make a copy of a plate, it's no better than trying to securely send thumb drives.

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  32. Variations on this are the only way. by Karmashock · · Score: 1

    All top secret information should flow through one time pad systems.

    Look at it this way. What does disk space cost these days? Imagine getting a 30 gigabyte one time pad file on its own little SSD drive. How much data could be passed back and forth as theoretically unbreakable encryption? At the very least 30 gigabytes of data. In practice, probably at least a magnitude beyond that.

    --
    I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
    1. Re:Variations on this are the only way. by mbone · · Score: 1

      All top secret information should flow through one time pad systems.

      Look at it this way. What does disk space cost these days? Imagine getting a 30 gigabyte one time pad file on its own little SSD drive. How much data could be passed back and forth as theoretically unbreakable encryption? At the very least 30 gigabytes of data. In practice, probably at least a magnitude beyond that.

      No, at most 30 gigabytes. The next byte you send will start to reveal previous traffic.

    2. Re:Variations on this are the only way. by Karmashock · · Score: 1

      Theoretically. It depends on how secure the traffic has to be... you could run some of the high volume lower security traffic through a portion of the key that is "stretched" a bit.

      But the top top security data... yeah. 1:1 ratio with the key.

      --
      I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
    3. Re:Variations on this are the only way. by slim · · Score: 1

      I am not a cryptographer, but I *think* it would not harm the strength of the encryption if you compress then encrypt.

      You could also use the OTP as a source of symmetric keys for AES, moving to a new one regularly, as SSL does.

    4. Re:Variations on this are the only way. by mbone · · Score: 1

      I am not a cryptographer, but I *think* it would not harm the strength of the encryption if you compress then encrypt.

      In theory, it should actually make it stronger, by removing redundancy. In practice, I bet it would mean that you could then predict the first few bytes of each message sent (i.e., some sort header info, followed maybe by something guessable if you know the language being used) and it can be a bad idea to begin each message with something predictable.

    5. Re:Variations on this are the only way. by slim · · Score: 1

      I am not a cryptographer, but I *think* it would not harm the strength of the encryption if you compress then encrypt.

      In theory, it should actually make it stronger, by removing redundancy. ...
        it can be a bad idea to begin each message with something predictable.

      Both completely irrelevant if you're encrypting with a OTP.

    6. Re:Variations on this are the only way. by mbone · · Score: 1

      A perfect OTP, you are correct.

      An imperfect OTP, or one imperfectly used, it could make a difference.

    7. Re:Variations on this are the only way. by mbone · · Score: 1

      I don't think that is correct. If you reuse the key, you reveal the key. Worse, it can be easily caught by simply cross-correlating every message pair. (No key reuse = no correlations - key reuse = lots of correlations.) It can be almost trivial to decode a OTP message pair with the same key.

      Of course, compressing before you encrypt is fine, as long as you don't reuse the key.

    8. Re:Variations on this are the only way. by suutar · · Score: 1

      for a one time pad, encryption doesn't affect the strength (it's perfect; it can't get better). For other methods, yeah, reducing redundancy in the plaintext reduces redundancy in the ciphertext, which is a good thing. As someone else mentioned, it may wind up with the first several bytes of plaintext being predictable, but these days any respectable algorithm has to be able to resist a known plaintext attack (the OTP resists it by never reusing the key; deriving the first 6 bytes by xoring with 'From: ' won't help you on any future message).

    9. Re:Variations on this are the only way. by Anonymous Coward · · Score: 0

      You sir, are an idiot.

    10. Re:Variations on this are the only way. by Karmashock · · Score: 1

      And yet that's precisely how most encryption works.

      You use an encryption key to randomize your data. A relatively tiny key is frequently used to randomize a very large portion of data. Yes. This sort of thing is technically breakable. But 480bit encryption is considered strong. What would 1 GIGABYTE encryption be... Pretty f'ing strong. Imagine an encryption key that was GIGABYTES in size. Technically breakable if you used it over many many gigabytes? Yes. But we're talking about a key so complex that super computers for decades wouldn't have a prayer at breaking it before the universe burned out.

      --
      I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
  33. Re:Not too long until an iceberg attack is reveale by Immerman · · Score: 1

    Not really - a USB drive is laughably easy to duplicate - that's kind of it's purpose. Exactly duplicating (or even just characterizing) microscopic surface imperfections on a piece of glass on the other hand likely requires specialized hardware that a spy can't easily carry in a suitcase. At least assuming that a smooth protective layer is bonded over it to prevent mold creation (say glass with a much different refractive index).

    So basically you're adding physical-key security to your OTP, which drastically strengthens the only major weaknesses of the technique.

    --
    --- Most topics have many sides worth arguing, allow me to take one opposite you.
  34. Be wary by mbone · · Score: 2

    Three things are required for a one time pad - that the key be shared, random and non-repeated. A one time pad is very much breakable if the key is not both random and non-repeated, and the biggest problem with its use can be the sharing of the keys.

      The Soviet "Verona" traffic was decoded because they reused pads (keys), rendering the message decryption straightforward, and also revealing the keys. The revealed keys were found to have some further weaknesses, as they were made manually (apparently by secretaries told to type randomly on their typewriters). These weaknesses included an avoidance of repeated characters, a tendency to alternate hands (a character on the left side of the keyboard would be likely to be followed by one on the right), and (IIRC) a preference for character pairs and triplets that didn't require too much stretching of the hands. (On the top line of a QWERTY keyboard, this means that, say, an initial "q" would be unlikely to be followed by another "q", that it would be likely to be followed by a letter in the "u - p" range, and that the third character would be more likely to be a q, w or e than an r, t or y.)

    Now, officially, that amount of manual non-randomness wasn't enough to break further Soviet one time pad encryptions, but I suspect that they were. I have also heard rumors that later use of random keys generated by electronic circuits had problems as the physical limitations of the electronic circuitry imposed a low-pass filtering that made these keys, again, not totally random. Note that true randomness is what is needed here - common digital pseudorandom techniques, such hashing with SHA-1, may help to obscure weaknesses, but they will not make a non-random key random.

    In this case, I would worry very much about

    - whether the physical technique produces a truly random key and
    - how to satisfy myself that today's random key is totally independent of every previous key. If this is, say, dependent on where the laser is pointing to in the glass, how far apart does each pointing need to be to make sure that the results are independent, and can I securely verify that today's direction is sufficiently different from every previous time and
    - as the technique is passing an initial sequence of bits through the randomizer glass, how random does the initial sequence need to be ? What weaknesses are imposed by non-randomness in that initial sequence.

    I could easily see this technique being secure in theory but massively broken in practice by some weakness in how the glass is made or handled or in the initial keys.

    Note, by the way, that the two parties must physically get together to generate the key, so in a sense this is really a secure key storage device. Once they use up their stored keys, they have to meet again to be able to send more messages, which of course is the real problem with one time keys (and why, for example, the Soviets reused some of the Verona keys).

    And, finally, this technique might make a cool way of doing truly secure hashing.

    1. Re:Be wary by mariox19 · · Score: 1

      The revealed keys were found to have some further weaknesses, as they were made manually (apparently by secretaries told to type randomly on their typewriters).

      Had the Soviets been in possession of a million keyboards and an equal number of monkeys, they'd most likely still be in business.

      --

      quiquid id est, timeo puellas et oscula dantes.

    2. Re:Be wary by mbone · · Score: 1

      Or at least they could have chucked the cold war and gone into the scriptwriting business.

    3. Re:Be wary by Anonymous Coward · · Score: 0

      The Soviet "Verona" traffic was decoded because they reused pads (keys), rendering the message decryption straightforward, and also revealing the keys. The revealed keys were found to have some further weaknesses, as they were made manually (apparently by secretaries told to type randomly on their typewriters).

      1. It's Venona, not "Verona".
      2. Far from being "straightforward", it took nearly a decade of work to decrypt everything that could be decrypted.
      3. Your section on non-randomness of keys is simply not true. Nothing like that happened. (Indeed, your example makes no sense in the context of Venona, where the one-time pads consisted of random numbers, not random letters.)

      Basically, you don't know what you're talking about. So you're in good company on Slashdot, but you should probably shut up anyway.

  35. True Randomness is Possible... by BoRegardless · · Score: 1

    When you get loaded.

  36. Re:Not too long until an iceberg attack is reveale by K.+S.+Kyosuke · · Score: 4, Interesting

    What about a MITM attack? Doesn't need Bob verify that the plates are actually the ones that Alice manufactured? You don't need to copy the plates to barge into the channel.

    --
    Ezekiel 23:20
  37. Re:Not too long until an iceberg attack is reveale by mbone · · Score: 2

    Of course, if it's possible to make a copy of a plate, it's no better than trying to securely send thumb drives.

    The simple fact that there are two serves as an existence proof of the possibility of making a copy.

  38. Re:Not too long until an iceberg attack is reveale by SpectreBlofeld · · Score: 1

    I don't think they are identical plates. The encryption would simply take the configuration of both into account.

  39. Re:Not too long until an iceberg attack is reveale by AchilleTalon · · Score: 1

    That's the point, you need physical access to the glass to break the code. With a USB key, at some point the USB key must be plugged in and can be copied remotely.

    --
    Achille Talon
    Hop!
  40. Re:Not too long until an iceberg attack is reveale by UnknowingFool · · Score: 1

    The main problem I see is that the pads must be distributed in some secure way. With public key cryptography, the public key is available for anyone to use and distribution of this key does not have to be secure.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  41. Re:Not too long until an iceberg attack is reveale by Anonymous Coward · · Score: 0

    I always assumed you exchanged pads in person (or over a secure connection), then used the pads to later transmit information when a secure connection isn't available. You could fill two harddrives with random data, then meet rather infrequently to re-randomize and exchange them.

  42. Re:Not too long until an iceberg attack is reveale by Chris+Dodd · · Score: 1

    >

    The innovation here is that that nobody can make a copy of the piece of glass.

    Or is it...? If Bob can create a OTP using the glass then so can Eve. All she does is sneak into his hotel room when he's asleep, generate his pad using his crystal and make a copy of it.

    The point is that its a READ ONCE device -- Eve can't make a copy of the data in Bob's key without destroying the physical device containing the key...

  43. another random source by eagl · · Score: 1

    I always thought a high quality recording from a windy outdoors location with no man-made sound sources would make a fine source of random values.

  44. Re: Not too long until an iceberg attack is reveal by tillo.mirtillo · · Score: 1

    This is actually an excellent question. I know HMAC exchanges need a distinct MITM protection for the same reason, maybe the same techniques can be applied in this situation? (I did not read the oroginal paper yet, maybe they already do that)

  45. Re:Not too long until an iceberg attack is reveale by Anonymous Coward · · Score: 0

    That relies on Eve always being able to intercept the encrypted messages so that she can translate the message from set of plates Alice-Eve to the Eve-Bob plates.

    As soon as you miss one message the game is up as Bob's plate doesn't work with Alice's.

    This is why you want to copy, not replace the plates.

    But, yes, you're right, as long as you're happy to always be the MITM and you dno't mind if you're discovered after you're done.

  46. Re:Not too long until an iceberg attack is reveale by slim · · Score: 1

    It must be at least read-twice. Once to jointly encrypt the "common key", which contains the pad, and once retrieve the pad from the common key.

  47. How this is somewhat better than USB keys by Cacadril · · Score: 1

    "I fail to see how this is more secure than simply exchanging USB keys."

    This is more secure than exchanging USB keys because such keys exist all the time between the moment of generation and the moment of decryption. An attacker that gains access to the storage media at some point in between can copy the pad very quickly without anyone noticing.

    This method lets Alice and Bob store only the sequence S and the combination W = (A xor B), which may be published, as Eve cannot use them to decode intercepted messages. The actual codes A and B are not stored, they are recreated when needed from S and the corresponding piece of glass.

    The two pieces of glass are safer because it is hard to copy them. That is, the idea is that each piece of glass is like a 100-petabyte one-time pad, which would be both time consuming to read and hard to store.

    The sequence S is used to extract a manageable portion A (or B) of this 100-petabyte pad.

    But here is perhaps the weakness of the system: If the sequence S is known to Eve, and she briefly gets access to one of the pieces of glass, she will only need to repeat the process by which A or B was generated from S and the glass. This is precisely the same process that Alice and Bob must repeat to actually use the system. Such brief access is largely equivalent to a similarly brief access to the USB key or the stored data on a hard disk. Once Eve has one of A or B, she computes the other one using A = B xor W or B = A xor W.

    So the security benefit boils down to the glass not being continuously connected to the optical device. This is similar to a USB key not being continuously connected.

    But it may still be easier to protect a single piece of glass that is reused with different values of S, than to keep track of multiple USB keys for the different sessions. (And not confuse these keys with other keys used for other purposes.)

    --
    There is no substitute for common sense. Especially, no body of rules will do.
    1. Re:How this is somewhat better than USB keys by viperidaenz · · Score: 1

      It's vulnerable to another kind of attack.
      If the piece of glass is destroyed in transit, the data it encrypted is lost forever. You can't create a backup key and you have to physically transport it to the recipient of the message for them the decrypt it.

  48. Zardoz is happening by cyberfunkr · · Score: 1

    http://www.imdb.com/title/tt0070948/synopsis?ref_=tt_stry_pl

    Infinite data being stored in a single crystal; all depending on how the light refracts.

  49. Re:Not too long until an iceberg attack is reveale by idunham · · Score: 1

    As far as I can tell, the glass is the OTP.
    Copying it is possible, but you need 24 hours (using current techniques).
    So Eve has to (a) get it for a day, and copy it, or (b) get physical access to it after obtaining the message, before the message becomes irrelevant.

  50. Re:Not too long until an iceberg attack is reveale by s1lverl0rd · · Score: 1

    Whatever you do, don't tell Alice - she's the jealous type, or so I've heard

  51. Re:Not too long until an iceberg attack is reveale by viperidaenz · · Score: 1

    At some point the glass needs to be "plugged in" in order to read the code off it again to decipher the message.

  52. Re:Not too long until an iceberg attack is reveale by quarterbuck · · Score: 1

    If the OTPs are in fact uncopyable, the authors don't need a perfectly secure channel. Alice sends plates to Bob. Eve intercepts the crate, and then what?
    Eve intercepts the crate and places a one time pad that she made (different from original) and sends the crate on. When Alice later sends the message, Eve reads it, re-encrypts it using the code Bob is expecting and forwards that on. Neither Alice nor Bob detects anything odd, while Eve knows the message before Bob.

    --
    http://slashdot.org/submission/1062723/Cheap-mobile-data-plan?art_pos=2
  53. Old hat by Anonymous Coward · · Score: 0

    Perhaps the esteemed expert author didn't know, but this has been done for many years with various physical noise sources. They've just used yet another sensor, otherwise this is old hat.

  54. POTP by rickb928 · · Score: 1

    Back around 2000--2001 I used POTP email client from, an Israeli company to satisfy a client's perceived need for encrypted communications.

    It solved the exchange problem on an initial or any sync message, and after that passed new pads each time.

    Pretty much unbreakable. I still have a copy, but I doubt it would run, and I need a partner to test it, sort of.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
  55. Clever but not infallible by yusing · · Score: 1

    Really clever. Haven't read the whole thing, but this seems like a potential weak-spot: "Of course, this process can be used only once. But Alice and Bob can generate a huge volume of combined keys by passing different random patterns through their slabs when they meet."

    When there's more than one key, there's potential for a human-factor screw-up. If there's no way for Alice and Bob to meet, then there's a time-limit. Finally, without access to the public combined-key, nothing works. So a few things can go wrong - and will.

    --

    "You must try to forget all you have learned. You must begin to dream." -- Sherwood Anderson

  56. OTP by Anonymous Coward · · Score: 0

    I have written an OTP program, but it is not for public use. I use the OTP generating routine here: http://www.fourmilab.ch/onetime/otpgen.html

  57. Random has been achieved I think. by Anonymous Coward · · Score: 0

    The ANU Quantum Random Numbers Server at http://150.203.48.55/Matrix.php

  58. plate intercepted, not better than Yosemite Sam? by WOOFYGOOFY · · Score: 1

    Does this alleviate Bob's problem of determining whether or not Eve has gotten the plate before it got to Bob or after it got to Bob? Is it not really impenetrable encryption, or does it just move the challenge from "snooping electronically" to "stealing without detection"? If Eve got a hold of the plate before Bob did could she not even in theory substitute a different plate? Copy the plate? Provably too hard or just too hard as far as we know or doable given resources, which? Bob would have to destroy / mutate the plate right after use- destroy after reading. Humans are the weak link in that scheme, right? Bob can't be relied to remember much info without the aid of some form of transcription. So good for secure launch codes, the ultimate in "use-once-and-render-irrelevant" , (but what if there's failure to launch? What do you know ? Can you still destroy the glass or do you have to keep it around for forensics examination and what are the security implications there? ) but not so good for ad hoc communication. And anyways how is this better than the one time pads you can listen to on shortwave radio? http://www.spynumbers.com/ Or the mysterious Yosemite Sam broadcast coming out of NM? http://www.spynumbers.com/ys.wav Which may effectively be a one-time pad where numbers are represented by hard-to-detect changes in the background noise / amplitude of the seemingly same Bugs Bunny excerpt?

  59. Two-time pad by Anonymous Coward · · Score: 0

    Is easily cracked. Consider the three-time pad equal to open-text, unless your opponent is lazy.

  60. Re:Not too long until an iceberg attack is reveale by Anonymous Coward · · Score: 0

    you would need a microscope ( eletronic one ? ) for to make an 1:1 copy of the crystal resp. of the glass - this microscope
    would have to be connected to an emulating transmitter of the code . . . would mean the microscope is delivering the "key" for the
    transmitter by scanning the glass or crystal . . .

  61. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  62. Re:Not too long until an iceberg attack is reveale by RockDoctor · · Score: 1

    If either the message is random, or the encryption key is random and non-repeating, then the message cannot be deciphered.

    I think that the OTP also needs to be longer than the message to be truly secure, but IANA-cryptanalyst, so I'm not better than 90% sure on that.

    Most encryption systems that I've seen compress the message before encryption, which makes it close enough to random to help a lot on that front of making Eve's life difficult ; and it makes the balance between message length and OTP length more favourable too.

    --
    Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
  63. Re:Not too long until an iceberg attack is reveale by dotar · · Score: 1

    ... the only major weakness...

    Except that part where your key has to be as long as your message...