I know this question might have been asked a lot but couldn't find anything that worked. From a windows machine 'A' I can only SSH into Linux server 'B' from where I can SSH into another Linux server 'C'. I need to be able to run GUI interfaces on server C which run on my Windows machine. I have tried the X11 forwarding with a new tunnel but for some reason doesn't seem to work. I know I am doing something wrong. Any ideas?
Thanks.
Moderator's Comments:
Please use CODE tags when displaying sample code, sample input, and sample output.
Last edited by Don Cragun; 10-14-2015 at 09:29 PM..
Reason: Add CODE tags.
Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured
server:
/etc/hosts.allow:
all : all
all :all@all
setup my /etc/exports file... (4 Replies)
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
I want to connect RHEL server from my windows 7 Professional machine graphically. I logged into 1 RHEL server with IP, 10.101.17.80 using Putty from my Windows 7 professional machine. Now from this server, 10.101.17.80, I want to connect to another RHEL server 10.101.17.79. I used,
ssh -X... (1 Reply)
I am able to connect a RHEL server from my Windows machine using Putty (via ssh). My question is what is the advantage of using Xming instead of Putty? Is it that Xming would enable a graphical connect from the Windows machine to RHEL server?
I hope my question is clear that what is the... (9 Replies)
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Hi,
Sorry if this is an incorrect place for this question but I haven't been able to find any answers by searching the forums or on google. I am in the market for a new HP Z420 workstation and HP wants a lot more money for one with the HP Linux Installer kit vs. the exact same configuration in... (2 Replies)
Hello all, I am having a bit of an issue on my Spacewalk installation. Some amplifying information is that it is Spacewalk 2.3 installed on a RHEL 6 machine and I am attempting to install/update a RHEL 5 channel/repository. I am fairly new to Spacewalk so I am still learning but this is what I... (3 Replies)
Hi
We have RHEL 6.7 on an HP physical server and want to install RHEL 7 (not upgrade) on top of it by means of virtualization. Is it possible to install/configure RHEV/KVM virtualization on base RHEL 6.7 OS instance and then install RHEL 7 as a VM guest on it? If yes, could you please guide me... (1 Reply)
I have 2 RHEL 5.9 system where customized applications are running.
These 2 servers are with in a network (LAN) with each other.One application in say Server 1 can talk to another application in server 2 and vice versa.
The applications are exchanging data among each other.
Recently I am... (0 Replies)
Discussion started by: Anjan Ganguly
0 Replies
LEARN ABOUT DEBIAN
sslh
SSLH(1p) User Contributed Perl Documentation SSLH(1p)NAME
sslh - Switch incoming connection between SSH and SSL/HTTPS servers
SYNOPSIS
sslh [ -v ] [ -p [host:]port ] [ -t timeout ]
[ --ssh [host:]port ] [ --ssl [host:]port ]
DESCRIPTION
sslh is a simple script that lets you switch an incoming connection on a single port between distinct SSH and SSL/HTTPS servers.
sslh listens for connections on a port and is able to redirect them either to an HTTPS web server or a SSH server.
This lets one setup both a HTTPS web server and a SSH server and access them through the same host+port.
OPTIONS
The program follows the usual GNU command line syntax, with long options starting with two dashes.
-p, --port [host:]port
The port the proxy will listen to. If no port is given, 443 is used by default. If no host is given, "localhost" is used by default.
-s, --ssh [host:]port
The SSH server which the SSH connections must be forwarded to. If omitted, the default is localhost:22.
-l, --ssl, --https [host:]port
The HTTPS server which the HTTPS connections must be forwarded to. If omitted, the default is localhost:443.
-t, --timeout delay
Timeout in seconds before a silent incoming connection is considered as a SSH connection. The number can be fractional.
The default is 2seconds.
-v, --verbose
Verbose output. This option can be used several times for more verbose output.
EXAMPLE OF USE
Is this tool actually useful? Yes.
For example one can use it to access both a SSH server and a secure web server via a corporate proxy that only accepts to relay connections
to port 443. Creating a tunnel that passes SSH connection through a CONNECT-enabled web proxy is easy with connect-tunnel (also included in
the "Net::Proxy" distribution).
The proxy will let both SSH and HTTPS connections out (since they all point to port 443), and the home server will connect those incoming
connections to the appropriate server. This only requires to run the HTTPS server on a non standard port (not 443).
TECHNICAL NOTE
How can this proxy find out what kind of protocol is using a TCP connection to port 443, without being connected (yet) to the server? We
actually rely on a slight difference between the SSL and SSH protocols (found thanks to ethereal):
SSH Once the TCP connection is established, the server speaks first, presenting itself by saying something like:
SSH-2.0-OpenSSH_3.6.1p2 Debian 1:3.6.1p2-1
SSL With SSL, it's always the client that speaks first.
This means that sslh can be used with any pair of protocols/services that share this property (the client speaks first for one and the
server speaks first for the other).
AUTHORS
Original idea and C version
Frederic Ple "<sslh@wattoo.org>".
Perl versions
Philippe 'BooK' Bruhat "<book@cpan.org>".
SCRIPT HISTORY
Version 0.01 of the script was a quick hack designed in 2003 as a proof of concept.
Version 0.02 (and higher) are based on "Net::Proxy", and included with the "Net::Proxy" distribution. Version 0.02 didn't work, though.
Version 0.03 correctly initialised the "in" connector.
Version 0.04 lets the proxy listen on any address (instead of "localhost", which is still the default). Thanks to Dieter Voegtli for
spotting this.
SEE ALSO
Net::Proxy, Net::Proxy::Connector::dual.
COPYRIGHT
Copyright 2003-2006, Philippe Bruhat. All rights reserved.
LICENSE
This module is free software; you can redistribute it or modify it under the same terms as Perl itself.
perl v5.10.1 2009-10-18 SSLH(1p)