HEX

Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit - prohibited by configuration in /home/u547966/brikov.ru/www/wp-content/plugins/admin-menu-editor/menu-editor.php on line 745
Server: Apache
System: Linux 4.19.0-0.bpo.9-amd64 x86_64 at red40
User: u547966 (5490)
PHP: 5.3.29-mh2
Disabled: syslog, dl, popen, proc_open, proc_nice, proc_get_status, proc_close, proc_terminate, posix_mkfifo, chown, chgrp, accelerator_reset, opcache_reset, accelerator_get_status, opcache_get_status, pcntl_alarm, pcntl_fork, pcntl_waitpid, pcntl_wait, pcntl_wifexited, pcntl_wifstopped, pcntl_wifsignaled, pcntl_wifcontinued, pcntl_wexitstatus, pcntl_wtermsig, pcntl_wstopsig, pcntl_signal, pcntl_signal_dispatch, pcntl_get_last_error, pcntl_strerror, pcntl_sigprocmask, pcntl_sigwaitinfo, pcntl_sigtimedwait, pcntl_exec, pcntl_getpriority, pcntl_setpriority
Upload Files
File: //usr/share/doc/libpam-shield/README.Debian
pam-shield for Debian
---------------------

Configuring pam_shield
----------------------

1) Edit the config file /etc/security/shield.conf 
and create an 'allow' line for trusted hosts.
Change trigger_cmd if desired.

2) Check the configuration in /etc/pam.d/common-auth.
The default configuration will lock out repeated attempts
by IP, but will not block login on the basis of missing
DNS or missing reverse DNS.

3) Simulate attack on Your host and check out

	ip route show
or
	iptables -L

depending on Your trigger script defined in shield.conf

 -- Mateusz Kaduk <mateusz@kaduk.net>  Mon, 03 Dec 2007 21:31:45 +0100
 -- Jonathan Niehof <jtniehof@gmail.com> Sat, 02 Jun 2012 12:48:05 -0600