Why it is (sometimes) ok to shoot yourself in the foot

I got this link on a list earlier today: Facebook (2 step authentication) fail !

I totally disagree with almost all the assumptions and conclusions of that post. The only bit I can sort-of agree with is that maybe, just maybe it is not a good idea to allow you to opt out of security without proving your identity with a higher level of assurance but I can also totally grok why FB is doing it this way. The reason is spelled “support costs”.

The fundamental mistake of the post is this: The author assumes that strong(er) authentication (eg 2-factor) should be at the discretion of the site owner.

As content owner (my facebook page, my crap) in this case, I carry most of the risk associated with protecting my data. It is therefore totally fine to let me bypass security if I want to – up to a point.

At some point FB assumes some basic level of risk and responsibility which is why they won’t let me create an account without a password.

If this were a bank the border between personal risk and site-owner risk would shift – in part because the law mandates a higher level of responsibility on the part of the bank than in the case of FB.

Higher level-of-assurance/protection is successfully introduced for one of two reasons:

  • the user values his/her data (cf blizzard tokens)
  • “the man” (eg the government) tells you how it must be

Luckily FB isn’t “the man” – at least not yet – and isn’t in a position to force users into valuing their data above a level that is minimally accepted by most users.

This is the reason strong authentication almost always fails when faced with reality: most of us security nerds don’t share the same gut-reaction with respect to data value than most “normal” users and therefore we are willing to accept a higher degree of hassle when it comes to protecting that data.

This brings me back to the fundamental point: the cost of introducing strong authentication is not in tokens, provisioning or identity proofing. Most of the cost is in support. The simple truth is that most ways we have devised to improve security of the authentication step in any protocol suck from a UI perspective. Fundamentally all such measures (be it SMS codes, OTP tokens or so called “smart” cards) all introduce extra steps in the login process. This means that they are seen by the user as an obstacle that he/she must overcome before they can get at whatever content they were going for.

Incidentally this is related to click-through terms-of-use dialogs but that is another story and another blogpost.

It is worth noting (as I usually try to do when this topic comes up in conversation) that some of the most successful deployments of 2-factor tokens are in the gaming industry and I firmly believe that in these cases the user values their data sufficiently much to accept the additional obstacles imposed by stronger authentication.

I also firmly believe that anyone who can design a truly user-friendly strong authentication mechanism would get rich pretty fast and would do a great service to the Internet.

8 Comments

Filed under Uncategorized

Why you should care about the CABforum

The CA browser forum (aka CABforum) announced a couple of days ago that they would form a WG on “organizational reform”.

Why is this important I hear you say?

The CABforum has quite a lot of power. This group makes decisions that affect which CAs are chosen for inclusion in default browser trust stores. Currently the group is comprised of browser and CA vendors. Notably absent are any relying parties.

Here is how to participate (quoted from the cabforum.org announcement):

In support of this process, the special working group is soliciting short (no more than 750 words, please) position papers and statements of interest from organizations and individuals on these topics. We encourage stakeholders to submit their comments to questions@cabforum.org now through March 30, 2012. All submissions will be posted publicly on the CA/Browser Forum website. (www.cabforum.org)

Comments Off

Filed under Trust

convergence & federations?

Convergence is one of several proposed solutions to the problem of lying and poorly managed CAs. DANE is of course another. I like fighting on multiple fronts so when rlbob sent me an inspirational email today after listening to Moxie talk about convergence at #RSAC I just could not resist it.

To make a long story short I went and setup a convergence notary. If you feel like trusting it feel free to visit https://etc.mnt.se/mnt.notary but make sure you visit convergence.io and install their FireFox plugin first.

Here then is the rlbob challenge:

The Chrome guy says they can’t use convergence because the traffic load would be too high for anyone but them to support, and they can’t be the ones to validate pubkeys for their own browser. In steps a worldwide network of registrars run by R&HE using our spare computing power and bandwidth. Let’s do it!

Lets see what happens next!

Comments Off

Filed under Trust

Not posting enough

Clearly the blog has been, if not dead then asleep for quite some time. I have no idea if people are even reading this but I’ll start posting again presently. My lack of updates has not been due to lack of activity!

Comments Off

Filed under Uncategorized

Gaps to Map

Right before the IETF in Anaheim I’m off to the ISOC Identity event: Mapping the Gaps in DC. This post is a set of possible discussion points for that event. The event will focus on the gaps between the technological and policy/legal view of the identity metasystem.

