17%
04.04.2023
_type = "simple-zonal"
03 }
04 provider "google" {
05 ...
06 }
07 data "google_client_config" "default" {}
08 provider "kubernetes" {
09 ...
10 }
11 /*******************************************
12
17%
10.06.2015
exploits like the OpenSSH bug CVE-2002-0083 [2] show that sometimes changing just one bit is sufficient to install a backdoor [3]. For sophisticated attacks, attackers could dump a kernel rootkit
17%
14.03.2013
: 6
08 microcode : 0x60c
09 cpu MHz : 800.000
10 cache size : 6144 KB
11 physical id : 0
12 siblings : 2
13 core id : 0
14 cpu cores : 2
15 apicid
17%
07.04.2022
security misconfigurations. I'll showcase how it would be possible for an attacker to use those IAM misconfigurations and create serious hassles.
Big Deal?
AWS IAM [3] lets you manage access to AWS
17%
20.05.2014
)]: Done 1 out of 181 | elapsed: 0.0s remaining: 4.5s
[Parallel(n_jobs=2)]: Done 198 out of 1000 | elapsed: 1.2s remaining: 4.8s
[Parallel(n_jobs=2)]: Done 399 out of 1000 | elapsed: 2.3
17%
25.03.2021
_idle_timeout 3m;
10 http2_max_requests 1000;
11
12 access_log /usr/local/var/log/nginx/http2.log http2;
13
14 ssl_certificate /test.crt;
15 ssl_certificate_key /test.key;
16
17 root
17%
03.04.2024
credentials. the initializer can take up to 3 minutes to run
08 # use docker-compose logs -f initializer to track progress
09 docker-compose logs initializer ? grep "Admin password:"
First, run
17%
08.10.2015
and Using Classes
01 class NetConfig
02 {
03 #Properties
04 [STRING]$ComputerName = "srv01";
05 [STRING]$IpAddress = "192.168.178.2";
06 [STRING]$DNS = "192.168.178.1";
07 #Methods
08
09 [Void]
10
17%
11.04.2016
_options=synced
08 servers=backend1, [...]
09 user=maxscale
10 passwd=secret
11
12 [Galera Listener]
13 type=listener
14 service=Galera Router
15 protocol=MySQLClient
16 address=10.42.0.1
17 port=3306
18
19 [Galera
17%
20.05.2014
"dependencies": {
09 "express": "*",
10 "swig": "*",
11 "consolidate": "*"
12 },
13 "devDependencies": {
14 "grunt": "~0.4.1",
15 "grunt-contrib-copy": "*",
16 "grunt
