Package Details: ossec-hids 3.5.0-1

Git Clone URL: (read-only, click to copy)
Package Base: ossec-hids
Description: Open Source Host-based Intrusion Detection System
Upstream URL:
Keywords: hids ossec ossec-agent ossec-hybrid ossec-local ossec-server security
Licenses: GPL2
Submitter: crt
Maintainer: crt
Last Packager: crt
Votes: 1
Popularity: 0.000000
First Submitted: 2017-09-12 07:04
Last Updated: 2019-11-28 22:30

Latest Comments

colluphid commented on 2019-05-26 00:18

Not sure how this worked in the past, but I ran the script manually with root permissions and was able to create the user and group necessary.

sudo ./init/ ossec ossecm ossecr ossec $HOME/.cache/yay/ossec-hids/pkg/ossec-hids/var/ossec

danisantos commented on 2019-02-01 13:40

I also got @vas error. Does anyone found a solution for this? It would be great for the package maintainer tell us how he did install the package

vas commented on 2018-12-11 11:53

Full error message:


Done building server

./init/ ossec ossecm ossecr ossec /home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec
Wait for success...
groupadd: PAM: Authentication service cannot retrieve authentication info
make: *** [Makefile:381: install-common] Error 1
cp: cannot create regular file '/home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec/home/vas/tmp/ossec-hids/pkg/ossec-hids/etc/ossec-init.conf': No such file or directory
chmod: cannot access '/home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec/home/vas/tmp/ossec-hids/pkg/ossec-hids/etc/ossec-init.conf': No such file or directory

 - Unknown system. No init script added.

 - Configuration finished properly.

 - To start OSSEC HIDS:
      /home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec/bin/ossec-control start

 - To stop OSSEC HIDS:
      /home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec/bin/ossec-control stop

 - The configuration can be viewed or modified at /home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec/etc/ossec.conf

    Thanks for using the OSSEC HIDS.
    If you have any question, suggestion or if you find any bug,
    contact us at or using our public maillist at
    ( ).

    More information can be found at

    ---  Press ENTER to finish (maybe more information below). ---

 - In order to connect agent and server, you need to add each agent to the server.
   Run the 'manage_agents' to add or remove them:


   More information at:

 - No action was made to configure the OSSEC HIDS to start
   during the boot. Add the following line to your init script: 

      /home/vas/tmp/ossec-hids/pkg/ossec-hids//var/ossec/bin/ossec-control start

sed: no input files

crt commented on 2018-10-22 01:21

Hm, I can't seem to reproduce that. Does it still happen?

slowmo commented on 2018-02-21 00:47

I get an error when I run makepkg -s

  • No action was made to configure the OSSEC HIDS to start during the boot. Add the following line to your init script:

    /tmp/makepkg/ossec-hids/pkg/ossec-hids//var/ossec/bin/ossec-control start

sed: no input files ==> ERROR: A failure occurred in package(). Aborting...


crt commented on 2017-09-13 07:55

You can try again. It should be fine.

zetorian commented on 2017-09-13 06:07

I understand late night forrays into PKGBUILD's, damn near crashed my system doing one a few weeks back.

Forgive me if I'm wrong because I don't have the packagebuild myself to run and test, but that seems to be an issue with privalages, a quick addition of 'sudo' to the install lines should resolve the problem. But again, I dont know at what point this error is being thrown so I cant be sure.

Also, thank you for taking point on the upkeep of this package, its nice to see someone taking it up again.

crt commented on 2017-09-13 05:15

Yeah, I did this late at night. I redid the PKGBUILD but now need to sort the /var/ossec directory problem.

zetorian commented on 2017-09-12 21:05

just so you know, this currently lists an install size of zero and fails to start at all. systemctl deamon reports /var/ossec not found. i believe this is due to the files not being installed properly after moving from the fakeroot environment, but i will look into it further.

edit: it actually never runs the make command for the package before installing.
the installation of the systemd service is also skipped. leading to the
total install size of zero and no files ever leaving the sourcedir