Standardized Federation Policy and Practice Statements

Building identity federation involves establishing policy documents and practice statements analogous to the CP and CPS of a PKI. In the world of public key infrastructure there are templates to start from – RFC 3647, ETSI TS 102 042, ANSI X9.79, etc. In the world of federations there is no such help. We need those and we need them to be simpler (if possible) than their PKI cousins.

Simplified/Standardized Federation Contracts

Joining a federation (as an SP or IdP) often involves signing some form of contract. For an SP joining multiple federations the fact that no two contracts look alike soon becomes a problem. There are at least two ways around this:

  • Make the contracts easily comparable – i.e standardize!
  • Do away with the contracts all together.

In may situations having a contract will probably be inevitable but in certain cases it might be perfectly reasonable not to have a contractual relationship between (say) an SP and a federation. I’ve blogged about this and there has been some work in this area.

Separate technical trust from federation metadata

Technical trust for identity federation is often (at least in many R&E federations) represented as signatures on SAML metadata documents which contain keys for the member entities. This works (often better than using a traditional PKI) but it does tie technical trust management in with a particular identity technology. We need a way to represent technical trust which is easier to setup and maintain than PKI and which can be applied to all identity technologies in use today.

Comments Off

Filed under Uncategorized

Computer Sweden picks up on Swedish eID problems

Computer Sweden har intervjuat Fredrik Ljunggren på Kirei om vår blog-plost om federerad e-id i Sverige.

Dom har faktiskt uppfattat budskapet riktigt väl!

Comments Off

Filed under E-delegationen

Kammarkollegium och organisationslegitimationerna

Det är svårt att tänka om.

Nyligen kom e-delegationen ut med sitt betänkande kring bla eID där man tydligt säger att man vill satsa på identitetsfederationer och på öppna lösningar för identifiering i Sverige. Ingen blir nog förvånad om Skatteverket kommer att få ansvara för nämnden för e-samordning och om Kammarkollegium kommer att få göra alla upphandlingar som blir resultatet av de standarder och regelverk som nämnden förhoppningsvis kommer att etablera. So far so no surprises…

Det är därför med växande förvåning jag har följt hanteringen av sk organisations-legitimationer hos Kammarkollegium under sommaren och hösten. Där har man suttit och räknat ut att X509-certifikat med både personnummer och organisationsnummer är det bästa sättet att representera att NN jobbar på firma X.

Alla som har någon insikt i hur identitetssystem byggs idag inser att det finns en del problem med ett sådant angreppsätt och att en modernare lösning kanske hade varit att jobba med teknologi som kan hantera attribut i någon form, tex OpenID, SAML, InfoCard eller varför inte attributcertifikat!

Trots att det alltså finns invändningar i sak och ett uppenbart behov att samordna med nära förestående arbete inom ramen för nämnden för e-samordning så kör Kammarkollegium på som om inget har hänt…

Idag var det informationsmöte på Sheraton. Det kändes lite som att sitta på en diskussion i 15 punkter kring färg, form, placering, material och distribution av havrepåsar för framtidens hästlösa vagnar. Vid varje punkt påpekade någon i publiken att det kanske inte behövs en häst eller att om det behövs en slags häst så kanske det är en järnhäst som inte äter havre. Efter varje diskussion så gick presentationen av nästa punkt vidare (“.. och såhär tror vi att havrepåsen ska spikas fast…”).

Någon påpekade helt korrekt (om också tämligen irrelevant) att det kan finnas användning av certifikat med organisationsnummer instoppade även om man använder federationsteknologi.

Jo man kan ju vilja leda en häst bredvid bilen och då vill man kanske ha en havrepåse…

Som vanligt i dessa sammanhang så drog någon med jämna mellanrum fram “signaturs-kortet”: “Det går ju inte att göra offline signaturer med en sån däringa federations-pryl…”. Helt rätt. Man kan inte köra sin hästlösa vagn ut i skogen om man skulle behöva avverka ett träd på vägen mellan Konsum och hemmet men genom att optimera för det vanligaste fallet (identifiering) så blir hela systemet så mycket billigare att man har råd att hyra sig en skogsmaskin när man behöver den.

