(a bad boy can substitute one object file with somethins like system ("rm -rf /") and destroy my server).
If anyone you don't trust has write access to the dumps you're in trouble whatever the data format and I guess that anyone with write access to the dumps can run any code he/she wants anyway.
The fact that you're using DBM::Deep only removes the risk of running code from the dump - it doesn't stop anyone from breaking your application.
Also, IIRC DBM::Deep doesn't really support objects, so if your probeset object contains references to other objects, they won't be blessed back. You might want to consider FreezeThaw or Storable.
update: I should probably point out that neither FreezeThaw nor Storable do automatic updates to the storage if the data in the object changes, so that could be a problem. As far as I know there is no direct DBM::Deep equivalent for objects.
In reply to Re: Implement Object Persistence (II)
by Joost
in thread Implement Object Persistence (II)
by tucano
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |