Re: ssh protocol in 5.3

From: Erik Trulsson (ertr1013_at_student.uu.se)
Date: 12/31/04

  • Next message: John Conover: "Re: ssh protocol in 5.3"
    Date: Fri, 31 Dec 2004 23:44:40 +0100
    To: Robin Becker <robin@reportlab.com>
    
    

    On Sat, Jan 01, 2005 at 10:31:43PM +0000, Robin Becker wrote:
    > I have just upgraded one of my systems from 4.9 to 5.3 and even after
    > restoring my old .ssh folder it seems I cannot get ssh on a 4.9 system
    > to use protocol 1 with the 5.3 system.
    >
    > Am I being stupid or must I go through the pain of creating a whole new
    > set of keys for protocol 2.
    >
    > We use protocol 1 for legacy reasons ie we have a very old
    > implementation of ssh on our win32 PCs.
    >
    > I have tried various .ssh/config options, but nothing seems to help.

    Make sure that /etc/ssh/sshd_config on the 5.3 systems contains a line
    'Protocol 2,1'. Then restart the sshd daemon (or just send it a
    SIGHUP.) (The default value for this option was changed between 4.9
    and 5.3. On 4.9 the default value is "2,1" while on 5.3 the default is
    "2".)

    Reading the sshd(8) and sshd_config(5) manpages carefully might prove
    helpful.

    -- 
    <Insert your favourite quote here.>
    Erik Trulsson
    ertr1013@student.uu.se
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: John Conover: "Re: ssh protocol in 5.3"

    Relevant Pages

    • Re: CVS and version 9.0
      ... I this OpenSSH version is removed kerberos support from protocol SSH1, ... users who use identity keys for remote login with passphrases. ... ssh-add is called and doesn't have a real TTY, ...
      (alt.os.linux.suse)
    • XP APIPA unsolved Mystery Till date ????
      ... Reinstall of the TCP/IP protocol to restore Winsock functionality ... Go to both of the following keys, export each of them, and then ... Click Protocol, then Add ...
      (microsoft.public.windowsxp.network_web)
    • RE: The string universal unique identifier (UUID) is invalid.
      ... The issue may be caused by a corrupt winsock or TCP/IP ... Delete corrupted registry keys and reinstall TCP/IP protocol. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Request for Comments: Getting OpenSSH to work with ssh.com and itself
      ... All the titles involving mixed protocol versions ... "To be clear, the two protocol versions SSH1 and SSH2 do not interoperate, ... Leaving your keys around inside an ssh-agent indefinitely means ... > assume what you mean is connecting an SSH2 client to an OpenSSH server, ...
      (comp.security.ssh)
    • Re: Lost ability to connect to internet with cable/router
      ... Then expand Components / Network / click on Protocol - ... for replacing the winsock and winsock2 registry keys: ... Step 1: Delete registry keys ... It is important to restart the computer after deleting the Winsock keys. ...
      (microsoft.public.windowsxp.network_web)