comment on

"To me it does matter. If it's not secure, somebody could easily log in as moritz, and with a few writeups could destroy the reputation (and perhaps even trust) that I built by writing more than 2000 posts."

Right, I see why having your account broken into is something that bothers you (and me), but that could happen in any other form as well (again: Yahoo! Palin. Mail). First of all, the "attacker" has to guess which provider you used (obscurity, yes never good). In this case, Perlmonks would be an easy guess.

Secondly, the "attacker" needed to somehow authenticate at Perlmonks with your credentials. So, rather than fearing OpenID being insecure, you really shouldn't trust Perlmonks security. So here it boils down to what OpenID provider you trust.

I haven't seen stories where OpenID was spoofed (if you have stories, please let me know). I can only think of DNS attacks (?).

--
b10m

In reply to Re: PerlMonks OpenID provider? by b10m
in thread PerlMonks OpenID provider? by friedo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.