Skip to main content

Shell script to login to server with autofill of sshadmin and root passwords.



First install expect in your local machine.
For ubuntu : apt-get install expect.
For Centos : yum install expect.

Create a file sshlogin
chmod +x sshlogin


#!/usr/bin/expect
set timeout 10
log_user 0
spawn ssh -p 1707 sshadmin@ipaddress
expect "*?assword:*"
send -- "sshadminPassword\r"
expect "*sshadmin@*"
send "su -\n"
expect "*?assword:*"
send -- "rootPassword\r"
send "uptime\n"
interact

1. Where 1707 is the ssh port,
2. ipaddress is the IP address of your server to which you need to login.
3. Replace "sshadminPassword" with your sshadmin password.
4. Replace "rootPassword" with your root password.
5. uptime is the command to execute after login to the server. You can give any command here.


You can also try (MTputty) in Windows machine for this purpose.
After installing the Mtputty

Go to Server Menu >> Add Server >> Script Tab

Enter the below code :

###_SLEEP:10000
sshadmin
###_SLEEP:2000
sshadmnpassword
###_SLEEP:10000
su - root
###_SLEEP:2000
rootpassword
###_SLEEP:200


1. Replace sshadminpassword with your sshadmin password.
2. Replace rootpassword with your root password.


Comments

Post a Comment

Popular posts from this blog

Password reset too simplistic/systematic issue

Some time when we try to reset the password of our user in linux it will show as simple and systematic as below: BAD PASSWORD: it is too simplistic/systematic no matter how hard password you give it will show the same. Solution: ######### Check if your password is Ok with the below command, jino@ndz~$ echo 'D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l' | cracklib-check D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l: it is too simplistic/systematic Now Create a password with the below command : jino@ndz~$ echo $(tr -dc '[:graph:]' 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K; You can see that this password will be ok with the cracklib-check. jino@ndz~$ echo '7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;' | cracklib-check                 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;: OK Thats all, Thanks.
Post a Comment
Read more

Nginx Ingress controller setup in K8S MultiNode Cluster with HA-Proxy as External LB

https://github.com/nginxinc/kubernetes-ingress/blob/master/docs/installation.md Pre-requisites: ############### >> K8s cluster setup with 1 Master and 2 Worker nodes. >> Deployed an application with Deployment name "client-sb" >> Also you need to create an HA-proxy server by spinning an Ec2 instance. After login the Ha-proxy server. # yum install haproxy # vi /etc/haproxy/haproxy.cfg delete everything after the global and defaults starting from "Main front-end which proxys to the backend" paste the below code in the end of the file: --------------------- frontend http_front   bind *:80   stats uri /haproxy?stats   default_backend http_back backend http_back   balance roundrobin   server kube 10.0.1.14:80   server kube 10.0.1.12:80 --------------------- # systemctl status haproxy # systemctl enable haproxy # systemctl start haproxy 1. Create a Namespace, a SA, the Default Secret, the Customization Confi...
Post a Comment
Read more

Running K8s cluster service kubelet with Swap Memory Enabled

For enabling swap memory check the below link : https://jinojoseph.blogspot.com/2019/10/enable-swap-memory-using-swapfile-in.html # sudo vi /etc/systemd/system/kubelet.service.d/10-kubeadm.conf Add the KUBELET_EXTRA_ARGS line as below: ---------------------------------------- Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false" ExecStart= ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS Now kubelet.service changed on disk. Run 'systemctl daemon-reload' to reload units # sudo systemctl daemon-reload # sudo systemctl restart kubelet # sudo systemctl status kubelet That is all cheers :p
Post a Comment
Read more