Skip to main content

How to access ssh terminal in web browser on Linux

How to access ssh terminal in web browser on linux

Running “everything” in a web browser used to be a bold statement. However, due to the powerful HTML5/JavaScript stack, a web browser increasingly becomes a dominant application delivery platform.

In this tutorial, we will looking that, how to access an SSH terminal in a web browser on Linux. Web-based SSH is useful when the firewall you are behind is so restrictive that only HTTP(s) traffic can get through. Or in case when we don't have ssh access client tools(putty, ssh-client)


Shell In A Box (or shellinabox) is a web-based terminal emulator, Which can run as a web-based SSH client. It comes with its own web server (shellinaboxd) which exports a command line shell to a web-based terminal emulator via AJAX interface. Shell In a Box only needs JavaScript/CSS support from a web browser, and does not require any additional browser plugin.

 #############
#####Install shellinabox on Linux#################

To install shellinabox on Fedora:
 

[root@myserver ~]#  yum install openssl shellinabox

To install on Centos/RHEL:    # we need enable epel repository first.

[root@myserver ~]#  yum install openssl shellinabox

To install shellinabox on Debian, Ubuntu or Linux Mint:

[root@myserver ~]#  apt-get install openssl shellinabox

Configure Shellinabox Web Server:
By default shellinabox web server listens on 4200 TCP port on localhost. Now here i will change  the default port to 443 for HTTPS. For that, modify shellinabox configuration as follows.


Configure shellinabox On Fedora/CentOS/RHEL:

[root@myserver ~]# vim /etc/sysconfig/shellinaboxd

PORT=443            ----------------> default port is 4200

#specify the IP address of ssh server


OPTS="-s /:SSH:192.168.50.144"      ---------->my ssh server ip address:

save and exit now:

Configure shellinaboxd On Debian, Ubuntu or Linux Mint:

[root@myserver ~]# vim  /etc/default/shellinabox

SHELLINABOX_PORT=443

SHELLINABOX_ARGS="--o-beep -s /:SSH:192.168.50.144"

save and exit now:

Now because we are using 443 port number so now we need a self signed certificate, So here we need to create self signed certificate. We can create it as follows:

# cd /var/lib/shellinabox
# openssl genrsa -des3 -out myserver.key 1024
# openssl req -new -key myserver.key -out myserver.csr
# cp myserver.key myserver.key.org
# openssl rsa -in myserver.key.org -out myserver.key
# openssl x509 -req -days 365 -in myserver.csr -signkey myserver.key -out myserver.crt
# cat myserver.crt myserver.key > certificate.pem


Now start the service, There is same method to start service on each flavor of linux:

[root@myserver ~]# service shellinabox start  ---> On Ubuntu,debian,Linux Mint:


[root@myserver ~]# service shellinaboxd on  ---> On Fedora,RHEL,CentOS

Now verify the port number of shellinabox


[root@myserver ~]# netstat  -tupnl | grep shellinabox


Now open up your web browser, and navigate to https://. You should be able to see a web-based SSH console, and log in to the remote SSH server via web browser interface.











 

Comments

Post a Comment

Popular posts from this blog

LINUX CONTAINERS

LINUX CONTAINERS What is Linux Container:  Linux containers have different approach than the Virtualization technology. Simply we can say this is OS level Virtualization, which means all containers run on top of one linux operating system.  We can start containers on a hardware running machine or inside of running virtual machine. Each container run's as a fully isolated operating sysem. In container virtualization rather than having an entire Operating System guest OS, containers isolate the guest but do not virtualize the hardware. For running containers one needs a patched kernel and user tools, the kernel provides process isolation and performs resource management. Thus all containers are running under the same kernel but they still have their own file system, processes, memory etc. Linux based containers mainly involved with two concepts: 1. Namespaces 2. Cgroups ( Controll Groups) There are total 6 types of Namespaces: 1. PID Na...

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image download...

Canonical Kubernetes Platform

Recently,  Canonical has announce the release of the Canonical Kubernetes Platform version 1.32, a robust and user-friendly solution for seamless cluster creation and management. This platform is designed to simplify the deployment and maintenance of containerized workloads, making it an ideal choice for both developers and enterprises. Here are some of the attracting features of this Platform.  ZeroOps with Built-in Essentials:  The platform comes pre-configured with critical components such as networking, DNS, metrics server, local storage, ingress, gateway, and load balancer, enabling immediate productivity post-installation. Simplified Installation and Maintenance:   Leveraging snap packages, the installation process is straightforward, and automated patch upgrades enhance security without manual intervention. Effortless Scalability:  Adding new nodes is seamless, and achieving high availability requires minimal effort, ensuring your infrastructure sca...