samhain 2.5.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News samhain 2.5.0 (Default branch)
# 1  
Old 11-03-2008
samhain 2.5.0 (Default branch)

samhain is a daemon that can check file integrity, search the file tree for SUID files, and detect kernel module rootkits (Linux only). It can be used either standalone or as a client/server system for centralized monitoring, with strong (192-bit AES) encryption for client/server connections and the option to store databases and configuration files on the server. For tamper resistance, it supports signed database/configuration files and signed reports/audit logs. It has been tested on Linux, FreeBSD, Solaris, AIX, HP-UX, and Unixware. License: GNU General Public License (GPL) Changes:
This version provides a new module to perform log file monitoring (currently supported: syslog, apache, samba, and pacct). On Linux, port monitoring now reports the process and the user for open ports. Some minor bugs have been fixed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
nstrtel(5)							File Formats Manual							nstrtel(5)

NAME
nstrtel - specifies the number of telnet device files the kernel can support for incoming telnet sessions VALUES
Failsafe Default Allowed values (Subject to available physical memory.) It is best to use the default value, and there should not be any need to lower it. However, if the simultaneous telnet connection load is very high, then the value of could be increased. Recommended values (Default value.) DESCRIPTION
The telnet daemon uses two STREAMS-based pseudo-terminal drivers and The kernel parameter, can be used to tune the number of pseudo-termi- nals. specifies the number of kernel data structures that are created at system boot time that are required to support the device files used by incoming telnet sessions on a server. If the command or SAM is used to create more telnet device files, the value of must be increased accordingly or the device files cannot be used because there are no kernel data structures available for communicating with the system. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect at the next reboot. When Should the Value of This Tunable Be Raised? When there is an increase in the load of telnet connections and there are no device files available to open telnet connections, then this kernel parameter should be increased. When the error is encountered, then the device files have been exhausted and should be raised. Once the value of is raised, should be run to create new device files. (If SAM is used to raise the value of is run automatically.) What Are the Side Effects of Raising the Value of This Tunable? More resources would be consumed. Extra kernel data structures, and extra device files may clog the system. When Should the Value of This Tunable Be Lowered? It is not advisable to lower the tunable value from the default value. Consult HP Support before lowering this tunable from the default value. What Are the Side Effects of Lowering the Value of This Tunable? Though not recommended, there would not be any side effects. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
insf(1M), telnetd(1M), telm(7), tels(7). Tunable Kernel Parameters nstrtel(5)