{"id":414,"date":"2006-03-19T10:18:56","date_gmt":"2006-03-19T18:18:56","guid":{"rendered":"\/?p=414"},"modified":"2019-03-06T09:11:03","modified_gmt":"2019-03-06T15:11:03","slug":"my-friend-the-attacker","status":"publish","type":"post","link":"https:\/\/www.identityblog.com\/?p=414","title":{"rendered":"MY FRIEND THE ATTACKER"},"content":{"rendered":"<p>In my recent post on <a href=\"\/?p=410\">Hardy Infocard Pioneers<\/a>, I refered to the fact that the first &#8220;attack&#8221; had been made on the site.  Apparently, I wasn&#39;t clear enough about the fact that I saw this as a <strong>good thing <\/strong>&#8211; something I appreciated.  That led to this comment from Rohan.<\/p>\n<blockquote>\n<p>Hi Kim,<\/p>\n<p>An Attacker. thats a nice title, when the intention was not to \u00e2\u20ac\u0153attack\u00e2\u20ac\u009d but try to look at infocards from the other side. From another perspective altogether. Everybody seems to just nod heads when workflows and use case examples are explained. I have not seen many who have tried to disagree in the \u00e2\u20ac\u0153open\u00e2\u20ac\u009d.<\/p>\n<p>Well, I am trying to do just that. Not disagree, but to look at it from another angle, and talk to you about my discoveries. <\/p>\n<p>I\u00e2\u20ac\u2122m sure that youd\u00e2\u20ac\u2122 acknowledge, that I \u00e2\u20ac\u0153did\u00e2\u20ac\u009d inform you as soon as I logged into your site with FAKE info. Well, thats not called an \u00e2\u20ac\u0153attack\u00e2\u20ac\u009d.<\/p>\n<p>As far as the \u00e2\u20ac\u0153browsehappy.com\u00e2\u20ac\u009d link goes, thats just a joke\u00e2\u20ac\u00a6<\/p>\n<p>Like you said : All of us will be attacked and all of us have to work hard &#8211; and together &#8211; to create a safe internet. I AGREE with you. 100%. But lets be open to ideas that may be contradictory to our own\u00e2\u20ac\u00a6.. My efforts are to create a SAFE internet. To point out issues and errors, so that one may work on fixing them. <\/p>\n<\/blockquote>\n<p>So let me set the record straight.  I think Rohan is making a positive contribution to thinking about InfoCards.  I appreciate what he is doing for the very reasons he expresses.  And if you go to his site, you&#39;ll see how creative he is.<\/p>\n<p>I didn\u00e2\u20ac\u2122t mean \u00e2\u20ac\u0153attacker\u00e2\u20ac\u009d in the \u00e2\u20ac\u0153normal\u00e2\u20ac\u009d sense of the word &#8211; I was talking about THE ATTACKER ROLE we refer to as identity and security people, when we attempt, as he did, to think things through from the <em>viewpoint of an attacker<\/em>. <\/p>\n<p>I am delighted to have others in the community thinking through the possible attacks with me.  More about that in a minute.<\/p>\n<p>In terms of the browsehappy.com thing, it was obvious that Rohan was poking fun &#8211; and that&#39;s fine.  I just appreciated the opportunity to rail, en passant, against a couple of the site&#39;s more dubious claims.<\/p>\n<p>This said, I&#39;d like to be very clear about the status of the work I&#39;m doing here to InfoCard-enable my site.<\/p>\n<p>There are two parts to this project.<\/p>\n<p> The first is pretty much complete, and involved developing a way to consume and verify InfoCard SAML tokens using a typical LAMP server without installing binaries.<\/p>\n<p>The second is the part I&#39;m working on now.  It involves experimentatng with how to use InfoCards concretely from a web site &#8211; in this case my blog.  I&#39;m learning as I go.  After all, InfoCards are a relatively recent arrival on the scene&#8230;<\/p>\n<p>I&#39;ll publish various elements of code as it evolves &#8211; but I&#39;m writing this stuff personally as an exploration &#8211; it isn&#39;t a product, doesn&#39;t yet have a formal threat analysis,  hasn&#39;t gone through security reviews, and hasn&#39;t even been seen by anyone other than me before appearing here.  What you see is what you get.<\/p>\n<p> My thinking is that the security threat model and reviews will be done here as part of the blogoshere process.  And no doubt we&#39;ll find things to fix, working as a team.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thinking from the viewpoint of the &#8220;attacker&#8221; is essential to developing a security and privacy threat analysis.  I take this work as being a positive contribution.<\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[],"_links":{"self":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/414"}],"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=414"}],"version-history":[{"count":1,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/414\/revisions"}],"predecessor-version":[{"id":1723,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/414\/revisions\/1723"}],"wp:attachment":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}