This may be seen as a bit much but in a post way back when I noted that you can find secrets by dumping the memory device to a file and grepping it. I was able to eliminate this danger by writing junk characters to the secret string to fill its entire previous length before destroying it.
When I have been in similar situations to yours I would overwrite the string after using it, and if it had to remain across states, then would encrypt it and store it as a hidden form field in the html returned to the user. Otherwise you can store a hash or just the last 4 digits if you wish. I believe the crypt function is one-way too; if you are using mysql you can store it in a password field. But you should do periodic cleaning, I would always clean old sessions after finishing a user's transaction.
-
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.
|