Vi behöver mer konkurrens inom eID i Sverige, inte mindre! Kammarkollegium har ett ansvar att göra upphandlingar som inte i onödan begränsar spelplanen till de få företag (jag kan räkna dom på ena handens fingrar även om jag har tappat ett par fingrar) som utfärdar den typ av ḱort som Kammarkollegium uppenbarligen har i åtanke. Jag menar att Kammarkollegium (om man alls ska ge sig in i detta) bör bredda upphandlingen till att inkludera all teknologi som rimligen kan anses ha samma nivå av tekniska skydd som ett klassiskt PKI-kort, tex olika former av OTP-tokens som av goda skäl blivit allt mer populära på senare tid.

I och med etableringen av federations-lösningar så spelar det ingen roll vad som används för inloggningen så länge det finns ett assuransnivå-begrepp (LoA) som både identifierande part och förlitande part kan enas om. Sådana assuransbegrepp finns det flera färdiga man kan använda – tex Kantara Identity Assurance Framework som av allt att döma är bra nog för att bli godkänt för användning inom USAs statsförvaltning.

Missförstå mig rätt nu – jag gillar 2-faktors-inloggning! Jag menar bara att efter 10+ år med PKI-kort som flaxar med armarna och aldrig lyfter så är det hög tid att vi släpper in några nya spelare i laget och ser om dom lyckas bättre. Federationsteknologi är bla ett sätt att göra spelplanen lite öppnare och lite jämnare.

Comments Off

Filed under E-delegationen

Swedish national SAML federation?

The long-awaited (at least if you’re Swedish and interested in public sector IT which does rather limit the audience a bit) e-delegationen report was released today. The section on national identity solutions says “SAML” and “federations” over and over.

On the whole the report promises a significant improvement over todays proprietary solutions. There is still lots of work left to do in order to realize these ideas. Those of us who have worked in identity space for a while know that there are plenty of opportunities to shoot oneself in the foot even if you have the right shoes on.

For reasons that escape me Sweden has a bit of a track record trying to “roll your own” in areas where there are plenty of existing standards and market direction, but this time I do believe e-delegationen is betting on the right horse. Good work!

Comments Off

Filed under Identity

Stork & InfoCard (and maybe U-Prove)

Paul Madsen twittered this networworld article about what i guess must be one of the first public appearances of the EU Stork project.

Kim Cameron and MSFT seem to be shopping InfoCard and Geneva all over the place these days so their comments about Stork shouldn’t be surprising to anyone. The article claims that InfoCard has seen solid industry uptake which may be true but according to the recent Concordia Survey on Federated Identity InfoCard has a very small deployed base.

Nevertheless I think it reasonable to think that InfoCard will get deployed more, even in the R&E community where federated identity is already a Big Thing (TM).

InfoCard shares important infrastructure with SAML making it fairly easy to deploy alongside SAML (even though the semantics and user experience of SAML WebSSO and InfoCard differ quite a bit), namely SAML metadata which, when deployed “the right way” becomes the primary trust fabric of an identity federation. Microsofts Geneva was apparently designed around the same principles of how SAML metadata should be used as is fast becoming best practice among R&E identity federations.

So we learn that STORK will consider SAML 2.0 and holder-of-key as the primary way to interface national eID solutions in the European countries. I really hope they understand that the devil is in the details and design metadata management and trust fabric management in a sensible way.

One can only wonder what lies behind Microsoft pushing Geneva all over the place. Typically Microsoft aren’t happy just following where others lead. Perhaps the idea is to include the U-Prove technology they bought with Credentia last year in Geneva and embrace and extend the identity federation framework…

Then again once you can see the threat it is suddenly less of a threat. The famous embrace and extend tactic is precisely that: famous. People who are interested in open standards and open implementations should recognize where the ball is being played and start to think about how to implement U-prove.

1 Comment

Filed under Identity

Metadata license becomes metadata terms-of-use

Andrew Cormack of ja.net talked at the REFEDS meeting today about recent work they have done on standardizing interfederation agreements. One interesting announcement was that they’ve picked up my old idea of associating a license with federation metadata. They ran this by a set of lawyers who basically said: “don’t call it a license, call it terms-of-use and you’re fine”.

This has the potential of simplifying federation operations (including federation peering) significantly since service-providers don’t have to be tied to federations by legal agreements. For multi-federation service-providers like Microsoft Dreamspark or Elsevier this is good news since they may in time get away from having to sign agreements with every federation on the planet.

While this may seem like a bad idea for federations whose business was driven by being able to charge SPs for inclusion in metadata in the long run everyone benefits from the identity business growing with the removal of a major obstacle.

2 Comments

Filed under Identity