From 954b6353b029062418b911114baa9f86b216e44e Mon Sep 17 00:00:00 2001 From: "http://lovesgoodfood.com/jason/" Date: Sun, 26 Sep 2010 04:18:15 +0000 Subject: [PATCH] --- doc/news/openid/discussion.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/news/openid/discussion.mdwn b/doc/news/openid/discussion.mdwn index c0447a13f..fdd5eecd1 100644 --- a/doc/news/openid/discussion.mdwn +++ b/doc/news/openid/discussion.mdwn @@ -90,3 +90,5 @@ I just tried logging it with OpenID and it Just Worked. Pretty painless. If yo ###LiveJournal openid One caveat to the above is that, of course, OpenID is a distributed trust system which means you do have to think about the trust aspect. A case in point is livejournal.com whose OpenID implementation is badly broken in one important respect: If a LiveJournal user deletes his or her journal, and a different user registers a journal with the same name (this is actually quite a common occurrence on LiveJournal), they in effect inherit the previous journal owner's identity. LiveJournal does not even have a mechanism in place for a remote site even to detect that a journal has changed hands. It is an extremely dodgy situation which they seem to have *no* intention of fixing, and the bottom line is that the "identity" represented by a *username*.livejournal.com token should not be trusted as to its long-term uniqueness. Just FYI. --[[blipvert]] +---- +Submitting bugs in the OpenID components will be difficult if OpenID must be working first... -- 2.32.0.93.g670b81a890