Created attachment 177138 [details] samhain 4.2.0 Samhain is an open source file integrity and host-based intrusion detection system for Linux and Unix. It can run as a daemon process, and and thus can remember file changes - contrary to a tool that runs from cron, if a file is modified you will get only one report, while subsequent checks of that file will ignore the modification as it is already reported (unless the file is modified again). Samhain can optionally be used as client/server system to provide centralized monitoring for multiple host. Logging to a (MySQL or PostgreSQL) database is supported. WWW: http://la-samhna.de/samhain/ This port has been removed from the ports tree in 2014 because of missing staging. The shar file contains three ports: security/samhain (standalone), security/samhain-client and security/samhain-server. The main port is samhain, samhain-client and samhain-server use the main port with different build options. Poudriere and portlint look OK. About samhain-server poudriere complains with: ====>> Checking for staging violations... done ====>> Error: Filesystem touched during stage (files must install to ${STAGEDIR}): extra: var/log/userlog extra: var/mail/yule etc/passwd: size (1531, 1579) etc/master.passwd: size (1650, 1703) etc/group: size (445, 458) ====>> Cleaning up wrkdir I assume this is because yule user is created during the installation. I suppose yule user should be added in UIDs and GIDs. Regards, Nikola
Can you submit a patch to add yule user as part of this submission please?
Created attachment 180630 [details] samhain 4.2.0 uid gid
Created attachment 180631 [details] GIDs yule user
Created attachment 180632 [details] UIDs yule user
A commit references this bug: Author: lifanov Date: Sun Mar 12 17:07:24 UTC 2017 New revision: 435996 URL: https://svnweb.freebsd.org/changeset/ports/435996 Log: add ports for Samhain Intrusion Detection System Samhain is an open source file integrity and host-based intrusion detection system for Linux and Unix. It can run as a daemon process, and and thus can remember file changes - contrary to a tool that runs from cron, if a file is modified you will get only one report, while subsequent checks of that file will ignore the modification as it is already reported (unless the file is modified again). Samhain can optionally be used as client/server system to provide centralized monitoring for multiple host. Logging to a (MySQL or PostgreSQL) database is supported. PR: 214623 Submitted by: Nikola Kolev <koue@chaosophia.net> Changes: head/GIDs head/UIDs head/security/Makefile head/security/samhain/ head/security/samhain/Makefile head/security/samhain/distinfo head/security/samhain/files/ head/security/samhain/files/fixsamhainrc.patch head/security/samhain/files/fixyulerc.patch head/security/samhain/files/patch-config.h.in head/security/samhain/pkg-descr head/security/samhain/pkg-message head/security/samhain/pkg-plist head/security/samhain-client/ head/security/samhain-client/Makefile head/security/samhain-server/ head/security/samhain-server/Makefile
Committed with some changes, thanks! o unwrap PORTDOCS If this stage is not expensive, it's better to unconditionally instal docs and let the package stage implement the option (if they are marked as %%PORTDOCS%%) o remove stray blank lines from pkg-message o add Creted by section to Makefiles o cleaned up OPTIONS to match common descriptions It's better not to add a description for common options listed in bsd.options.desc.mk. I also switched from GPG to GNUPG option, as this one is more common o remove explicit cat for pkg-message It's discouraged to explicitly cat this: pkg tool does this for you Sorry this took so long!