File Datastore doesn't unserialize.

@Paul M
I didn't say that using a certain plugin is always a security risk, I said that using custom modifications (eg. that includes all modifications) is always a security risk.

If there were only two plugins, ohne that echos "Hello World" and another one that make that makes the calling user admin.
Now, if there is the question "Are plugins save?", what would you answer without going into detail for specific hacks, etc.?

The filebased datastore many not serialize but my original point still stand :)

Regardless, its still loading uncompiled data in that pluginlist array which is stored in memory during the request.

ps. forgot about it using var_export, ive always used eaccelerator personally.

Trigun have you benchmarked a board using your accelerator against the file datastore? I would be interested in the results.
I'm genuinely interested in this by the way it's not a redundant question.

Maybe there should be more tick box things (in the forthcoming, elusive, hack db) like:
inserts to db
changes permission stuff
could mess up
etc.
A little self regulation could help people make the right choice :)

Running any kind of code is a security risk. You just trust Jelsoft to write better code than most.

People with multiple web servers can't really use file datastore and have to use either eA or memcache which has their own issues.

Even if you use no hacks it still can be a security risk lol

Leaving your home is a security risk.
Using the telephone is a security risk.
Having friends is a security risk.
Drinking tap water is a security risk.
Etc,etc, etc......