"Someone just hacked my website... they have all the usernames and passwords for the entire website... I'm so screwed!"

OK, now that I have your attention... why oh why does the export function of this module drop a plain text file into the portal root with potentially exposed usersnames/passwords in plain text?

I just hit a clients site to find that all the files they ever exported are in the portal root... of course they never deleted the file after they "clicked here" to download it. 

Of course... no one could guess the file name right - they would never find it to download it? Well,,, there is this editor see... and they have to be able to upload files and such... they can see it...and download it... and get the admin user/password (as well as thier evil co-workers user/pass).

Can we *pretty please* get a module setting that at least lets us direct WHERE the export file goes.. maybe we can at least exert some security on that folder. It would be even better if we could just email the file (zipped of course sent in S/MIME) and it never leaves a trace on the server itself. 

Holding my breath on this one trying to prevent a disaster

Normally I'de agree with you.  But this isn't a real case where the product is insecure...It's not the product that is insecure, it's the usage that insecure.  It also needs to be public knowledge as a warning to all those folks that have and use the product to clean up the files that it deposits...and think before exporting the passwords.

I'm just as shocked as the fortune 500 company that I found this on, that the developer that put this module in, didn't train the user using it to be a little more careful.


As DataSprings, you just need to give the users of this module a more foolproof way to protect themselves.  You give us the hammer to pound the nail, but we need a little guard over our thumbs so we don't hit ourselves and do permanent damage.