On Wed, Apr 29, 2015 at 8:45 AM, Pedro Pereira <
perei...@gmail.com> wrote:
> Yup, it did mess up the user accounts... i commented the htpasswd section of
> the script but it still created 3 new accounts, dunno why. The workaround
> the logon loop is to restore the /tmp permissions ownership, you where
> right. Somehow, the ossec-wui script changes the permissions in the /tmp/
> folder of ubuntu, not the /var/ossec/tmp permission or even the
> /var/www/ossec-wui/tmp. I thinks there's a bug in the script, permission
> changing wise. I followed this
> :
http://ubuntuforums.org/showthread.php?t=2050685
Where did you run setup.sh from? The script doesn't seem too
complicated, or robust. So if you ran it from the wrong location, it
could probably cause some issues. Running it as root also seems silly,
but I'm sure it's documented that way. (I also see some non-portable
options being used, but that wouldn't affect ubuntu)
> For now, it seems to work. But i still cannot comprehend why did it create
> the accounts ossec, ossecr and ossecm...Can you guys check out the script
> and give me a hand?
Those are ossec accounts, and have very little to do with the wui.