31%
03.12.2015
. Clients don't actually know whether they really see all the messages that arrive at the broker; the broker ACLS decide this.
Messages transport payloads; payload data can also be binary and be up to 256MB
31%
20.05.2014
Viewing Server Topology
01 # numactl --hardware
available: 8 nodes (0-7)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9
node 0 size: 16373 MB
node 0 free: 15837 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19
node 1
31%
18.02.2018
public_key = "${file("${var.ssh_pub_key}")}"
07 }
08 resource "digitalocean_droplet" "mywebapp" {
09 image = "docker-16-04"
10 name: guest
11 region = "fra1"
12 size = "512mb"
13 ssh
31%
25.10.2011
-256-cbc;
07 }
08 policy pfs2-aes256-sha1 {
09 perfect-forward-secrecy {
10 keys group2;
11 }
12 proposals aes256-sha1;
13 }
14 vpn racoonvpn {
15 bind
31%
25.03.2020
_DATA=$1
06
07 # This is the Event Data
08 echo $EVENT_DATA
09
10 # Example of command usage
11 EVENT_JSON=$(echo $EVENT_DATA | jq .)
12
13 # Example of AWS command that's output will show up
31%
18.07.2013
. The problematic compression is disabled.
Listing 1
Configuration Example
SSLProtocol -SSLv2 -SSLv3 -TLSv1 -TLSv1.1 +TLSv1.2
SSLHonorCipherOrder on
SSLCipherSuite ECDHE-RSA-AES256-GCM-SHA384:DHE
30%
25.09.2013
)
8 (4)
7.2
0.9
Nehalem-EP (2009)
8 (4)
32
4
Westmere-EP (2010)
12 (6)
42
3.5
Westmere-EP (2010)
8 (4)
42
30%
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
30%
25.03.2020
/share/doc/stunnel*/. The example in Listing 1 shows a very simple configuration that uses stunnel as a plain vanilla TLS client.
Listing 1
Stunnel as a TLS Client
; global settings
sslVersion = TLSv1.2
chroot = /var
30%
14.03.2013
family, by the names of SHA-224, SHA-256, SHA-284, and SHA-512. But, again, some cryptographers saw issues looming; the methods that SHA-2 uses differ only slightly from those used by MD5 and SHA-1.
So
