From the imxge wxll today
Source twitxr imxge wxll
Post Links
Flux Share |
Bookmark |
Permalink | Trackback |
Email to a Friend |
Leave a Comment
Cloning passport card RFIDs in bulk for under $250
Post Links
Flux Share |
Bookmark |
Permalink | Trackback |
Email to a Friend |
Leave a Comment
phpMyID ?
The phpMyID documentation states:
Remember, BOTH the openid.sever and openid.delegate values should be set to
the same thing.
Forcing me to add a “openid.delegate” to this blog. For testing this is a good enough but not if you want to use http://broerse.net/wordpress/ as your “openid.delegate”. I almost want to write perlMyID to fix this.
Post Links
Flux Share |
Bookmark |
Permalink | Trackback |
Email to a Friend |
Leave a Comment
Testing OpenID
I just created http://broerse.net/wordpress/ as my OpenID provider using phpMyID (not Perl). I only enabled yadis support but now I can only login to half the OpenID enabled sites. I can put meta <http-equiv="X-XRDS-Location" content="http://broerse.net/id/yadis.xrdf">in the head HEAD sections of HTML documents and remove .xrds from the header but I think some sites just do not support yadis and look for headers like this:
<link rel="openid.server" href="http://broerse.net/id/" />
<link rel="openid.delegate" href="http://broerse.net/wordpress/" />
This diversity opens the way for a lot of errors. You can enter differed data in your header than in the head section and when you add the “link” items you can create 3 different OpenID’s on one URI and get one of them seemingly at random. One site I logged in to even changed my OpenID to the yadis URI. It seems yadis support is not what it is supposed to be. Some sites use the first item in the yadis file discarding the “Service priority” adding even more “random” identities to an URI. I hope the OpenID foundation will add an OpenID validator to the site to battle this issues.
Post Links
Flux Share |
Bookmark |
Permalink | Trackback |
Email to a Friend |
Leave a Comment