18%
09.01.2013
0
22 243056
23
12
24
1
25
26
27 16
28
29
18%
04.10.2018
"data_dir": "/var/consul",
08 "datacenter": "Datacenter-A",
09 "disable_update_check": true,
10 "enable_script_checks": true,
11 "enable_syslog": true,
12 "encrypt": "xxxxxxxxxxxxxx
18%
03.08.2023
: "routers",
"value": "192.168.2.254"
}],
"reservations": [{
"hw-address": "00:11:22:33:44:55",
"ip-address": "192.168.2.60",
hostname: "host-2-60"
}, {
"hw-address": "00:00:00:00:00
18%
02.02.2021
.
As surely as night follows day, automated attacks will target the default Secure Shell port (TCP port 22), so I will use SSH as the guinea pig test case with the knowledge that I can move the real SSH service
18%
14.11.2013
(Session);
11 %EXPORT_TAGS = ( DEFAULT => [qw(&Session)] );
12
13 sub Session {
14 open(IN, "/etc/sysconfig/spacewalk_api.conf") or die "Spacewalk API config not found: $!";
15 $_ = ;
16 my ($server
18%
14.03.2013
=/opt/pjsua.conf
06 SOUNDFILE=/tmp/alert.wav
07 TEXT2WAVE=/usr/bin/text2wave
08 DURATION=20
09 NUMBER=01234567890
10 MESSAGE="Monitoring Alert"
11
12 # Setting a lock file
13 # We can't make more than one call
14
