summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://lovesgoodfood.com/jason/ <Jason_Riedy@web>2010-09-26 04:19:29 +0000
committerJoey Hess <joey@kitenet.net>2010-09-26 04:19:29 +0000
commit896adeafda0b81227ca54f058b18f7c3aadd318c (patch)
treedae2352e61e2b161a0e385334e82ba018aea278e
parent954b6353b029062418b911114baa9f86b216e44e (diff)
(fixing silly formatting issue)
-rw-r--r--doc/news/openid/discussion.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/news/openid/discussion.mdwn b/doc/news/openid/discussion.mdwn
index fdd5eecd1..bc9856ad9 100644
--- a/doc/news/openid/discussion.mdwn
+++ b/doc/news/openid/discussion.mdwn
@@ -90,5 +90,7 @@ 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...