65%
06.10.2019
time relative to Docker.
Docker Dominance
The first version of Docker [1] was released March 20, 2013. Although containers had already been available on Unix-like systems for a few years, Docker
65%
21.01.2014
a search function. The following function launches the smallest Amazon instance on offer using the ami-df9b8bab
image:
conn.run_instances('ami-df9b8bab', instance_type='m1.small')
If you take a look
65%
25.09.2023
Installation
- name: Install AWX
kubernetes.core.k8s:
state: present
definition:
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: "{{ awx
65%
27.09.2021
the Exchange PowerShell approach with
Connect-ExchangeOnline -userPrincipalName com>
New-UnifiedGroup -DisplayName "" -Alias "" -Owner com>
or use the Azure
65%
13.12.2018
is then given a new shell from jamesvb1
, which DNS identifies as s1.stangernet.com
.
Figure 8: The attacking system.
Figures 9 and 10 show another sequence
65%
22.05.2023
.HistogramOpts{
Name: "prometheus_http_request_duration_seconds",
Help: "Histogram of latencies for HTTP requests.",
- Buckets: []float64{.1, .2, .4, 1, 3, 8, 20, 60, 120},
+ NativeHistogramBucketFactor: 1
65%
15.09.2020
version 2.8
FUSE library version: 2.9.7
fusermount version: 2.9.7
using FUSE kernel interface version 7.19
(e.g., on Ubuntu 18.04).
Initial SSHFS Test
For these initial tests, I’m exchanging data between
65%
30.11.2020
.04):
$ sshfs -V
sshfs version 2.8
FUSE library version: 2.9.7
fusermount version: 2.9.7
using FUSE kernel interface version 7.19
Initial SSHFS Test
For these initial tests, I'm exchanging data between two
65%
02.10.2017
is just “echoing” a string. Note that I'm intentionally using the relative path and not the usual absolute path, /usr/bin/host
.
Listing 1: A Sample snapcraft.yaml
File
---
name: Echo a name
version: "1
65%
17.04.2017
> at the command line as follows:
nslookup dc02.microsoft.com dc01.contoso.com
Here, nslookup attempts to resolve host dc02.microsoft.com
using server dc01.contoso.com
. Instead of the second entry, you could
