26%
10.04.2015
submitted his master's thesis on the subject of TCP Stealth in 2014 [12].
If you have been following the port knocking scenario for a few years, you might remember SilentKnock [13]. The project uses the same
26%
13.06.2022
in performance (assuming a normal distribution). One-eighth of a standard deviation is 4.78% of normally distributed data or 95.22% of the mean, allowing for benchmarks 4.78% below the mean. If you select
26%
02.08.2022
] in performance (assuming a normal distribution). One-eighth of a standard deviation is 4.78% of normally distributed data or 95.22% of the mean, allowing for benchmarks 4.78% below the mean. If you select
26%
30.01.2020
: 1 (f=1): [w(1)][100.0%][r=0KiB/s,w=1401KiB/s][r=0,w=350 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3104: Sat Oct 12 14:39:08 2019
write: IOPS=352, BW=1410KiB/s (1444kB/s)(82.8Mi
26%
20.06.2012
was there. To test whether this worked, ssh
to the node n0001
as root.
[root@test1 ~]# ssh n0001
Last login: Sat May 26 12:00:06 2012 from 10.1.0.250
The /etc/hosts
on the master node works fine
26%
02.06.2020
= sol.copy()
10
11 for j in range(0,ny-1):
12 sol[0,j] = 10.0
13 sol[nx-1,j] = 1.0
14 # end for
15
16 for i in range(0,nx-1):
17 sol[i,0] = 0.0
18 sol[i,ny-1] = 0.0
19 # end for
20
21 # Iterate
22
26%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
26%
10.09.2012
to logfiles, and it’s pretty simple to use:
[laytonjb@test1 ~]$ logger "This is a test"
...
[root@test1 ~]# tail -n 2 /var/log/messages
Aug 22 15:54:47 test1 avahi-daemon[1398]: Invalid query packet.
Aug 22 17:00
26%
19.11.2019
, ioengine=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=475MiB/s][w=122k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1634: Mon Oct 14 22:18:59 2019
write: IOPS=118k, BW=463Mi
26%
04.11.2011
-server 192.168.1.2;
filename "/pxelinux.0";
host node01 {
hardware ethernet 00:11:22:33:44:a0;
fixed-address 192.168.1.101;
}
host node01-bmc {
hardware ethernet 00:11:22:33:44:8d;
fixed-address 192
