comment on

you just do the file (or you eval the result of the database query), and your second program can use the value computed by the first program.

... or discover that some black hat has replaced your file with one containing system('rm -rf /')

Data::Dumper is not a good method of doing persistence, because of the need to evaluate the stored file as actual Perl code using do or eval your code is only as secure as your file storage.

If you must have a Human Readable persistent storage then you probaby want to look at Data::DumpXML or Data::Denter

with the former you might want to consider my talk from last years yapc::Europe about a security implication of deserializing Perl objects into your code.

/J\

In reply to Security Issue with Data::Dumper as a persistence mechanism by gellyfish
in thread Data::Dumper in a nutshell? by munchie

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.


Problems? Is your data what you think it is?
	PerlMonks