I remember a PAR presentation online (maybe Autrijus') in which he suggests putting one critical module on a remote server. However in addition to liability resting on your neck now, it isn't secure and can be read by the user or admin if they really wanted to read it. What is your security need? Do you mean "can't be stolen and resold", "they have to pay", "has to be liscensed per user", "Don't want them to see my dirty code", "want to encrypt server traffic", "want to protect passwords and credit card numbers", or what? If the person running the server is your enemy, the answer is no. But you can do some secure things in perl i.e. regarding webapps.
-
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.
|