100%
31.10.2025
password 8 ZDF339a.20a3E
05 log file /var/log/quagga/zebra.log
06 service password-encryption
07 !
08 interface eth0
09 multicast
10 ipv6 nd suppress-ra
11 !
12 interface eth1
13 ip address 10 ... 12
99%
31.10.2025
PRIVATE (id)
06
07 id = omp_get_thread_num()
08 write(*,*) 'Thread ',id,' Checking in'
09
10 IF (id == 0) THEN
11 WRITE(*,*) ' Number of threads in use is ',omp_get_num_threads()
12 ENDIF
13
14 ... 12
99%
31.10.2025
Service (Amazon S3)
19 - ami plugin for Amazon Simple Storage Service (Amazon S3)
20 - sftp plugin for SSH File Transfer Protocol
21 - ebs plugin for Elastic Block Storage
22 - local plugin ... 12
98%
31.10.2025
set send_slow {1 .1}
06 proc send {ignore arg} {
07 sleep .1
08 exp_send -s -- $arg
09 }
10 }
11 set timeout -1
12 spawn $env(SHELL)
13 match_max 100000 ... 12
81%
04.12.2024
Rubén Llorente ... " {
11 endpoint = "https://192.168.3.15:8006/"
12 username = "root@pam"
13 password = "proxmox"
14 insecure = true
15 tmp_dir = "/var/tmp"
16
17 ssh {
18 agent = true
19 }
20
80%
01.06.2024
Rubén Llorente ... is not verified. The purpose of this routine is to prevent man-in-the-middle (MITM) attacks.
Sake uses the x/crypto/ssh Go package, which is a bit quirky [3]. An issue I stumbled on when testing Sake
61%
30.01.2024
Rubén Llorente ...
8, 9
Debian
11, 12
Ubuntu
20.04, 22.04
FreeBSD
13.x
OpenBSD
7.3
I recommend the downloadable installer, but I will skip
19%
10.06.2015
" ; shift
20 local display_list="$1"
21 while read display width_mm height_mm width height ; do
22 if [[ "$display" == "$find_display" ]] ; then
23 echo ${width}x${height}
24
18%
29.10.2013
-e-hxaxpp3bsa-stack-AWSEBSecurityGroup-ZNUGTMANJ7WO
2013-05-08 20:21:40 INFO Created Auto Scaling launch configuration named: awseb-e-hxaxpp3bsa-stack-AWSEBAutoScalingLaunchConfiguration-12RI7463WQWE3
2013-05-08
17%
30.11.2025
_config
03 bash#> vi sshd_config
04 AllowTcpForwarding no
05 ClientAliveCountMax 3
06 ClientAliveInterval 0
07 Compression delayed
08 LoginGraceTime 60s
09 LogLevel DEBUG3
10 MaxAuthTries 2 ... 3
