Re: having trouble with sshd

From: Ganbold (ganbold_at_micom.mng.net)
Date: 02/26/04

  • Next message: Dag-Erling Smørgrav: "Re: having trouble with sshd" 
    Date: Thu, 26 Feb 2004 18:14:47 +0800
To: des@des.no (Dag-Erling Smørgrav )

    Debug outputs of sshd when connecting client:

    psh# sshd -d -p 5999
    debug1: sshd version OpenSSH_3.7.1p2 FreeBSD-20040106
    debug1: private host key: #0 type 0 RSA1
    debug1: read PEM private key done: type DSA
    debug1: private host key: #1 type 2 DSA
    debug1: Bind to port 5999 on 0.0.0.0.
    Server listening on 0.0.0.0 port 5999.
    Generating 768 bit RSA key.
    RSA key generation complete.
    debug1: Server will not fork when running in debugging mode.
    debug1: res_init()
    Connection from 192.168.0.18 port 3578
    debug1: Client protocol version 1.5; client software version
    PuTTY-Release-0.53b
    debug1: no match: PuTTY-Release-0.53b
    debug1: Local version string SSH-1.99-OpenSSH_3.7.1p2 FreeBSD-20040106
    debug1: permanently_set_uid: 22/22
    debug1: Sent 768 bit server key and 1024 bit host key.
    debug1: Encryption type: blowfish
    debug1: Received session key; encryption turned on.
    debug1: Installing crc compensation attack detector.
    debug1: Attempting authentication for tsgan.
    debug1: PAM: initializing for "tsgan"
    debug1: PAM: setting PAM_RHOST to "ganbold.micom.mng.net"
    Failed none for tsgan from 192.168.0.18 port 3578
    Accepted password for tsgan from 192.168.0.18 port 3578
    Accepted password for tsgan from 192.168.0.18 port 3578
    debug1: monitor_child_preauth: tsgan has been authenticated by privileged
    process
    debug1: session_new: init
    debug1: session_new: session 0
    debug1: Installing crc compensation attack detector.
    debug1: Allocating pty.
    debug1: session_new: init
    debug1: session_new: session 0
    debug1: session_pty_req: session 0 alloc /dev/ttyp1
    debug1: PAM: setting PAM_TTY to "/dev/ttyp1"
    debug1: PAM: establishing credentials
    debug1: Setting controlling tty using TIOCSCTTY.
    debug1: Entering interactive session.
    debug1: server_init_dispatch_13
    debug1: server_init_dispatch_15
    debug1: Window change received.

    Ganbold

    At 04:08 PM 26.02.2004, you wrote:
    >Ganbold <ganbold@micom.mng.net> writes:
    > > At 12:38 AM 26.02.2004, you wrote:
    > > > The preferred method is now keyboard-interactive. If your client does
    > > > not support it, get a better client.
    > > I'm using putty-0.53b.
    >
    >putty supports keyboard-interactive, and it's even on by default. See
    >http://the.earth.li/~sgtatham/putty/0.54/puttydoc.txt, section 4.18.2.
    >
    >what protocol version are you using, btw?
    >
    >DES
    >--
    >Dag-Erling Smørgrav - des@des.no
    >_______________________________________________
    >freebsd-hackers@freebsd.org mailing list
    >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

  • Next message: Dag-Erling Smørgrav: "Re: having trouble with sshd"

    Relevant Pages

    • Re: Server refusing connection.
      ... the command line through my PuTTY client, but I cannot load the URLs ... I need some assistance to figure out why my ssh server is refusing my ... debug1: read PEM private key done: type RSA ... Server listening on 0.0.0.0 port 22. ...
      (comp.security.ssh)
    • OpenSSH 3.5p1 port forwarding problem on Solaris 2.8
      ... I'm trying to use port forwarding to get a SqlNet connections back thru ... This gets a Connection refused. ... debug1: Rhosts Authentication disabled, ...
      (comp.security.ssh)
    • Re: OPENSSH 3.4p1-3 on AIX 4.3.3
      ... Teh debug output from the server is exactly the same, ... another port. ... reverse dns setup properly for that client? ... debug1: Server will not fork when running in debugging mode. ...
      (SSH)
    • RE: port forwarding and oracle
      ... Objet: port forwarding and oracle ... forward the connection (using java thin client drivers) through it times ... debug1: Connection to port 2521 forwarding to dbserver port 1521 requested. ... debug1: channel 3: new ...
      (SSH)
    • OpenSSH through a Firewall
      ... I have an ssh through a firewall problem which I think should be easy ... currently only allows port 80 and port 21 through to the server(aka ... Here is the log output from the client end: ... debug1: read PEM private key done: type RSA ...
      (comp.security.ssh)