11%
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
11%
31.07.2013
Code Example
1 #include
2
3 /* Our structure */
4 struct rec
5 {
6 int x,y,z;
7 float value;
8 };
9
10 int main()
11 {
12 int counter;
13 struct rec my
11%
30.11.2020
: Pull complete
3db6272dcbfa: Pull complete
Digest: sha256:8be26f81ffea54106bae012c6f349df70f4d5e7e2ec01b143c46e2c03b9e551d
Status: Downloaded newer image for registry:2
docker.io/library/registry:2
11%
05.02.2023
wgossrvc
Listing 4
setup_goss.sh Diff Additions
5a6
> GOSSVFLE='/lib/systemd/system/goss.service'
9,10c10,12
< sha256sum
< tee
---
> sha256sum
> systemctl
> tee
81a84
11%
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
11%
21.08.2012
--> Processing Dependency: libpng12.so.0(PNG12_0) for package: rrdtool-1.3.8-6.el6.i686
--> Processing Dependency: libxml2.so.2 for package: rrdtool-1.3.8-6.el6.i686
--> Processing Dependency: libpango-1.0.so.0
11%
30.11.2025
: Transtech Lynx Calleo Application Server 2260 [1]: CPU/RAM: Intel Xeon E5-2643 (quad-core CPU, eight threads, 3.3GHz)/32GB RAM (DDR-3, 1600MHz, ECC)
Controller: LSI Logic Mega RAID SAS 9261-8i PCIe x8, 512MB
11%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
11%
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
11%
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
