Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160
KexAlgorithms diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1
wtorek, 7 lutego 2017
piątek, 3 lutego 2017
niedziela, 29 stycznia 2017
haproxy
nazwa backendu: appX-backend, roundrobin
backend appX-backend
balance roundrobin
server appX_01 192.168.2.2:8080 check
server appX_02 192.168.2.3:8080 check
jesli request zawiera appX np http://example.com/appX to przekieruj do appX-backend, domyslnie do appZ-backend
frontend http-in
bind *:80
acl url_appX path_beg -i /appX/
use_backend appX-backend if url_appX
default_backend appZ-backend
przekieruj ruch na serwer backupowy tylko wtedy kiedy pierwszy bedzie niedostepny
backend appZ-backend
server appZ_01 192.168.2.2:8080 check
server appZ_02 192.168.2.3:8080 check backup
backend appX-backend
balance roundrobin
server appX_01 192.168.2.2:8080 check
server appX_02 192.168.2.3:8080 check
jesli request zawiera appX np http://example.com/appX to przekieruj do appX-backend, domyslnie do appZ-backend
frontend http-in
bind *:80
acl url_appX path_beg -i /appX/
use_backend appX-backend if url_appX
default_backend appZ-backend
przekieruj ruch na serwer backupowy tylko wtedy kiedy pierwszy bedzie niedostepny
backend appZ-backend
server appZ_01 192.168.2.2:8080 check
server appZ_02 192.168.2.3:8080 check backup
środa, 25 stycznia 2017
ssh mail login
#!/bin/bash
mail=user@domain.tld
monitored_user=root
monitored_ip=x.x.x.x
hostname=$(hostname)
# add a welcome message:
printf >&2 "\nWelcome on $hostname $USER\n"
read -d " " ip <<< $SSH_CONNECTION
[[ $ip == $monitored_ip && $USER == $monitored_user ]] || exit 0
date=$(date "+%d.%m.%Y %Hh%M")
reverse=$(dig -x $ip +short)
mail -s "Connexion of $USER on $hostname" $mail <<EOF
IP: $ip
Reverse: $reverse
Date: $date
EOF
mail=user@domain.tld
monitored_user=root
monitored_ip=x.x.x.x
hostname=$(hostname)
# add a welcome message:
printf >&2 "\nWelcome on $hostname $USER\n"
read -d " " ip <<< $SSH_CONNECTION
[[ $ip == $monitored_ip && $USER == $monitored_user ]] || exit 0
date=$(date "+%d.%m.%Y %Hh%M")
reverse=$(dig -x $ip +short)
mail -s "Connexion of $USER on $hostname" $mail <<EOF
IP: $ip
Reverse: $reverse
Date: $date
EOF
wtorek, 24 stycznia 2017
BIND9 master + slave + sec
named.conf.options
acl dnsy { $IP;
127.0.0.1;
};
options {
directory "/var/cache/bind";
dnssec-validation auto;
auth-nxdomain no; # conform to RFC1035
allow-recursion { dnsy; };
allow-transfer { dnsy; };
recursion yes;
version "DNS";
listen-on-v6 { none; };
};
named.conf MASTER
zone "test.net" { type master; file "/etc/bind/test.net.db"; also-notify { $IP; }; allow-transfer { $IP; }; notify yes; };
named.conf SLAVE
zone "test.net" { type slave; masters { $IP; }; file "test.net.db"; };
acl dnsy { $IP;
127.0.0.1;
};
options {
directory "/var/cache/bind";
dnssec-validation auto;
auth-nxdomain no; # conform to RFC1035
allow-recursion { dnsy; };
allow-transfer { dnsy; };
recursion yes;
version "DNS";
listen-on-v6 { none; };
};
named.conf MASTER
zone "test.net" { type master; file "/etc/bind/test.net.db"; also-notify { $IP; }; allow-transfer { $IP; }; notify yes; };
named.conf SLAVE
zone "test.net" { type slave; masters { $IP; }; file "test.net.db"; };
piątek, 20 stycznia 2017
niedziela, 15 stycznia 2017
piątek, 30 grudnia 2016
Cloudlinux: custom PHP settings for user
You can create additional custom.ini file inside user "cage" and add to it necessary values.
For example:
# su -s /bin/bash USERNAME
# cd /etc/cl.php.d/alt-phpXX/ (where XX depend from version)
# nano custom.ini >>
disable_functions="mail"
Also, PHP Selector allows customers to edit php.ini settings:
http://docs.cloudlinux.com/index.html?custom_php_ini_options.html
Subskrybuj:
Posty (Atom)