more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
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
|
|