{"id":702,"date":"2007-03-04T15:34:08","date_gmt":"2007-03-04T23:34:08","guid":{"rendered":"\/?p=702"},"modified":"2007-03-04T16:01:53","modified_gmt":"2007-03-05T00:01:53","slug":"identities-on-multiple-devices","status":"publish","type":"post","link":"https:\/\/www.identityblog.com\/?p=702","title":{"rendered":"Identities on multiple devices"},"content":{"rendered":"

As I said here<\/a>, I want also to look at a second strange claim<\/a> by Eve<\/a>: <\/p>\n

On another issue, she noted that OpenID 1.0 has a vulnerability in that it leaves users’ identities open to possible correlation by unauthorized third-parties.<\/p>\n

But that CardSpace has a vulnerability of an opposite but equally problematic nature. Given that each CardSpace is associated with a particular client device (i.e., a particular desktop, laptop, or mobile phone running Vista), and given the fact that each user might have multiple such devices, each with a multiplicity of cards running on them…that the more such devices, cardspaces, and i-cards multiply for a given user, the more difficult it will become for a particular user to correlate the various fragments of their identity across their own personal “space.”<\/p><\/blockquote>\n

This really<\/strong> strikes me as bizarre.  Maybe Eve was asleep while the entire world learned to copy mp3s onto their music players and carry them around?  Duh.  We know how to move files from device to device.  In fact there are probably many hundreds of millions of people who can do it better than either Eve or I can.<\/p>\n

The idea that this is the big vulerability of CardSpace boggles my mind.  The whole criticism “Does not compute.”<\/em><\/p>\n

Then again, I actually use<\/em> Information Cards, and move them from device to device, so maybe that's why it's so clear to me how easy it is to do. <\/p>\n

Let me share the exact experience I have installing the Information Cards from my PC's CardSpace onto my mobile phone.<\/p>\n

 Moving Information Cards from device to device<\/strong><\/p>\n

1)  I open up CardSpace and select Back Up Cards.  This will create a file containing my cards.  I decide to call it “cardset”.<\/p>\n

<\/p>\n

2) I copy ‘cardset’ to my phone and click on it:<\/p>\n

<\/p>\n

3) The phone asks for the password I used to protect my file<\/p>\n

 <\/p>\n

4) It verifies I'm importing the right cards<\/p>\n

<\/p>\n

5)  And now I have the same cards on my phone device as on my PC.<\/p>\n

<\/p>\n

How hard is that?  It would be the same process copying the file to some other device.  It works fine.  As easy as getting a word document or powerpoint or mp3 from one place to another.  Dongle anyone?  How about email?<\/p>\n

Still, the uberpoint is this:  once Information Cards live on my phone, they go whereever I go. <\/p>\n

There are lots of ways phones can potentially talk to other devices.  So who says we have to copy our cards to all our devices once they live in a secure, personal device like a phone that we always have with us?<\/p>\n

NOTE<\/strong>:  I want to point out that the mobile implementation of CardSpace I'm showing here is NOT a product.  It's a way of learning about the issues, and collaborating with colleagues in the world of telecom and secure portable devices.  But hey!  It's still a lot of fun.  More later.<\/p>\n","protected":false},"excerpt":{"rendered":"

Eve thinks CardSpace has “a vulnerability of an opposite but equally problematic nature…”<\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[8,15,11,5,4],"tags":[],"_links":{"self":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/702"}],"collection":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/users\/68"}],"replies":[{"embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=702"}],"version-history":[{"count":0,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/702\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}