Slashdot Mirror


Live From the Stomach of a Whale

Well, we've done one more show before we leave for LWCE from where we'll have multiple icecasts throughout the week. In our latest episode, we talk about the Slash code release, Kevin Mitnick's encrypted data, and the DoubleClick fiasco.

7 of 18 comments (clear)

  1. Why we like CowboyNeal by BaronCarlos · · Score: 2
    Like BaronCarlos said before, he's the Tom Servo of Geeks in Space.

    Along this same analogy:
    Rob is Crow
    and Jeff is Joel.

    Any MST3K fan would agree that all the characters are lovable, but all still have their favorite.

    Tom Servo, and CowboyNeal, are both super sarcastic, in the passive sense.

    He's the thinking man's comic.

    We love that.

    Another great episode.
    And E-mail is being sent.
    *Carlos: Exit Stage Right*

    "Geeks, Where would you be without them?"

    --
    *Carlos: Exit Stage Right*

    "Geeks, Where would you be without them?"
    "Got Linux?"

  2. Hey... wait a second... by Kid+Zero · · Score: 2

    I've got all 20 episodes. (if you count 3.1 as a seperate episode). Does this mean I need a new hobby?

    Oh well... It's always funny to listen to.

  3. Malda Rant and Cops by Duxup · · Score: 2

    Note to /. users. Don't play this episode too loudly when Malda rants . . . elderly neighbors will call cops due to "domestic dispute" next door.

  4. Mitnick's encrypted files by David+Gould · · Score: 3


    the government is apparently totally incapable of cracking encryption even given five years with the data to themselves. ... 12 bits of encryption ... My VAIO could brute-force that in five minutes.

    I saw this a few times in the comments on that story too, and I can't get over how totally some people seem to fail to understand encryption. This is at least as dumb as the "factoring large prime numbers" mistake that so many people make when talking about RSA. What makes you think he used such a weak code? Your TI-85 would have been perfectly capable of encrypting with, say, a 4096-bit RSA key (I have no idea what he actually used) -- it may have taken minutes or even hours instead of seconds, but the result is every bit as strong now as it was then. What you're missing is that that is exactly the point of why "they" don't like people having strong encryption: they can't crack it! That's why it's called strong encryption. It's not like, "Gee, this code is really hard, but you'd think in five years they'd manage to figure it out." That's just ridiculous. If the files are encrypted with a 4096-bit RSA public key, then they might as well be random noise, since that number is never going to be factored (barring a breakthrough in quantum computing or number theory).

    Sure, distributed.net has done well on some small keys, and is likely to finish RC5-64 in the next couple years, but those efforts are to prove a point about the weakness of small keys. Strong encryption is the kind where, if every particle in the universe were part of one big computer, the code still couldn't be cracked in the lifetime of the universe. In those cases, the only way to get at the data is some kind of "sideband attack", e.g., finding the key written down somewhere (if he'd been that dumb) or getting him to surrender it. If he was smart enough to use a strong code and not leak any sideband information, there's nothing they can do.

    We're the most powerful nation in the world and can't crack five-year-old encryption in five years.

    Well, that just goes to show what happens when those evil hackers have access to strong encryption. This is why that technology has to be controlled -- to save the government from this kind of embarrassment. Seriously, this is the strangest part of your argument: all this time, whenever a crypto-control story has come up, we have all railed against the government(s) for trying to control the technology and limit us to codes that they can break, and now, when you see an example of what happens when someone uses a strong code, you make fun of them for not being able to crack it. What's that?


    David Gould

    --
    David Gould
    main(i){putchar(340056100>>(i-1)*5&31|!!(i<6)<< 6)&&main(++i);}
    1. Re: Mitnick's encrypted files by Inoshiro · · Score: 2

      Ahh, you must not compare Apples and computers (pun!).

      128-bit encryption in Win2k is symetrical, using a RSA style negotiation setup. 128bits is more than enough for a symetrical key, as it still takes a long, long time to check all the possible 2^128 numbers against a block.

      Public key (RSA) style for general encryption, OTOH, requires a much greater keylength because you are giving away some information. You can't choose low-order polynomials, as it would make it trivial to break your data. You have to keep your "key window" in a much higher area, which is perfectly fine until someone figures out a quick way of factoring super huge numbers :-)

      So two different styles of encryption, two different optimal key lengths..
      ---

      --
      --
      Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  5. Free Kevins Porn! by Zaffle · · Score: 2

    In recent news, distributed.net has announced a new challege. The US government has sponsored the Crack Kevins Porn, errr, Disk Drive compitition. :)

    Btw - I agree with Robs rant on advertising. I wish I could do that too. :)

    Oh, and I run Junkbuster, and yup, I enable Ads for slashdot, and a few other sites.

    The length of this broadcast was good. Not too short, umm, still not long enough, I'd prefer 24hr slashdot radio, but I'm just strange. But seriously I'd love to have broadcasts more often.

    ---

    --

    I use to have a funny sig, but slash cut it off, and I forgot what the punchline was.
  6. Re:linuxone by Duxup · · Score: 2

    If you listen an episode or two back they make some comments on it, with some humor.