aboutsummaryrefslogtreecommitdiff
path: root/doc/news/openid
diff options
context:
space:
mode:
authorhttp://blipvert.myopenid.com/ <http://blipvert.myopenid.com/@web>2010-09-22 20:10:26 +0000
committerJoey Hess <joey@kitenet.net>2010-09-22 20:10:26 +0000
commita31d6ab1b9ca061b565d976f754c11b1bef7a325 (patch)
treeb07edf68096f45ff7e413b1b828fd83ae78a1ce4 /doc/news/openid
parent6902f9850a1f1c6e7eca9fab29ec98d4e7d9df3a (diff)
downloadikiwiki-a31d6ab1b9ca061b565d976f754c11b1bef7a325.tar
ikiwiki-a31d6ab1b9ca061b565d976f754c11b1bef7a325.tar.gz
Diffstat (limited to 'doc/news/openid')
-rw-r--r--doc/news/openid/discussion.mdwn5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/news/openid/discussion.mdwn b/doc/news/openid/discussion.mdwn
index fa8acb942..a79a87989 100644
--- a/doc/news/openid/discussion.mdwn
+++ b/doc/news/openid/discussion.mdwn
@@ -82,5 +82,8 @@ which fails here? Or is something broken in Ikiwiki's implementation?
Yes. I'd only recently set up my server as a delegate under wordpress, so still thought that perhaps the issue was on my end. But I'd since used my delegate successfully elsewhere, so I filed it as a bug against ikiwiki.
----
-##Pretty Painless
+###Pretty Painless
I just tried logging it with OpenID and it Just Worked. Pretty painless. If you want to turn off password authentication on ikiwiki.info, I say go for it. --[[blipvert]]
+
+###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]]