Help moving site Post: 302968322

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Moving machine to other site

Hi, I�d like to have some opinions of waht settings we should take note before power down a server and move it to other facilities. Of course, the first thing is check the backups. Thanks in advance.

2. IP Networking

port access to site to site VPN

Setup a site to site VPN between two cisco routers. One of the site locations is unable to access ports such as https://example.com:9001 How do I let them go into port 9001? They can ssh, ftp, telnet and everything else. Is this a VPN issue or ACL access issue? I put permit ip host...

3. IP Networking

How to establish site to site vpn - Linux machine and cisco asa?

Hi, I am trying to establish vpn between my linux server and cisco asa at client side. I installed openswan on my cent os. Linux Server eth0 - 182.2.29.10 Gateway - 182.2.29.1 eth1 - 192.9.200.75 I have simple IPtables Like WAN="eth0" LAN="eth1"

4. IP Networking

Does cisco 1921 router support site to site VPNs using IPSec?

Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? " A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that...

5. IP Networking

IPSec Openswan Site to Site VPN - Big Pain

Hi @all, I try to connect 2 LANs with IPSec/Openswan LAN 1: 192.168.0.0/24 LAN 2: 192.168.1.0/24 This is my Config: conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ...

6. What is on Your Mind?

Is this site for me?

Hello, I am new here and my name is Robert. I was actually looking for a forums website where I can go with questions regarding Linux and embedded Linux applications. I am fairly new (6 months) to the world of Linux and embedded Linux applications and the the learning curve is steep. When I am not...

LEARN ABOUT DEBIAN

secsh

SECSH(5)							    Lsh Manuals 							  SECSH(5)

NAME

       secsh - the Secure Shell protocol

DESCRIPTION

       secsh  is  a  protocol suite for secure remote login and other secure network services over an insecure network. It is outlined in [SECSH].
       It has three major components:

       The Transport layer protocol
	      This protocol, specified in [SECSH-TLP], provides  server  authentication,  confidentiality,  and  integrity  with  perfect  forward
	      secrecy.

       The User authentication protocol
	      This protocol, specified in [SECSH-AUTH], is used to authenticate a client to a server.

       The Connection protocol
	      This protocol, specified in [SECSH-CONN], multiplexes an encrypted tunnel into several logical channels.

IMPLEMENTATIONS

       Several implementations of the secsh protocol suite exist.

       The SSH2 product of SSH Communications Security Ltd., Finland <URL:http://www.ssh.fi> was the first. The secsh protocol suite has benefited
       a lot from their experience with their older SSH1 product, which is still in widespread use; it implements an older protocol ([SSH1]).

       The lsh suite of programs is a free implementation of the secsh protocol suite; it is distributed under the GNU General Public License.

REFERENCES

       [SECSH-ARCH] T. Ylonen, T. Kivinen, M. Saarinen, T. Rinne and S. Lehtinen, SSH Protocol Architecture, Internet draft, 6 August 1998

       [SECSH-TRANS] T. Ylonen, T. Kivinen, M. Saarinen, T. Rinne and S. Lehtinen, SSH Transport Layer Protocol, Internet draft, 6 August 1998

       [SECSH-AUTH] T. Ylonen, T. Kivinen, M. Saarinen, T. Rinne and S. Lehtinen, SSH Authentication Protocol, Internet draft, 6 August 1998

       [SECSH-CONN] T. Ylonen, T. Kivinen, M. Saarinen, T. Rinne and S. Lehtinen SSH Connection Protocol, Internet draft, 6 August 1998

       [SSH1] T. Ylonen, The SSH (Secure Shell) Remote Login Protocol, Internet draft (expired), 15 November 1995

TRADEMARKS

       SSH and Secure Shell are trademarks or registered trademarks of SSH Communications Security Ltd.

AUTHOR

       This man-page was written by J.H.M. Dassen (Ray) <jdassen@wi.LeidenUniv.nl>.

SEE ALSO

       lsh(1), lshd(8), ssh2(1), sshd2(8), ssh1(1), sshd1(8)

LSH
								   JANUARY 1999 							  SECSH(5)