16%
14.09.2021
$(find /sys/devices/system/cpu -regex ".*cpu[0-9]+/topology/thread_siblings_list") | sort -n | uniq
0,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
16%
10.06.2015
(xrandr) "provides automatic discovery of modes (resolutions, refresh rates, …) [and] the ability to configure output dynamically (resize, rotate, move, …)" [3]. The xrandr configuration tool lets me
16%
07.04.2022
is also possible.
A VM with Debian 10 (Buster) or 11 (Bullseye) and 1GB of RAM is all you need for the RPort server. The costs amount to $3-$7 per month, depending on the cloud provider. For an RPort
16%
28.06.2011
.part.22
12 Generating manifest /tmp/centos.5- 3.x86.img.manifest.xml
13
14 $ euca- register images/centos.5- 3.x86.img.manifest.xml
15 IMAGE emi- c658102B
When all three parts have been uploaded
16%
09.04.2019
are incorrect on AWS Simple Storage Service (S3) or CloudTrail, which could result in your security metrics suffering a humiliating public leak. In other words, behind the scenes, AWS configures all the plumbing
16%
04.10.2018
-app . --name=$APP"
20 # create a new application from the image in the OpenShift registry
21 - "oc start-build $APP --from-dir=. --follow || sleep 3s"
22 # start a new build
23 - "oc get routes $APP
16%
07.10.2014
_open(struct inode *inode, struct file *file)
18 {
19 return single_open(file, prochello_show, NULL);
20 }
21
22 static const struct file_operations prochello_fops = {
23 .owner = THIS_MODULE,
24 .open
16%
06.10.2019
now favors the CRI-O run time [3], thanks to its optimization for the orchestrator. (See the article on OpenShift 4 in this issue for more on CRI-O.)
CRI-O runs as a lightweight run time that should
16%
13.06.2022
, memory intensive
FT – discrete 3D fast Fourier transform (FFT) emphasizing all-to-all communication
The three pseudo applications are:
BT – block tri-diagonal solver
SP – scalar penta
16%
11.04.2016
, and BackDoor Factory.
Native Stagers
Stagers manage an attack on the target system as follows [3]:
1. Establish a socket connection to the Metasploit handler (this will happen as the stage 1 victim
