Offering secure logins doesn't help verify someone elses identity unless the insecure interface is shut down. Just because you can login in via a secure channel does not mean that the person who posted a link to their code never used the insecure interface.
Are you offering to pay for the site certificate? If not, the site will probably have to run with a self signed certificate. Would that make you feel more secure? A self signed certificate wouldn't mean a whole lot more to me than what we have now.
For the most part, things that get posted here are small snippets that can be easily audited by any competent perl programmer in a few minutes. Links to larger things are provided but the authenticity of those providers is better checked in other ways than a secure login here (like MD5 signatures with a verifiable key).
90% of every Perl application is already written. ⇒ | dragonchild |
-
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.
|