Slashdot Mirror


Intro to Encryption

An anonymous reader submitted a Techworld story which is a sort of encryption primer. The difference between codes & cyphers, and what all those acronyms like RSA and DES actually mean. This is good primer material for newbs, and a good refresher for fogeys.

60 of 244 comments (clear)

  1. intro to encryption by JavaLord · · Score: 4, Funny

    svefg cbfg!

    1. Re:intro to encryption by Anonymous Coward · · Score: 5, Informative

      a b c d e f g h i j k l m n o p q r s t u v w x y z
      n o p q r s t u v w x y z a b c d e f g h i j k l m

      first post!

    2. Re:intro to encryption by virid · · Score: 2, Funny

      i hope you didn't actually need to chart that out...

      --
      "The world only exists in your eyes. You can make it as big or as small as you want." - F Scott Fitzgerald
    3. Re:intro to encryption by justforaday · · Score: 3, Funny

      Nope...Double, or better yet, quadruple rot13 are the greatest...

      --
      I'll turn into a supernova and burn up everything. Well I'll turn into a black little hole and you'll turn into string.
    4. Re:intro to encryption by Black+Perl · · Score: 3, Funny

      I use ROT26, myself.

      --
      bp
    5. Re:intro to encryption by Black+Perl · · Score: 3, Insightful

      How's the .sigsperiment going? It's pretty funny.

      Thanks. Actually it's been good for my karma. Some moderators dutifully comply--even on non-insightful humor bits. That's pretty funny.

      --
      bp
  2. Inaccuracy in article? by DarkHelmet · · Score: 5, Informative
    About RSA: Current hardware means key lengths should be 1024 bits for complete security. The present generation of web browsers use 128-bit keys so cannot be considered secure against a determined and sufficiently well-resourced attack.

    Certificates are 1024 or 2048 bit with SSL. On the other hand, once the key is sent and shared, a 128 bit symmetric form of encryption is used. The only thing RSA is used for is sending / receiving the symmetric encryption key, yes?

    Correct me if I'm wrong.

    --
    /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
    1. Re:Inaccuracy in article? by cpeikert · · Score: 4, Interesting

      You're right.

      There are other glaring inaccuracies, e.g.: An increasingly important use for asymmetric encryption is digital signing. A digital signature is the reverse of public key encryption.

      This is sort-of true if you're talking about plain-vanilla RSA signatures (though even here, it's only about half-right). But in general, digital signatures have nothing to do with encryption. An encryption scheme does not always yield a useful signature scheme, nor vice-versa.

    2. Re:Inaccuracy in article? by Ann+Coulter · · Score: 3, Interesting

      I'm developing a slow but very secure RSA cipher that treats your binary data as one large number. It will take the digits of this number in base m (where m is the modulus) and salt and encrypt each digit. This produces a data block that is encrypted using only one cipher. This eliminates the symmetric hole altogether, even though that hole is rather small. My new technique has value bacause the symmetric hole is still one of the biggest holes in the entire PGP system, next to implementation specific vulnerabilities.

    3. Re:Inaccuracy in article? by Asgard · · Score: 2, Informative

      I don't think the use of a symmetric system is considered a hole; the idea is that symmetric systems are strong keybit-for-keybit. As long as the symmetric and public key stregths are similiar there isn't a weakness one way or the other.

    4. Re:Inaccuracy in article? by wfberg · · Score: 4, Informative

      About RSA: Current hardware means key lengths should be 1024 bits for complete security. The present generation of web browsers use 128-bit keys so cannot be considered secure against a determined and sufficiently well-resourced attack.

      Certificates are 1024 or 2048 bit with SSL. On the other hand, once the key is sent and shared, a 128 bit symmetric form of encryption is used. The only thing RSA is used for is sending / receiving the symmetric encryption key, yes?


      Kinda yes. The public key is used to encrypt the session key, which is used in turn to encrypt the payload using a symmetric algorithm for speed.

      Certificates are a bit bigger than 1024 or 2048 bits. They contain the public key (consisting in the case of RSA, among other things, of the 1024/2048 bit modulus) the owner's identification (e.g. e-mail address, common name, url, ..), validity dates, and a digital signature from a certificate authority (in some cases they're only self-signed, in other cases, dosens of people may contribute to authenticating a public key's ownership information, as in PGP).

      A certificate is just that; it's to certify that a certain public key belongs to a certain entity.

      If you pay enough to microsoft/opera/etc., you can certify anybody you want and all internet explorer users will take it for granted, because no one checks certificates.
      --
      SCO employee? Check out the bounty
    5. Re:Inaccuracy in article? by mr.+mulder · · Score: 3, Informative

      You're correct - somewhat.

      Many assymmetric encryption schemes only use public/private key pairs to establish a secure connection. Once a secure connection has been established, most schemes generate a private key that will be used for symmetric encryption.

      The reasons for switching to symmetric are many, but primarily it is done for speed. Symetric encryption algorithms are very fast compared to assymetric. Also, symertic algorithms can easily be implemented in hardware, thus, speed boosts are even greater when switched to symetric algorithms.

      This kind of answers your question, but there are still a few crazy zealots out there that insist upon the sole use of assymetric algorithms - it is more secure, but worlds slower.

    6. Re:Inaccuracy in article? by cpeikert · · Score: 2, Informative

      The confusion stems from the fact that the RSA family is pretty good for both encryption and signatures, though it is used in a different way for the two applications.

      One other standardized signature is DSA, which is based on the hardness of computing discrete logs. The DSA algorithm itself is not the inverse of any secure encryption scheme. (It's worth noting that there are some encryption schemes based on discrete log; they're just not the inverse of DSA.)

    7. Re:Inaccuracy in article? by Lord+Dimwit+Flathead · · Score: 2, Informative

      The first part of that paragraph bugs me too:

      Unfortunately, nothing in life is free, and so it is with asymmetric cryptosystems. Since d can be computed from e given p and q, and p and q are the factors of N, they must be chosen so large that N cannot be factorised in any reasonable time.

      While this is accurate, it's the first and only mention of d, e, p, q and N. The author also never actually explains that RSA is built on the assumption that prime factorization is mathematically hard. It appears that he simply cut-and-pasted from another text without bothering to make sure that it fit with the article. I can only imagine the confusion of the poor newbies trying to make sense of this.

  3. Much better than that article by yahyamf · · Score: 5, Informative

    I would strongly recommend the Code Book by Simon Singh over that short article. It takes the reader from the Ceaser cipher all the way to quantum codes and is a very enjoyable read. The Codebreakers by David Kahn is also an excellent though somewhat lengthier volume

  4. Difference betwen Codes and Cyphers? by NardofDoom · · Score: 5, Funny

    That's easy. Code is what I stare at all day, while Cypher is the jerk who betrayed Neo in The Matrix. Duh.

    --
    You have two hands and one brain, so always code twice as much as you think!
  5. 640 bits should be enough for anybody by stecoop · · Score: 3, Insightful

    Rest assured that unless some one finds a mathematical back door that the algorithms approaching 1024bits will not be the weakest link in the security of your data (at least with hardware today). Just have a look at the key space in Distributed's RC5-72 vs. RC5-64. The key space for RC5-72 is astronomically higher than RC5-64.

    Usually, the weakest link will be the user using short keys or the user using the same password on a weaker system.

    1. Re:640 bits should be enough for anybody by lukewarmfusion · · Score: 4, Funny

      "...and my porn passwords are Romeo and Juliet!"

      Well my porn passwords are Juliet and Juliet. It's a lesser known work, to be sure, but it's certainly steamier.

  6. Handbook by Ann+Coulter · · Score: 5, Informative

    The Handbook of Applied Cryptography: http://www.cacr.math.uwaterloo.ca/hac/ is a very detailed guide to some cryptographic algorithms and theories. This is not for newbies at all. For those wanting to implement a particular cipher, this book is the place to refer to. On top of everything, it is free.

    1. Re:Handbook by melandy · · Score: 2, Informative

      Cryptography - A Very Short Introduction is an good book to introduce concepts of crypto. It's not a detailed manual about how any specific ciphers work, just an introduction to concepts.

    2. Re:Handbook by wfberg · · Score: 4, Informative

      I'd recommend applied crptography by Bruce Schneier instead.

      Not only does it cover the same ground, it also goes into detail a bit more about real tricky business; protocols (where most mistakes are made these days, since nearly everybody uses off-the-shelf algorithms like AES, DSA, RSA and ElGamal). This guy knows how to write, and succeeds in warning you of potential pitfalls in a humorous manner. Also, he knows his stuff; he submitted one of the AES candidates, Blowfish.

      Bruce also publishes the most excellent Crypto-Gram newsletter.

      Beware of not heeding Bruce's stern words of warning. You may end up in the doghouse! The humiliation! The shame upon your house!

      --
      SCO employee? Check out the bounty
    3. Re:Handbook by swillden · · Score: 2, Insightful

      I'd recommend applied crptography by Bruce Schneier instead.

      Seconded.

      But keep in mind Schneier's opening statement in his next book, "Secrets and Lies", which says that "Applied Cryptography" has probably led to the creation of more bad security than any other single text. Not because the book is bad (it contains errors, but they're fairly minor) but because the book makes you think you're an expert. After plowing through some 600 pages of dense material, you *have* to be an expert, right? Unfortunately, no, after 600 pages you're a layman with a solid overview of the topic.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    4. Re:Handbook by plover · · Score: 4, Informative
      Actually, Practical Cryptography is probably more useful to most people. In that book, Bruce provides real-world examples of security needs and then details how the protocols should be implemented so as to preserve that security. He leaves the math alone, and discusses the protocols and data instead.

      He wrote it after realizing how poorly people had misunderstood his warnings in Applied Cryptography (as documented in Secrets and Lies.) I thought his warnings were plain enough, but apparently too many people just plopped in some encryption because they "needed" some, and Blowfish was printed right there in the appendix.

      --
      John
  7. Eric Rescorla has written a fine book... by tcopeland · · Score: 4, Interesting

    ...SSL and TLS, which includes an introductory that has a nice overview of encryption concepts and techniques.

    The explanation of stream vs block ciphers is especially good, with nice examples showing how each technique works.

  8. Comprehensive list of unsolved codes and ciphers by tokengeekgrrl · · Score: 4, Interesting

    If after reading the intro to encryption you are so inspired to try to crack one, I highly recommend this list:

    http://www.elonka.com/UnsolvedCodes.html

    Enjoy.

    - tokengeekgrrl

  9. I realized something while reading the article... by zerguy · · Score: 2, Interesting

    What is the point of all these different encryption methods? No one has ever broken PGP. No one has ever broken GPG. No one has ever broken a well-protected OTP cipher (and they never will.) Why do they keep churning out new ones when the ones we have work?

    --
    **This begins my ever-changing sig
    We need a -1 RTFA moderation option!
    **This concludes my ever-changing sig
  10. This is good primer material for newbs by JohnGrahamCumming · · Score: 4, Insightful

    That's some clever way of saying "crap", right? This article is horrible, and if I was an encryption newbie all I'd be able to do after reading this article is spout acronyms.

    Here's part of what the article says about RSA:

    "Unfortunately, nothing in life is free, and so it is with asymmetric cryptosystems. Since d can be computed from e given p and q, and p and q are the factors of N, they must be chosen so large that N cannot be factorised in any reasonable time"

    THE ARTICLE NEVER STATES WHAT d, p, q, e OR N ARE. Sorry for the shouting but this piece o'crap is worthy of a /. front page?

    John.

  11. Safe encryption by darkstream · · Score: 5, Funny

    When I want to email with a new friend using PGP encryption, I send him my key one character at a time via snail mail using newspaper clippings. The only time this becomes a problem is when the post office laps itself and delivers more than one letter a day, or gets an earlier letter there later than a later letter, but it's the only way to be sure the key never falls into enemy hands. Of course, I don't get to email many people these days...

    --
    Fun with Inkwell | www.coo
  12. Applied Cryptography by Meostro · · Score: 5, Informative

    Bruce Schneier's Applied Cryptography is another excellent resource for all you crypto-geeks out there. It goes from the basics (including the substitution cipher presented in the article) through basic crypto (ENIGMA, DES) all the way up through state-of-the-art (don't think AES was in my 1st ed., but I believe it's in there now). He talks about everything from the theoretical to the practical, hash collisions to rubber-hose cryptography.

    It comes with source too! You know you love source....

  13. Re:I realized something while reading the article. by grahamsz · · Score: 5, Insightful

    Say tommorrow someone discovered an efficient technique for computing the prime factors of a composite. That would blow RSA and probably DSA out of the water - rendering most parts of PGP/GPG worthless.

    Unless we have other asymetric ciphers to fall back on, then e-commerce would be wiped out.

    Additionally algorithms with very low computational requirements are of particular importance since we need encryption that can run on smart cards, but cant be broken by super computers.

  14. Not really the best intro for crypto by Gentoo+Fan · · Score: 4, Informative

    I'd point people here first, then to a few other links that other people have pointed out. The article linked is a bit terse for a newbie.

  15. Clarification on web-browser security... by xquark · · Score: 4, Informative

    >>The present generation of web browsers use 128-bit keys
    >> so cannot be considered secure against a determined
    >> and sufficiently well-resourced attack.

    The 128-bit there is the symmetric cipher key length, RSA is
    used for signature authentication and not encryption, key
    exchanges occur via hand-shake algorithms ie: diffie-hellman
    and derivatives there of...

    a 128-bit symmetric cipher is actually very strong, for temporary
    transit data ie: purchase data, cc numbers etc.

    Arash Partow
    __________________________________________ ________
    Be one who knows what they don't know,
    Instead of being one who knows not what they don't know,
    Thinking they know everything about all things.
    http://www.partow.net

    --
    Arash Partow's Philosophy: Be a person who knows what they don't know, and not a person who doesn't know.
  16. Sosumi, McCartney! by Chris+Tucker · · Score: 4, Funny

    "When I find myself in times of trouble, PKZ he comes to me.
    Speaking words of wisdom, 'PGP, PGP.'"

    --
    Guaranteed! This comment 100% Anthrax free!
  17. Someone has been reading too much Cryptonomicon by finkployd · · Score: 2, Insightful

    f you just want to deter prying eyes a substitution cipher using multiple substitutions and several different substitutions schemes offers a reasonable level of encryption for virtually no computational effort. (This is the way Enigma works and after all, it did take Alan Turing to break it).

    The Poles broke it, they even invented the "computers" (bombes) that automated the further breaking of it. Turing (not to diminish the contributions he made to BP) really just vastly improved on their methods and created a much more sophisticated machine to break it.

    Finkployd

    1. Re:Someone has been reading too much Cryptonomicon by freaks_and_geeks · · Score: 2, Informative

      Won't supply a link here, but Simon Singh's excellent "The Code Book" provides a large level of detail about the Polish contributions to breaking Enigma.

      Ahh, what the hell, I _will_ supply a link here. Or, just google "Rejewski Enigma".

  18. random & pseudorandom pads by cant_get_a_good_nick · · Score: 4, Informative

    Random pads with truly random data is unbreakable. The few times it has been broken has been due to human error (reusing the same random data stream). The US tracked some russian spies with this, they reused pads, and we found out there was a mole in the atomic bomb program.

    That said, paddign with pseudo-random data is very unsafe. Breaking this type of encryption is typically one of the first homework assignments in cryptography courses. The article is either very fuzzy on this distinction, or plain out wrong, depending on how you read it.

  19. Re:I realized something while reading the article. by tomstdenis · · Score: 2, Interesting

    Factoring specifically has nothing todo with anything that can break DSA. Improvements in NFS related algorithms could however... Also we still have ECC and a few lattice algos left [NTRU anyone?]

    I wouldn't worry too much about it though. While I expect new algorithms [probably not even NFS based] to be invented at some point it probably won't be tommorow.

    Tom

    --
    Someday, I'll have a real sig.
  20. Re:Comprehensive list of unsolved codes and cipher by cpeikert · · Score: 4, Informative

    If after reading the intro to encryption you are so inspired to try to crack one, I highly recommend this list...

    The problem with challenges like "crack this uncracked cipher" is that the challenge is not realistic.

    Most of these codes/ciphers give you no idea the process behind how they were generated. That's unrealistic: usually an analyst will have the algorithm that does the encryption (if not the key itself), either via open-source, reverse engineering of a public binary, legitimate purchase, or espionage.

    Most of these challenges only give you a tiny piece of ciphertext. That's not realistic: if you're trying to break, say, SSL, you'll be able to get your hands on megabytes of transcripts, and you'll even be able to generate ciphertexts that correspond to plaintexts of your choice.

    Most of these "ciphers" don't generalize to arbitrary messages. That's unrealistic. Sure, someone can design some ad-hoc cipher to encrypt the location of his buried treasure using landmarks, clever puns, and weird symbols. That's a far cry from being able to efficiently encrypt an arbitrary TCP/IP stream.

  21. SETI noise by 3770 · · Score: 4, Interesting


    If you want to be absolutely definitely sure that no one can intercept your communication with someone then here's what you do.

    1) Get 600MB of random noise data from listening for extra terrestrials from for instance SETI.
    2) Burn two CD's, give one to your friend. Keep the other.
    3) Encrypt your message by superimposing it on that noise at a given location.
    4) send the message as well as the location with the random location that you started copying the noise from (from the CD).

    This message can _not_ be deciphered if you make sure that you never reuse the same random noise. Even if you reuse it it is hard.

    In addition, if you at some point expect that someone is on to you, just burn the two CD's.

    At that point those messages can _never_ be deciphered. Even if you try for a billion years.

    Simple.

    Unbreakable.

    --
    The Internet is full. Go Away!!!
    1. Re:SETI noise by saigon_from_europe · · Score: 3, Funny
      1) Get 600MB of random noise data from listening for extra terrestrials from for instance SETI.
      Don't do it!!! Simply, it's not safe. What if you take signal from some extraterestial inteligent species? That signal will not be completely random, and someone will be able to break it...
      --
      No sig today.
    2. Re:SETI noise by Knight2K · · Score: 4, Insightful

      This scheme is more commonly known as a one-time pad. Basically, you need to generate a set of random data that can be combined with your plain-text. A common implementation used to be pads of onion-skin paper with blocks of random letters on them. Onion-skin was used since it was possible to generate pairs of pads using carbons and also because the paper was easy to destroy. The pads usually had something like the date the pad was to be used on them.

      Often these systems were broken because the pads were misused: the same pad used multiple times, or the same pad used with some variation.

      IIRC, the scheme you are purposing is similar to the way that the red telephone communication between the Soviet Union and the US, as well as embassy communications, was secured. In that case, special vinyl records were distributed that had to be started at the same point. The length of the record determined how long you can talk.

      This essay on Bruce Schneier's site highlights one of the chief weaknesses of the one-time pad: the key distribution problem. You have to figure out how to get your friend's CD to him without being intercepted. You also have to be sure that the computer that generated the CD's wasn't compromised; someone spying on your machine could just log what audio file you used, copy it, and generate their own key CD.

      Considering that a CD can only hold around 700MB (for a standard audio CD), I would say the key space is small enough that even if an attacker doesn't know your position choosing scheme (your description of the system states that the position is part of the message, so I'm being generous here), it should be possible to brute force the message if he somehow gets access to the key.

      Another problem is: you may suspect that you are being watched or the system is compromised, but your buddy may not. How do you communicate that information to your friend, especially if you aren't supposed to be in contact with them in the first place?

      If the attacker has your key CD, he could send an encrypted message stating that you (the legitimate user) are the attacker? Then who would your buddy believe?

      The benefit of public-key cryptography is that it limits the amount of data that needs to be shared in order to communicate. The keys used for encryption never leave the possession of the person doing the encryption. It is also relatively simple to generate new keys.

      Of course, man-in-the-middle attacks can still happen. But if you can establish the first public keys that you and your friend will use in a secure manner (e.g. face-to-face meeting), subsequent public keys can be encrypted using the last trusted key, or by using other key sharing schemes.

      --
      ======
      In X-Windows the client serves YOU!
    3. Re:SETI noise by Monf · · Score: 2, Informative

      Didn't they use to do the same thing with vinyl records? (except for the seti part...)

      --
      Pay no attention to that man behind the curtain.
    4. Re:SETI noise by capilot · · Score: 2, Informative

      Even if you reuse it it is hard

      No. If you reuse it, it's easy to break. The Rosenberges went to the electric chair because some Russian spy reused a pad.

  22. Best class in college by silux · · Score: 2, Insightful

    One of my favorite classes was clasical algebra. I'm always glad to see some info about encryption and how it works. Thanks guys

  23. Re:I realized something while reading the article. by ACNiel · · Score: 2, Interesting

    They didn't work well, which is why modern cryptography was born. As far as practical goes, practical is a function of necessity.

    OTP has the significant shortcoming of key exchange. You have to have a method of distributing keys that will not be compromised. This is extremely hard to do.

    If the book ever falls into the wrong hands, then you have to throw everyones book out, and start over. You have to have access to your agents that are inside. Are you just going to send them their new book to the Kremlin, postmark Blechley Park?

    It can be done, it is inprenetrible, but has huge risks and shortcomings.

  24. Re:ROT13 by General+Wesc · · Score: 2, Funny

    Sometimes that's not good enough. In such instances, I always rot-13 it two times for twice the security.

  25. Mel & Baker a good crypto book by Coop · · Score: 3, Informative


    Cryptography Decrypted by H. X. Mel and Doris Baker is a good intro to crypto. I found it entertaining and the topics went from elementary to, uh, more than I cared to know. The appendices explaining the mathematics of crypto were interesting as well.

    --
    "If you're not passionate about your operating system, you're married to the wrong one."
  26. some things newbs should learn about encryption by brlewis · · Score: 2, Informative
    If you're going to give a cursory intro to encryption for the masses, I think a less mathematical approach would be warranted. This is not an exhaustive list, but here are some practical questions:
    1. Who can intercept my interaction with web sites if it's unencrypted?
    2. Who can intercept my email if it's unencrypted?
    3. How can I tell if my web browser is using encryption?
    4. What do those warnings about SSL certificates mean?
    5. Why does Internet Explorer warn me about a page with "both secure and nonsecure items"? What can I do about it?
  27. A better introduction by aaronvegh · · Score: 3, Informative
    From PGP's site: How PGP Works.

    It talks about the origins of crypto a little, and leads into public key encryption, a field I have been trying to learn a little more about. Much better article than the parent!

    --
    You can have my one-button mouse when you pry it from my cold, dead fingers.
  28. Re:I realized something while reading the article. by nwbvt · · Score: 3, Insightful
    How do OTPs work? Each side has an identical stack of pads which are used to encrypt and decrypt codes. Each time one pad is used, it is destroyed. This is mathematically unbreakable, though there are methods of cracking the code that do not involve mathematics (such as stealing a copy of the pad).

    This may not be too big of a problem if we just have two people who need to send a few messages to each other as long as both can keep the pad safe, but it fails horribly in other situations. For instance lets say I want to send my credit card number to some online store, but I want to make sure it is encrypted first. Lets say the store writes a random pad for us to use. How do we share it? Somehow they have to get it to me without anyone else seeing it. But if we had a known secure method of communication, we wouldn't need the pad in the first place, now would we?

    Public Key encryption solves this problem by allowing the store to develop the code and send me a key that only allows me to encrypt it (it can't decrypt anything). Thus it doesn't matter if the whole world intercepts the key, all that would allow them to do is encrypt more messages. It doesn't help them decrypt anything. Of course all these codes are usually based on problems that are mathematically hard to solve. If an easy solution is found (as with knapsack cryptosystems like Merkle-Hellman), then it becomes easy to crack the codes, and thus we need to have other codes available. In addition, many decryption algorithms are very slow and thus work is done on more efficient algorithms (though slow ones like RSA actually can be sped up by only encrypting a private key with the public key scheme and using the private key to encrypt the actual message).

    Hope that helps.

    --
    Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
  29. Re:I realized something while reading the article. by nwbvt · · Score: 2, Informative
    "...but that is very unlikely to happen."

    Actually its not. There is an efficient algorithm out there for factoring numbers into primes. The only problem is that it requires technology (quantum computers) which doesn't exist yet, but which is on the horizon.

    "And why is my article modded flamebait?!"

    Because mods are jackasses.

    --
    Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
  30. And now to toot a small horn by VernonNemitz · · Score: 2, Interesting

    Over at SourceForge is a relatively new Project called Primary Cryption. Working code (for Win32/WINE) has already been released. The source code includes hundreds of lines of commentary about encryption, C programming tricks, and other stuff that you might find interesting. The logo may be of interest, too. Some discussions about it have been started at the HalfBakery and at sci.crypt.research Oh, and if you want to put some effort into figuring out how easy (or tough) it is to break the proposed encryption scheme, feel free! I'd like to know. Thanks!

  31. isyay isthay ayay odecay? by NewtonsLaw · · Score: 3, Funny

    Iyay etbay obodyyay ancay igurefay histay utoay!

    Uggerbay, hatway oday ouyay eanmay "veryeay oneyay owsknay igpay atlinlay?"

  32. Re: Credability = Zero by KillerCow · · Score: 3, Informative

    About RSA: Current hardware means key lengths should be 1024 bits for complete security. The present generation of web browsers use 128-bit keys so cannot be considered secure against a determined and sufficiently well-resourced attack.

    Firstly, directly comparing symetric and asymetric key lengths shows that the authour has no knowledge of encryption. They are not directly comparable since they are used in different ways and have different meanings.

    Secondly, claiming 128-bit keys are insecure shows that the authour has no knowledge of encryption. 80-bit keys are widely considered infeasible to break.

  33. RND number generation and encription cards by saigon_from_europe · · Score: 4, Interesting

    During my army service, I was told about random number generating cards. Basic idea is very simple, use thermal noise in conductors/semiconductors as a starting point for number generation.

    So if you need random numbers for encryption, try some googling, and you will find many variations on this theme - serial port based equpment; noise from sound card (low cost solution - all you need is software). There are also schemes for do-it-yourself equipment.

    Unfortunately, you should be a bit reluctant to accept the idea that all these things work as advertised. Just for beginning, although thermal noise is white noise by default, it get filtered in system during the processing. Its spectrum will not be the same as it was on the origin. (I am not an expert, but I think that spectral characteristics of the signal is not a requrement for randomness, but this is still good example of possible flaw in implementation.)

    If I would start using this, I would test this generators with some mathematical tools.

    Also, there are encription cards. I was able to see one made by Soekris. It has hardware implementation of DES. DES is designed to be done in hardware - shifting and xoring is easy to implement in hardware. Soekris makes 486 and P5 low-consumption small sized boxes. With this card, you may make good and fast IPSec firewall that runs on 133MHz 486 (!). Unfortunately, I am not in touch with this equipment any more, but problem was that Linux driver was in alpha state (situation from 10 months ago). BSD drivers were in release state.

    (One idea came to my dirty mind - how interesting this card might be for crackers?)

    --
    No sig today.
  34. Re:I realized something while reading the article. by radish · · Score: 2, Informative

    No one has ever broken PGP. No one has ever broken GPG.
    Correction: No-one has ever admitted to having broken PGP or GPG. Unless you know something those of us outside the NSA don't, you can never be so sure.

    Remember, the Nazi's thought no-one had broken Enigma...

    --

    ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

  35. Re:known plaintext attacks? by capilot · · Score: 2, Interesting

    The primer seems a little overconfident about random ciphers

    That's where I threw up my hands in disgust. I've never heard of a "random cipher" before. Did he mean one time pad? Those are provably unbreakable, assuming you have a good source of random numbers. Did he mean XOR the message from a cheap-ass PRNG? Unnacceptable. And why 4 bytes at a time? If it's just XOR, then 4 bytes at a time buys you nothing.

    This article was written by someone who read someone else's articles, and understood about half of it.

  36. Good For Newbs! by dshaw858 · · Score: 3, Insightful

    This article makes me all warm and fuzzy inside. I'm a big advocate of encryption (especially PGP/GPG), and hopefully this article will encourage some neophytes to start using encryption (such as PGP). I'm not a paranoid geek that sits inside all day, if that's what you're thinking, by the way; I just think that a user has the right to be secure and private.

    - dshaw

  37. A perfect prime-factorizing algorithm by roystgnr · · Score: 2, Funny

    If it were possible to factor any prime in one month

    Any prime's factors are itself and one.
    </smartass>

  38. What p, q, e, d, and N mean by shostiru · · Score: 3, Informative
    No. They're from the RSA algorithm. In a nutshell ("number" means integer):

    • Generate two large prime numbers, call them p and q.
    • Calculate N = p*q. This is a much larger, but not prime, number.
    • Choose some number e coprime (i.e., relatively prime) to (p-1)*(q-1), greater than 1 and less than N. Two numbers are relatively prime if they have no common factors (e.g., 32 and 49 are relatively prime, but 32 and 48 aren't). e is, by convention, the number used to encrypt a message.
    • Find some number d such that d*e modulo (p-1)*(q-1) is 1. d is, by convention, the number used to decrypt a message. Of course, you can encrypt with d and decrypt with e, too.

    That's it. Now, put N and e together in a file and call it your "private key", and put N and d together and call it your "public key". To use them:

    • Convert the message into a number n less than N. For example, if N is 40 bits long (worthless, but for the sake of argument...) you could take four bytes at a time from your message as an unsigned 32-bit integer.
    • Encrypt n to generate the ciphertext, c, by raising n to the power of e, and then taking the result modulo N (i.e., c = n^e mod N). Send your encrypted number c to the recipient.
    • The recipient then takes c and raises that to the power of d, modulo N, to get the original n (i.e., n = c^d mod N). Neat, huh?

    In practice RSA takes too much time, so you make yourself a random key, encrypt that using RSA, and you and your recipient communicate using a symmetric cipher.

    As to why ((n^e mod N)^d mod N) = n, that's where it helps to know some math. Mathweb or Wikipedia can help you, but having a bit of background in abstract algebra will help.