Slashdot Mirror


Australian Gov't Offers $560k Cryptographic Protocol For Free

mask.of.sanity writes "Australia's national welfare agency will release its 'unbreakable' AU$560,000 smart card identification protocol for free. The government agency wants other departments and commercial businesses to adopt the Protocol for Lightweight Authentication of ID (PLAID), which withstood three years of design and testing by Australian and American security agencies. The agency has one of Australia's most advanced physical and logical converged security systems: staff can access doors and computers with a single centrally-managed identity card, and user identities can be automatically updated as employees leave, are recruited or move to new departments. PLAID, which will be available soon, is to be used in the agency's incoming fleet of contact-less smartcards that are currently under trial by staff. It will replace existing identity cards that operate on PKI encryption."

16 of 163 comments (clear)

  1. So when it gets replaced by courtjester801 · · Score: 5, Funny

    Can it be referred to as the Former Lightweight Authentication of ID, or FLACID?

  2. A little more info by explosivejared · · Score: 4, Informative

    Here is a briefing on the PLAID 6 protocol with more specifics on the actual algorithms and cryptography in general involved. PDF link if the first one doesn't work for you.

    --
    I got a catholic block.
    1. Re:A little more info by TechyImmigrant · · Score: 4, Informative

      The protocol looks unremarkable. They pass some entropy and IDs back and forth, using conventional standards based encryption and hash algorithms.

      Their problem is keeping the cards secure and they state clearly that they are using commercially available smart cards.

      There are secrets in the cards, an RSA private key and an AES master key. The bigger problem is keeping these secrets in the cards and distributing the keys to cards. The PLAID protocol has no bearing on these matters.

      --
      Evil people are out to get you.
    2. Re:A little more info by swillden · · Score: 5, Informative

      There are secrets in the cards, an RSA private key and an AES master key. The bigger problem is keeping these secrets in the cards and distributing the keys to cards. The PLAID protocol has no bearing on these matters.

      Which is fine, because those problems are easily solved.

      Commercially-available smart cards provide a rather high degree of security. Extracting keys from them isn't impossible (nothing is), but it is very difficult and expensive. I design high security systems for a living, and we have no concerns about the security of the cards themselves, because experience shows it's just not an issue.

      What we do focus on is the security of the issuance process, because that's where those keys get injected. That problem is also solvable, mainly by performing the key injection in secure facilities using highly secure devices (FIPS 140-2 level 4 certified hardware security modules). It's expensive and complex (from a management and process perspective, not a technical perspective), but a high degree of security is achievable.

      The protocol looks unremarkable. They pass some entropy and IDs back and forth, using conventional standards based encryption and hash algorithms.

      It is unremarkable, which is one of its most significant strengths. It's just a lighter-weight approach to the problem, one that can be implemented efficiently on current-generation hardware. Previously, PK authentication on smart cards was considered too slow to use for physical access control and other applications where sub-second authentication was required. Faster smart cards coupled with a lightweight authentication protocol mean that PK authentication can be completed reliably in as little as 200 ms. That's fast enough to use it for transit applications.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    3. Re:A little more info by owlstead · · Score: 4, Interesting

      The protocol looks unremarkable. They pass some entropy and IDs back and forth, using conventional standards based encryption and hash algorithms.

      That's a good thing.

      Their problem is keeping the cards secure and they state clearly that they are using commercially available smart cards.

      Which is also a good thing, as long as these cards have been analyzed well. I would be worried if they were using cards with "military grade" security meaning that they were only analyzed by few, without any standardized security level like FIPS or CC.

      There are secrets in the cards, an RSA private key and an AES master key. The bigger problem is keeping these secrets in the cards and distributing the keys to cards. The PLAID protocol has no bearing on these matters.

      Sorry, but you are wrong on both matters.

      The RSA private key and AES master keys are not on the card. It contains the RSA public key and the AES derived key (one that is specific to the card).

      There are many interesting things about this protocol. Lets have a list so I can get a few mod points on this old discussion:

      • No ID before authentication (card ID is encrypted with public RSA key, standard RSA encryption uses random padding)
      • No RSA private key encryption for the authentication (vulnerable to attack)
      • Uses standardized, up to date algorithms (SHA-1 is only used in a secure way as far as I can see)
      • Uses RSA public key on the card, which is *faster* than ECC because the public exponent will likely be small (010001h normally)

      Ok, for some disadvantages

      • Requires contact-less processor card with AES and hardware RSA support
      • Access is much slower than with AES only authentication
      • Time and power usage of RSA calculations may make it more difficult to do a successful authentication
      • Unremarkable (probably has been invented earlier)
      • Requires terminal that performs RSA private key encryption
      • Requires RSA private key to be present on reader side, key cannot be revoked
      • Still requires a single master key (hopefully it will never be leaked)

      All in all, this protocol is very interesting for mutual authentication. I'll have to look into it further (e.g. how much the private key needs to stay private).

  3. PLACID by ajlitt · · Score: 4, Funny

    That's a much better acronym than the originally proposed Protocol for Automated National Identification and Control.

    1. Re:PLACID by Java+Pimp · · Score: 5, Funny

      That's a much better acronym than the originally proposed Protocol for Automated National Identification and Control.

      Or the lesser known Protocol for Enhanced Network and Internet Security.

      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    2. Re:PLACID by Red+Flayer · · Score: 4, Funny

      But any of us with good fashion sense would prefer the Protocol for Authenticating Identification Systems with Latent Encryption Yobs over the original PLAID anyway.

      --
      "Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
  4. Yeah Right... by Frosty+Piss · · Score: 4, Insightful

    Given Australian government's views on privacy, I wonder when the back door will be discouvered? Or is looking for it agianst the law?

    --
    If you want news from today, you have to come back tomorrow.
  5. Mmmh by Britz · · Score: 5, Insightful

    "Here, have my lock and key. Nobody will be able to get into your home. Except, maybe, me :-)"

  6. I laugh ... by Morphine007 · · Score: 4, Insightful

    ... when an organization claims that they're going to provide something that's unbreakable

    The claim is usually an open invitation to reduce the "unbreakable" object to ashes.

    1. Re:I laugh ... by mark-t · · Score: 4, Interesting
      Meh.... unbreakable encryption is easy, or so close to it that the difference is largely irrellevant:
      1. Find any two nice and large prime numbers and publish them. Call them A and B. Call their product C. Let n = one less than the number of bits in C.
      2. Both the source and destination can pick any number that is coprime to (A-1)*(B-1), call them Xs and Xd. They do not share this information.
      3. The source and destination then compute Ys and Yd, respectively, such that their own X*Y is congruent to 1 mod (A*B). They do not share this information.
      4. The source takes n bits from the data, D, and applies the following transform: D = D ^ Xs mod C. This data is transmitted.
      5. The destination then applies the transform D = D ^ Xd mod C and transmits that back to the source.
      6. The source applies the transform D = D ^ Ys mod C and transmits that to the destination
      7. The destination finally applies D = D ^ Yd mod C, and in this final transform retrieves the unencrypted data.

      This allows one to completely securely transmit up to n bits of data from a source stream, and because the source and destination can pick new X and Y values with every transmission, and unencrypted data is never found on any transmitted data stream. The likelihood of breaking it is genuinely 1 in 2^n and can only be broken by brute force attack. Factoring methods will not break the encryption because what would normally be associated as a public/private key pair (X,Y) in some other encryption protocols is never shared with the other party.

    2. Re:I laugh ... by smallfries · · Score: 5, Informative

      That looks familiar but I can't remember the name, what scheme is it?

      The likelihood of breaking it is genuinely 1 in 2^n and can only be broken by brute force attack.

      That's not strictly true. Although the discrete log problem is hard it is still a computational assumption. Proving that 2^n is a lower bound would be a significant achievement. This scheme is only "unbreakable" in the sense that RSA is - breaking it requires solving a problem that we suspect, but are unable to prove, is very hard.

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
  7. PLAID 6 Protocol by Anonymous Coward · · Score: 4, Informative

    * Uses existing off-the-shelf symmetric and asymmetric crypto algorithms (SHA1, AES 256, RSA 1024, RSA 1984) tied together via the PLAID protocol
    - Note - Neither SHA256 nor ECC are used at this time because production cards are either not obtainable from all vendors nor do they achieve the required performance, (in spite of theoretical advantage of ECC)
    - Note - RSA 1984 is a trade off between performance and security, and ensuring the transaction fits in one APDU command.
    * Fast & simple - less than 1/2 second (400ms) and the Java Card - applet is extremely small (about 4 Kb)
    * Not clone-able, re-playable or subject to privacy or identity leakage
    * Same protocol can be used for PACS/LACS & contact/contactless
    * PIN can be verified when card-not-present by comparing PIN hash
    - Saves user having to hold contactless card to reader during typical PKI session
    * Mutual authentication Protocol
    * Algorithms used are commercially available on virtually all modern smartcards including Java
    Card, MULTOS, most SIMs and many proprietary cards
    * Algorithms and their selected key lengths have been tested on production cards and devices to ensure speeds are real, not theoretical

    * No IP issues - IP was developed solely by the Australian Government by its agency, Centrelink, and will be openly and freely licensed
    * Designed to be used either stand-alone or as a bootstrap into other specifications like Australian IMAGE, US PIV, ICAO Passports etc.
    * Supports multiple concurrent specs dependant on device request to card
    - i.e. Card could supply Weigand number or CHUID or Centrelink CSIC or Passport MRZ etc etc dependant on use case
    * Supports multiple (256) key sets dependant on device request to card
    - i.e. there might be a "perimeter key set" and a "high security key set" and a "LACS key set" and an "administrative key set" etc etc and the terminal device only requests the one it requires, reducing the possibility of compromise of the others.
    - The key sets can be rolled, by loading spare unused key sets (up to 255) in case of compromise (memory is the limitation)
    * Optionally provides session keys for higher level specs
    * Protocol can be registered and implemented under ISO/IEC 24727-3 and 6, and either used under ISO/IEC 24727or implemented separately

    However:
    Slightly slower than existing physical access Tag and proprietary solutions (by 0.2 to 0.3 seconds)
    - Keys MUST be distributed & managed
    * Vendors need to build key management for PLAID into existing or new key management systems. (Centrelink vendor is doing this for LACS)
    * PACS using older Weigand technologies need secure SAM devices in the readers
    * Newer PACS can utilise back end HSM devices/SAMs on the network or in distribution frames

  8. Re:contactless smart cards are the way to go by Burkin · · Score: 4, Interesting

    Until you lose your wallet and the person who finds it has complete control to ruin every aspect of your life connected to said card... ...

    Yes, because clearly they would have no system to revoke lost cards.

  9. Re:contactless smart cards are the way to go by profplump · · Score: 4, Insightful

    The government never issued SSN with the intent of being a universal identifier.