21%
04.10.2018
-RTT poses a threat to any application that runs in multiple zones but declines tickets issued in one zone (A) in any other of its zones (B, C, D, …).
By sending a ClientHello and early data intended ... After a decade in service, TLS 1.2 is showing many signs of aging. Its immediate successor, TLS 1.3, has earned the approval of the IETF. Some major changes are on the way. ... TLS 1.3 ... TLS 1.3 and the return of common sense
21%
07.02.2019
exiting the data region, the data from the accelerator is copied back to the host. Table 3 shows a simple example of using the copy
clause.
Table 3: The copy
Clause
Fortran
C
!$acc data copy(a
21%
20.03.2014
access is aligned to internal sector size, so that should be your first consideration. Without further data, the rule of thumb adopted by Microsoft in Windows 7 of aligning to 1MB (2048x512 and 256x4096
21%
09.12.2021
in Listing 6.
Listing 6: gzip
and gpg
$ gzip -9 -c package-list.txt | gpg --symmetric --cipher-algo aes256 -o secure.gz.gpg
gpg: keybox '/home/laytonjb/.gnupg/pubring.kbx' created
The command line pipes
21%
30.01.2020
-06f4dce9c3ae2c504" # for eu-west-3 paris
07 InstanceType: t2.small
08 AvailabilityZone: !GetAtt FortiVPCFrontNet.AvailabilityZone
09 KeyName:
10 Ref: KeyName
11 Network
21%
14.03.2013
command:
# sockstat | grep "\*:[0-9]"
The description for rc.conf(5) lists the services that need to be bound to a fixed IP address via parameters. One example is the inetd service:
inetd_flags="-wW -a
21%
05.12.2014
of this attack, including a description, walk-through, and exploit is available at Exploit-DB [11].
Over the years, I've made use of a Perl script that reduces very long W3C Apache log entries down to just
21%
19.06.2023
128-bit complex floating-point
complex256
c32
256-bit complex floating-point
bool
?
Boolean (True or False)
unicode
U
Unicode string
21%
25.09.2023
Quad-core Xuantie C910
64KB+64KB data/instruction caches per core
1MB shared L2 cache
GPU
50GFLOPS BXM-4-64
NPU
4TOPS INT8 at 1GHz
21%
27.08.2014
was the sequential write test using 1MB record sizes:
./iozone -i 0 -c -e -w -r 1024k -s 32g -t 2 -+n > iozone_write_1.out
To gather the block statistics, I ran ioprof in a different terminal window before I ran
