15%
18.07.2013
rq2 ra92
08 set rq3 cdrom
09
10 attach rq0 d0.dsk
11 attach rq1 d1.dsk
12 attach rq2 d2.dsk
13
14 attach -r rq3 cdrom.iso
15
16 set rl disable
17 set ts disable
18
19 set xq mac=08-00-2B-AA-BB-CC
20
15%
21.08.2014
Detection))
09 iso9660 (ISO9660 CD)
10 hfs (HFS+)
11 ufs (UFS (Auto Detection))
12 raw (Raw Data)
13 swap (Swap Space)
14 fat12 (FAT12)
15 fat16 (FAT16 ... 22
15%
16.10.2012
($ssh, '/sbin/ifconfig');
07 stream_set_blocking($stream, true);
08
09 $response = '';
10 while($buffer = fread($stream, 4096)) {
11 $response .= $buffer;
12 }
13
14 fclose($stream);
15 echo $response;
16
17
15%
09.10.2017
_consumer_secret>"
06 config.access_token = ""
07 config.access_token_secret = ""
08 end
09
10 user = client.user("23Cent")
11 puts user.name
12
13 def collect
15%
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
15%
30.01.2020
: (groupid=0, jobs=1): err= 0: pid=7055: Sat Oct 12 19:09:53 2019
write: IOPS=34.8k, BW=136MiB/s (143MB/s)(9.97GiB/75084msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=136MiB/s (143MB
15%
03.02.2022
,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
14%
17.02.2015
}
07 define service{
08 use generic-service
09 host_name w2k12srv
10 service_description Uptime
11 check_command check_nt!UPTIME
12 }
13 define service
14%
30.11.2020
"conditions": [
05 {
06 "type": "RuntimeReady",
07 "status": true,
08 "reason": "",
09 "message": ""
10 },
11 {
12 "type": "NetworkReady",
13
14%
05.12.2014
_domain": "yourdomain.com",
06 "dataset_uuid": "d34c301e-10c3-11e4-9b79-5f67ca448df0",
07 "resolvers": [
08 "192.128.0.9",
09 "192.128.0.10"
10 ],
11 "max_physical_memory": 4096,
12 "nics": [
13
