14%
26.11.2013
RawKey = "4ea1...b2bf";
02 var encAlg = {
03 name : "AES-GCM",
04 params : {
05 iv : hex2bin("534aea17"),
06 additionalData: hex2bin("534aea17"),
07 tagLength: 128
08 }
09 };
10 function encrypt
14%
05.12.2014
(plyr)
06 library(ggplot2)
07
08 setwd("~/R/RFI")
09 rfi <- read.csv("rfi-extract-July2011.log",header=TRUE, sep=",")
10
11 ## read in data to frame
12 data <- data.table(rfi)
13 ct <- count
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%
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%
30.11.2025
(in days)
05 export CA_EXPIRE=3650
06
07 # Certificate validity (in days)
08 export KEY_EXPIRE=3650
09
10 # Predefined certificate values
11 export KEY_COUNTRY="DE"
12 export KEY_PROVINCE="BY"
13 export
14%
30.11.2020
"conditions": [
05 {
06 "type": "RuntimeReady",
07 "status": true,
08 "reason": "",
09 "message": ""
10 },
11 {
12 "type": "NetworkReady",
13
14%
07.10.2014
as reliably as the rest of the PKI world.
4. Protocols
A public website must support the TLS 1.0, TLS 1.1, and TLS 1.2 protocols. SSL 2 is obsolete and insecure. SSL 3 is also deprecated and, although
14%
30.11.2025
=""
04 PING="ping -c1 -w 3"
05 PING2=""
06
07 case $OS in
08 HP-UX*)
09 PING=ping
10 PING2="-n 1"
11 RSH="remsh"
12 RSH2="-l user"
13 ;;
14 Sun
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%
30.11.2025
06 I_T nexus information:
07 LUN information:
08 LUN: 0
09 Type: controller
10 SCSI ID: deadbeaf1:0
11 SCSI SN: beaf10
12 Size: 0
13
