9 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hello Forum,
I'm using a bit of code from a script I found that allows me to capture the status code of connecting via SSH to remote servers:
ssh -qno StrictHostKeyChecking=no -o ConnectTimeout=1 user@$InputIP 'ls -l /home/user >/dev/null 2>&1' > /dev/null 2>&1
status="$(echo $?)"
echo... (4 Replies)
Discussion started by: greavette
4 Replies
2. Solaris
Hi,
Sorry if this question has been asked before, however, I have tried looking in the forum (and google in general) and I haven't found an answer, so I thought I'd ask here.
I am trying to use a GUI application in Solaris 10. Normally I connect with a VPN then SSH and use Xming to... (2 Replies)
Discussion started by: John_sp
2 Replies
3. Shell Programming and Scripting
Bonjour,
I have a large script with a lot of print statements and misc commands. Standard and error outputs are redirected like into the following code :
#!/usr/bin/ksh
LOG=/<some dir>/log
> $LOG
exec >>${LOG} 2>>${LOG}
print aaaaa
print bbbbb
print ccccc
...
some_cmd
That way,... (5 Replies)
Discussion started by: Fundix
5 Replies
4. UNIX for Advanced & Expert Users
Hello,
What is the best way to disallow new ssh connections for the duration of my session ?
I want to evade read/write collisions. Things work like that - one session put files on server, other copies these files and then deletes them. So in order to evade collision:
- I check if there are... (1 Reply)
Discussion started by: vilius
1 Replies
5. Solaris
Hello guys, I have one script running that I need to keep it running 24x7 so I'd like to know how can I implement a sort of monitoring process I mean if for some reason this process dies somehow it gets automatically started again.
Thanks. (8 Replies)
Discussion started by: cerioni
8 Replies
6. Ubuntu
Hello friends,
I'm connection to an external network using a VPN configured over an Ubuntu.
The problem is that whenever I get connected to a remote computer using my VPN as router, after a while, sometimes short, sometimes long, sometimes immediately, the connection gets lost and I've to... (1 Reply)
Discussion started by: lzcool
1 Replies
7. AIX
I'm investigating an issue where rsync's to an AIX server will sometimes fail. I suspect the problem might be due to the number of simultaneous SSH connections being made to the host dropping the rsync attempts. I'd like to view the number of open ssh connections. The who command will list logged... (1 Reply)
Discussion started by: indiana_tas
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I'm very new to Unix so please bear with me... :)
Here is my requirement:
I need to create a cron job to run two different scripts at 1 a.m. every day.
Here's what I did:
I used the "crontab -e" command and created a crontab file using the vi editor.
When I exit the editor using... (3 Replies)
Discussion started by: yogiB
3 Replies
9. BSD
just as the title says.
thanks.
#General Rule Sets
/sbin/ipfw add 0300 check-state
/sbin/ipfw add 0301 deny tcp from any to any in established
/sbin/ipfw add 0302 pass tcp from any to any out setup keep-state
/sbin/ipfw add 0303 pass udp from any to any out
#SSH FTP
/sbin/ipfw add 0400... (11 Replies)
Discussion started by: dwildgoose
11 Replies
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)