14%
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
14%
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
14%
14.03.2013
enable TLS 1.2 – given OpenSSL 1.0.1 and a recent 2.2 or 2.4 version of the Apache web server – using the SSLProtocol configuration option. Listing 1 provides a potential server configuration.
Listing
14%
28.11.2021
import (
04 "crypto/md5"
05 "crypto/sha1"
06 "crypto/sha256"
07 "crypto/sha512"
08 "encoding/hex"
09 "hash"
10 "io"
11 "log"
12 "os"
13 )
14
15 func genChecksum(file, hashfunc string
14%
09.01.2013
metadata tables...
08 Dumping metadata...
09 ..objects..
10 ..blocks..
11 ..inodes..
12 ..inode_blocks..
13 ..symlink_targets..
14 ..names..
15 ..contents..
16 ..ext_attributes..
17 Compressing and uploading
14%
18.07.2013
buffered disk reads: 616 MB in
3.00 seconds = 205.03 MB/sec
$ hdparm -T /dev/sda
/dev/sda:
Timing cached reads: 6292 MB in
2.00 seconds = 3153.09 MB/sec
If this were a spinning disk, you would also
14%
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%
23.03.2022
laytonjb laytonjb 19946519 Nov 20 2020 Lmod-8.4.15.tar.gz
31988342 drwxrwxr-x 2 laytonjb laytonjb 4096 Oct 27 14:22 mpibzip2-0.6
31988329 -rw-rw-r-- 1 laytonjb laytonjb 92160 Oct 27 14:18 mpibzip
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
