My apologies, it's something on the system, not in the code. That'll teach
me to post before checking source. I'll post the fix once I find it for
anyone else that might come across it.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/World-writable-KahaDB-files-tp4603663p
I had already found and used the ACTIVEMQ_USER variable in the init script,
and it's working properly.
Thanks for confirming things will work fine by tightening down those
permissions.
I can't help but think this is at least a bug, if not a security issue. In
the interest of least privileges, sh
It really makes me nervous knowing that anyone with any filesystem access to
my ActiveMQ machine can delete, overwrite, or corrupt my KahaDB files.
While we as users should do our best to secure our servers, I don't see why
666 perms are needed on the db files and 777 perms are needed on the paren
