Slashdot Mirror


IBM Crypto Up For Grabs?

An Anonymous Coward writes: "BBC Newsnight have tonight shown an article about a groups of hackers who are about to release details of the vulnerability of the IBM Cryptographical processors. ( Details here.) The BBC article can be watched online here. Alan Cox makes a starring role ;)" windowlicker adds some detail: "Mike Bond and Richard Clayton, from Cambridge University, have cracked IBM's 4758 crytoprocessor running the 'Common Cryptographic Architecture' (CCA). You can do the same with $1000-worth of hardware and the info from here. Many banks use this system for protecting PINs." The video file requires Real software; here's the BBC's article online for those of us without.

4 of 230 comments (clear)

  1. RealVideo Coverage by guru_steve · · Score: 5, Informative

    I'm watching the video right now, and its taken a bit of time to find out where this segment is on the bbc news.

    So, for those of you who don't feel like jumping around the video for this segment, it starts at about 22 minutes in the broadcast.

  2. ATM's are more prone to stone age methods by number+one+duck · · Score: 4, Informative

    I'm not too worried about this. An electronic fraud is something that can be reasonably gotten out of, its the *banks* fault if their system eats your money. (Admittedly, I haven't read the small print of my own bank, but hey, its not the article, anyway).

    The big problem I have with my bank, however, is the location and layout of their ATM machines to begin with:

    1) ATM's are built into the wall, rather than in any kind of nook. The line generally forms directly behind the user. (This isn't so much of a problem for e.g. drive through atms, as the bulk of the car is obscuring view of the transaction).

    2) The buttons on the keypad are almost two inches across! I know they have to make them 'easy to use', and big happy buttons are important for that, I imagine... but having to move my entire hand around to enter the code makes it trivial to watch someone's movements...as opposed to normal sized buttons where what is being pushed is generally obscured by your hand itself.

    3) This is a general problem. Cards are *inserted* rather than *swiped*, which makes it almost trivial for people to rig the machines to prevent the card from being returned. A card swipe, where the card never leaves my hand, would be infinitely preferred to leaving my bank card at the mercy of any hoodlum with a bottle of soap and a pair of pliers.

    4) Apparently the ATM card I recieved is more than I asked for... it is also a credit card AND a debit card AND who knows what all else... if they acquire it they can run me down even if I don't have any money left in the account proper.

  3. Re:Only a matter of time by Black+Acid · · Score: 5, Informative
    The PIN is four decimal digits = 10,000 combinations ~= somewhere between 13 and 14 bits of security.

    For those interested, you can find how many bits a key with x values is using logarithms:



    bits = log(x) / log(2), or

    bits = d / log(2)

    Where d is the number of decimal digits the key is. Therefore, a 4-digit PIN has 4/log(2) or precisely 13.287712379549449391481277717958 bits of cryptographic strength. Not much compared even to weak encryption such as 64-bit DES, or the 56-bit des-ii cracked by d.net.

  4. Related technical paper by dazed-n-confused · · Score: 4, Informative

    If you want more technical detail, check out the
    paper on API-Level Attacks on Embedded Systems by Mike Bond and Ross Anderson.

    Ross Anderson is the author of "Security Engineering" -- if you're interested in this story but haven't read the book, consider this a strong recommendation. More details inc. sample chapters at his website. Plus other fascinating stuff.