Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

Nitrox:

I'm liking this thread, and it was interesting to hear why you are using File::Cache. Just a couple of things:

  1. Create a group for your 'short running scripts' and long running daemon to be a part of (this is probably possible in Win32 :).) Have the File::Cache write it's hierarchy to a place where only people in the group can read/write.
  2. Use a key, and encrypt the cache values. If you don't care if people can read through your keys, then this can add a smidge of integrity. That is, agree on a 'password' for all data being written to the key and then use an symmetric Crypt:: module.

Hope that's helpful...Good luck!

By the way, did you notice that on the File::Cache actually recomends using Cache::Cache instead? Hm...

Kurt


In reply to Re^2: Adding a bit of security to Cache::FileCache by whereiskurt
in thread Adding a bit of security to Cache::FileCache by Nitrox

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.