Rsync problem - SSH

This is a discussion on Rsync problem - SSH ; Hello Newsgroup, I'm not an network expert. In our Institut i was able to use rsync with ssh for backup my data from PC to linux server. Since we got a new server the ssh version has changed from ssh1 ...

+ Reply to Thread
Results 1 to 15 of 15

Thread: Rsync problem

  1. Rsync problem

    Hello Newsgroup,


    I'm not an network expert.

    In our Institut i was able to use rsync with ssh for backup my data from
    PC to linux server. Since we got a new server the ssh version has
    changed from ssh1 to ssh2. To access the server I have to use a
    vpn-client (Cisco VPN-Client 4.0.3).

    I'm still able to get an ssh2 connection (only if i force ssh to use
    keyboard-interactive authentication). rsync is installed on the server
    as well. But when i try to use rsync with ssh2 i fail. (See my tries below.)


    Thank you in advance for every help,
    Bernd




    =============== Rsync Version on PC ===============================
    C:\rsync>rsync
    rsync version 2.5.1-dev protocol version 26
    Copyright (C) 1996-2002 by Andrew Tridgell and others

    Capabilities: 32-bit files, socketpairs, hard links, symlinks,
    batchfiles, no IP
    v6,
    32-bit system inums, 64-bit internal inums
    rsync is a file transfer program capable of efficient remote update
    via a fast differencing algorithm.



    ======== Login to server works (using SSH2 & keyboard interactive)
    ===========

    C:\rsync>ssh2 -h
    ssh2: SSH Secure Shell 3.2.0 Windows Client
    Copyright (c) 1995-2002 SSH Communications Security Corp
    SSH is a registered trademark and Secure Shell is a trademark of
    SSH Communications Security Corp (www.ssh.com).
    All rights reserved.

    C:\rsync>ssh2 -oallowedauthentications=keyboard-interactive
    xyz.xyz.xyz.xyz -l user
    Keyboard-interactive:
    Password:
    Keyboard-interactive:
    Authentication successful.
    Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.

    Last login: Wed Feb 22 10:33:40 2006 from 192.168.255.10

    ======== Rsync Version on server ===========

    user@server:~$ rsync
    rsync version 2.6.6 protocol version 29
    Copyright (C) 1996-2005 by Andrew Tridgell and others

    Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
    inplace, IPv6, 64-bit system inums, 64-bit internal inums


    ======== Try to use rsync and ssh2 fails ===========


    C:\rsync>rsync -av -e "ssh2
    -oallowedauthentications=keyboard-interactive -l user -d 3"
    user@xyz.xyz.xyz.xyz:/tst tst
    debug: Connecting to xyz.xzy.xyz.xyz, port 22... (SOCKS not used)
    debug: Ssh2/ssh2.c:2297: Entering event loop.
    debug: Ssh2Client/sshclient.c:1421: Creating transport protocol.
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    key_len: 16
    ..
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    key_len: 16
    ..
    debug: SshAuthMethodClient/sshauthmethodc.c:85: Added
    "keyboard-interactive" to
    usable methods.
    debug: Ssh2Client/sshclient.c:1462: Creating userauth protocol.
    debug: client supports 1 auth methods: 'keyboard-interactive'
    debug: Ssh2Common/sshcommon.c:530: local ip = abc.abc.abc.abc, local
    port = 1380
    debug: Ssh2Common/sshcommon.c:532: remote ip = xyz.xyz.xyz, remote port = 22
    debug: SshConnection/sshconn.c:1945: Wrapping...
    debug: Remote version: SSH-2.0-OpenSSH_3.8.1p1 Debian-krb5 3.8.1p1-7
    debug: OpenSSH: Major: 3 Minor: 8 Revision: 1
    debug: Ssh2Transport/trcommon.c:1518: All versions of OpenSSH handle kex
    guesses
    incorrectly.
    debug: Ssh2Transport/trcommon.c:1714: Computing algorithms from key
    exchange.
    debug: Ssh2Transport/trcommon.c:1901: lang s to c: `', lang c to s: `'
    debug: Ssh2Transport/trcommon.c:1967: c_to_s: cipher 3des-cbc, mac
    hmac-sha1, co
    mpression none
    debug: Ssh2Transport/trcommon.c:1970: s_to_c: cipher 3des-cbc, mac
    hmac-sha1, co
    mpression none
    debug: SshProtoTrKex/trkex.c:481: Making first key exchange packet.
    debug: Remote host key found from database.
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    key_len
    : 24.
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    key_len
    : 24.
    debug: Ssh2Common/sshcommon.c:331: Received SSH_CROSS_STARTUP packet
    from connec
    tion protocol.
    debug: Ssh2Common/sshcommon.c:381: Received SSH_CROSS_ALGORITHMS packet
    from con
    nection protocol.
    debug: server offers auth methods
    'gssapi-with-mic,publickey,gssapi,keyboard-int
    eractive'.
    Keyboard-interactive:
    Password:
    debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    respons
    e packet.
    Keyboard-interactive:
    debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    respons
    e packet.
    debug: Ssh2Common/sshcommon.c:299: Received SSH_CROSS_AUTHENTICATED
    packet from
    connection protocol.
    debug: Ssh2/ssh2.c:817: forward_x11 = TRUE, forward_agent = TRUE
    debug: Ssh2Common/sshcommon.c:840: num_channels now 1
    debug: SshStdioStream/sshwinstdiostream.c:372: disconnection signaled to
    stdio s
    tream.
    debug: SshConnection/sshconn.c:406: EOF from channel stream
    debug: SshConnection/sshconn.c:674: EOF received on write from channel
    0xb3f258,
    extended stream 0.
    debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    ignoring
    debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    ignoring
    debug: SshStdioStream/sshwinstdiostream.c:286: eof outputted to stdio
    stream.
    debug: Ssh2ChannelSession/sshchsession.c:1923: received exit status : 12
    debug: Ssh2Common/sshcommon.c:807: num_channels now 0
    debug: Got session close with exit_status=12
    debug: destroying client struct...
    debug: Ssh2Client/sshclient.c:1497: Destroying client.
    debug: SshConfig/sshconfig.c:2313: Freeing pki. (host_pki != NULL,
    user_pki = NU
    LL)
    debug: SshCertDB/cert-db.c:727: memory left 0
    debug: SshConnection/sshconn.c:1997: Destroying SshConn object.
    debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b37268 is
    being dest
    royed.
    debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b371f0 is
    being dest
    royed.
    rsync: read error: Connection reset by peer
    rsync error: error in rsync protocol data stream (code 12) at io.c(151)

    C:\rsync>


  2. Re: Rsync problem

    Bernd Breitschaedel wrote:
    > Hello Newsgroup,
    >
    >
    > I'm not an network expert.
    >
    > In our Institut i was able to use rsync with ssh for backup my data
    > from PC to linux server. Since we got a new server the ssh version
    > has changed from ssh1 to ssh2. To access the server I have to use a
    > vpn-client (Cisco VPN-Client 4.0.3).


    That doesn't say much about the version of SSH on the server, or on the PC.
    I assume it's not OpenSSH on your local client? And can you connect to it
    with a good known client, such as Putty?



  3. Re: Rsync problem

    Nico Kadel-Garcia schrieb:

    > That doesn't say much about the version of SSH on the server, or on the PC.
    > I assume it's not OpenSSH on your local client? And can you connect to it
    > with a good known client, such as Putty?


    Thank you Nico for your awnser,


    Yes i can log in using Putty on my PC.

    The ssh2.exe was installed on my PC with a programm called
    "SSH Secure Shell" Version 3.2.0 (Build 267) by SSH Communucations
    Security Corp. http://www.ssh.com/

    The OS on the server is Debian GNU/Linux. I guess the ssh version on the
    server is the standard one in this distribution.

    Maybe this might help:
    =====
    user@server~$ openssl version -a
    OpenSSL 0.9.7e 25 Oct 2004
    built on: Sun Nov 14 19:36:52 UTC 2004
    platform: debian-i386-i686/cmov
    options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)
    blowfish(idx)
    compiler: gcc -fPIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
    -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DOPENSSL_NO_IDEA -DOPENSSL_NO_MDC2
    -DOPENSSL_NO_RC5 -DL_ENDIAN -DTERMIO -O3 -march=i686 -mcpu=i686
    -fomit-frame-pointer -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
    OPENSSLDIR: "/usr/lib/ssl"
    =====


    Greetings,
    Bernd




  4. Re: Rsync problem

    Nico Kadel-Garcia schrieb:

    >
    > That doesn't say much about the version of SSH on the server, or on the PC.
    > I assume it's not OpenSSH on your local client? And can you connect to it
    > with a good known client, such as Putty?
    >
    >


    Hy again,

    Here are some tries using plink.exe which i've got from the PuTTY homepage.

    Same again:
    - I can log in using plink.
    - Using of rsync and plink fails.


    Greetings,
    Bernd



    ==========

    C:\rsync>plink
    PuTTY Link: command-line connection utility
    Release 0.58
    Usage: plink [options] [user@]host [command]
    ("host" can also be a PuTTY saved session name)
    Options:


    =========

    C:\rsync>plink user@xyz.xyz.xyz.xyz
    Using username "user".
    Using keyboard-interactive authentication.
    Password:
    Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.

    Last login: Wed Feb 22 14:02:40 2006 from 192.168.255.2
    user@server:~$

    ==========
    C:\rsync>rsync -av -e plink user@xyz.xyz.xyz.xyz:/tst tst
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    ^C
    Using keyboard-interactive authentication.
    rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)

    ==========

    C:\rsync>rsync -av -e "plink -l user" user@xyz.xyz.xyz.xyz:/tst tst

    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    ^C
    rsync error: unexplained error (code 58) at rsync.c(229)

  5. Re: Rsync problem

    Bernd Breitschaedel wrote:
    > Hello Newsgroup,
    >
    >
    > I'm not an network expert.
    >
    > In our Institut i was able to use rsync with ssh for backup my data from
    > PC to linux server. Since we got a new server the ssh version has
    > changed from ssh1 to ssh2. To access the server I have to use a
    > vpn-client (Cisco VPN-Client 4.0.3).
    >
    > I'm still able to get an ssh2 connection (only if i force ssh to use
    > keyboard-interactive authentication). rsync is installed on the server
    > as well. But when i try to use rsync with ssh2 i fail. (See my tries
    > below.)
    >
    >
    > Thank you in advance for every help,
    > Bernd
    >
    >
    >
    >
    > =============== Rsync Version on PC ===============================
    > C:\rsync>rsync
    > rsync version 2.5.1-dev protocol version 26
    > Copyright (C) 1996-2002 by Andrew Tridgell and others
    >
    > Capabilities: 32-bit files, socketpairs, hard links, symlinks,
    > batchfiles, no IP
    > v6,
    > 32-bit system inums, 64-bit internal inums
    > rsync is a file transfer program capable of efficient remote update
    > via a fast differencing algorithm.
    >
    >
    >
    > ======== Login to server works (using SSH2 & keyboard interactive)
    > ===========
    >
    > C:\rsync>ssh2 -h
    > ssh2: SSH Secure Shell 3.2.0 Windows Client
    > Copyright (c) 1995-2002 SSH Communications Security Corp
    > SSH is a registered trademark and Secure Shell is a trademark of
    > SSH Communications Security Corp (www.ssh.com).
    > All rights reserved.
    >
    > C:\rsync>ssh2 -oallowedauthentications=keyboard-interactive
    > xyz.xyz.xyz.xyz -l user
    > Keyboard-interactive:
    > Password:
    > Keyboard-interactive:
    > Authentication successful.
    > Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux
    >
    > The programs included with the Debian GNU/Linux system are free software;
    > the exact distribution terms for each program are described in the
    > individual files in /usr/share/doc/*/copyright.
    >
    > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    > permitted by applicable law.
    >
    > Last login: Wed Feb 22 10:33:40 2006 from 192.168.255.10
    >
    > ======== Rsync Version on server ===========
    >
    > user@server:~$ rsync
    > rsync version 2.6.6 protocol version 29
    > Copyright (C) 1996-2005 by Andrew Tridgell and others
    >
    > Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
    > inplace, IPv6, 64-bit system inums, 64-bit internal inums
    >
    >
    > ======== Try to use rsync and ssh2 fails ===========
    >
    >
    > C:\rsync>rsync -av -e "ssh2
    > -oallowedauthentications=keyboard-interactive -l user -d 3"
    > user@xyz.xyz.xyz.xyz:/tst tst
    > debug: Connecting to xyz.xzy.xyz.xyz, port 22... (SOCKS not used)
    > debug: Ssh2/ssh2.c:2297: Entering event loop.
    > debug: Ssh2Client/sshclient.c:1421: Creating transport protocol.
    > debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    > key_len: 16
    > .
    > debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    > key_len: 16
    > .
    > debug: SshAuthMethodClient/sshauthmethodc.c:85: Added
    > "keyboard-interactive" to
    > usable methods.
    > debug: Ssh2Client/sshclient.c:1462: Creating userauth protocol.
    > debug: client supports 1 auth methods: 'keyboard-interactive'
    > debug: Ssh2Common/sshcommon.c:530: local ip = abc.abc.abc.abc, local
    > port = 1380
    > debug: Ssh2Common/sshcommon.c:532: remote ip = xyz.xyz.xyz, remote port
    > = 22
    > debug: SshConnection/sshconn.c:1945: Wrapping...
    > debug: Remote version: SSH-2.0-OpenSSH_3.8.1p1 Debian-krb5 3.8.1p1-7
    > debug: OpenSSH: Major: 3 Minor: 8 Revision: 1
    > debug: Ssh2Transport/trcommon.c:1518: All versions of OpenSSH handle kex
    > guesses
    > incorrectly.
    > debug: Ssh2Transport/trcommon.c:1714: Computing algorithms from key
    > exchange.
    > debug: Ssh2Transport/trcommon.c:1901: lang s to c: `', lang c to s: `'
    > debug: Ssh2Transport/trcommon.c:1967: c_to_s: cipher 3des-cbc, mac
    > hmac-sha1, co
    > mpression none
    > debug: Ssh2Transport/trcommon.c:1970: s_to_c: cipher 3des-cbc, mac
    > hmac-sha1, co
    > mpression none
    > debug: SshProtoTrKex/trkex.c:481: Making first key exchange packet.
    > debug: Remote host key found from database.
    > debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    > key_len
    > : 24.
    > debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    > key_len
    > : 24.
    > debug: Ssh2Common/sshcommon.c:331: Received SSH_CROSS_STARTUP packet
    > from connec
    > tion protocol.
    > debug: Ssh2Common/sshcommon.c:381: Received SSH_CROSS_ALGORITHMS packet
    > from con
    > nection protocol.
    > debug: server offers auth methods
    > 'gssapi-with-mic,publickey,gssapi,keyboard-int
    > eractive'.
    > Keyboard-interactive:
    > Password:
    > debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    > respons
    > e packet.
    > Keyboard-interactive:
    > debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    > respons
    > e packet.
    > debug: Ssh2Common/sshcommon.c:299: Received SSH_CROSS_AUTHENTICATED
    > packet from
    > connection protocol.
    > debug: Ssh2/ssh2.c:817: forward_x11 = TRUE, forward_agent = TRUE
    > debug: Ssh2Common/sshcommon.c:840: num_channels now 1
    > debug: SshStdioStream/sshwinstdiostream.c:372: disconnection signaled to
    > stdio s
    > tream.
    > debug: SshConnection/sshconn.c:406: EOF from channel stream
    > debug: SshConnection/sshconn.c:674: EOF received on write from channel
    > 0xb3f258,
    > extended stream 0.
    > debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    > ignoring
    > debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    > ignoring
    > debug: SshStdioStream/sshwinstdiostream.c:286: eof outputted to stdio
    > stream.
    > debug: Ssh2ChannelSession/sshchsession.c:1923: received exit status : 12
    > debug: Ssh2Common/sshcommon.c:807: num_channels now 0
    > debug: Got session close with exit_status=12
    > debug: destroying client struct...
    > debug: Ssh2Client/sshclient.c:1497: Destroying client.
    > debug: SshConfig/sshconfig.c:2313: Freeing pki. (host_pki != NULL,
    > user_pki = NU
    > LL)
    > debug: SshCertDB/cert-db.c:727: memory left 0
    > debug: SshConnection/sshconn.c:1997: Destroying SshConn object.
    > debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b37268 is
    > being dest
    > royed.
    > debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b371f0 is
    > being dest
    > royed.
    > rsync: read error: Connection reset by peer
    > rsync error: error in rsync protocol data stream (code 12) at io.c(151)
    >
    > C:\rsync>
    >


    Are you using public key authentication, and if do, did the
    authorized_keys file get deleted or overwritten when the server was updated.

    --
    To reply by email remove "_nospam"

  6. Re: Rsync problem

    Chuck schrieb:

    >
    > Are you using public key authentication, and if do, did the
    > authorized_keys file get deleted or overwritten when the server was updated.
    >


    The server was replaced by an other (new ip as well). authorized_keys
    files of the old server are worthless and lost.

    On the new server public key authentication seems to be disabled.
    I've tried to use public key authentication with Putty my SSH Secure
    Client. But the only auth method which seems to work is
    keyboard-interactive.

    Thats why i'm use ssh as follows:
    ssh2 -oallowedauthentications=keyboard-interactive

    When i use plink.exe also keyboard-interactive is used (with no need
    for an extra command line option).


    Greetings,
    Bernd


    ===============

    C:\rsync>plink user@xyz.xyz.xyz.xyz
    Using username "user".
    Using keyboard-interactive authentication.
    Password:
    Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.

    Last login: Wed Feb 22 14:02:40 2006 from abc.abc.abc.abc
    user@server:~$

  7. Re: Rsync problem - still unsolved

    I'm a bit disappointed because my problem is still unsolved.
    I would greatly appreciate any further help.

    Thanks,
    Bernd


  8. Re: Rsync problem - still unsolved

    Bernd Breitschaedel writes:

    >I'm a bit disappointed because my problem is still unsolved.
    >I would greatly appreciate any further help.


    Perhaps your nearest doctor?
    Thinking that other people spend all of their time thinking about your
    issues, and have memorized what all your problems are is not rational
    thought. If you want help you have to tell people what the problem is as
    clearly as possible, and then they may or may not help you, either through
    ability or desire.




  9. Re: Rsync problem - still unsolved

    On Thu, 09 Mar 2006 15:18:10 +0100, Bernd Breitschaedel wrote:

    >I'm a bit disappointed because my problem is still unsolved.
    >I would greatly appreciate any further help.


    This message has precisely zero technical content, and me xtal
    ball is bust... Seems like you gonna stay disappointed until
    you lookup ESR's how to ask questions and follow his advice.

    Grant.
    --
    Cats are smarter than dogs. You can't make eight cats pull
    a sled through the snow.

  10. Re: Rsync problem - still unsolved

    Unruh schrieb:
    > Perhaps your nearest doctor?


    Do you think my doctor has better ssh-knowlege than the community in
    c.s.ssh?

    > Thinking that other people spend all of their time thinking about your
    > issues, and have memorized what all your problems are is not rational
    > thought.


    I agree.
    That's why I have send my posing as a follow-up to my first posting.
    Every serious news-client should fast and easily allow an qualified user
    to find the problem I am refering to.
    (And i wanted to avoid "learn.to/quote" - replies)

    > If you want help you have to tell people what the problem is as
    > clearly as possible, and then they may or may not help you, either through
    > ability or desire.


    I think i did. And i tried out all thankworthy suggestions and posted
    the results in my thread. Since there was no further activity in my
    thread, i thought a reader could easily think my problem is already solved.


    Peace,
    Bernd


  11. Re: Rsync problem - still unsolved

    Bernd Breitschaedel writes:


    To: berndb@sbox.tugraz.at
    From: Unruh
    From: Unruh
    Orig-To: Bernd Breitschaedel
    Subject: Re: Rsync problem - still unsolved
    Newsgroups: comp.security.ssh
    References: <43fc37b6$0$12384$3b214f66@aconews.univie.ac.at> <4410375d$0$11610$3b214f66@aconews.univie.ac.at> <44118041$0$12642$3b214f66@aconews.univie.ac.at>

    In comp.security.ssh you write:

    >Unruh schrieb:
    >> Perhaps your nearest doctor?


    >Do you think my doctor has better ssh-knowlege than the community in
    >c.s.ssh?


    Yes, he is more of an expert than we are at diagnosing why someone has a
    completely warped view of how the world operates.


    >> Thinking that other people spend all of their time thinking about your
    >> issues, and have memorized what all your problems are is not rational
    >> thought.


    >I agree.
    >That's why I have send my posing as a follow-up to my first posting.


    So what was the point of this thread?

    >Every serious news-client should fast and easily allow an qualified user
    >to find the problem I am refering to.
    >(And i wanted to avoid "learn.to/quote" - replies)


    Again you seem to think that readers are willing to put in time and effort
    figuring out what your problem is. If you want a solution, post the problem
    in the same posting as the request for solution.


    >> If you want help you have to tell people what the problem is as
    >> clearly as possible, and then they may or may not help you, either through
    >> ability or desire.


    >I think i did. And i tried out all thankworthy suggestions and posted


    No you did not. Your post had zero information in it.

    >the results in my thread. Since there was no further activity in my
    >thread, i thought a reader could easily think my problem is already solved.


    No, they do not. They do not think about your problem at all. If you want
    more information or help it is up to you to once again tell the world what
    the problem is.

    Even after you have posted 20 lines of text, and I have posted more than
    that, neither I nor anyone else has any idea what the problem is.
    And no, I am not going to go searching to try to find out. If you do not
    think it is important enough to post in your request for a response, I do
    not think it is important enough to search for it.

    I do have the decency to let you know what is happening, so you cease
    wondering why noone is responding, but I am sure that
    you will simply interpret that negatively.






  12. Re: Rsync problem - still unsolved

    On 10 Mar 2006 20:44:36 GMT, Unruh wrote:

    >Bernd Breitschaedel writes:

    ....

    >>the results in my thread. Since there was no further activity in my
    >>thread, i thought a reader could easily think my problem is already solved.

    >
    >No, they do not. They do not think about your problem at all.


    Yes, and I'm about to KF this thread, not interested. Seems like
    OP is clueless and desires to remain so.

    Unlike many man pages, `man rsync` has practical examples to help
    get one going.

    Grant.
    --
    Cats are smarter than dogs. You can't make eight cats pull
    a sled through the snow.

  13. Re: Rsync problem - still unsolved

    Hello Unruh!
    Hello Grant!

    Unruh wrote:

    > So what was the point of this thread?


    Seems that in your newsclient the thread starts with my message from the
    9.3.2006.

    My client shows my message from the 22.2.06
    43fc37b6$0$12384$3b214f66@aconews.univie.ac.at
    as first posting of the thread, where i tried to expain my problem.

    I just wanted to reactive this old thread, because someone willing to
    help me could think this problem is already out of date in our fast
    living world.
    Starting a new thread with exactly the same topic just a few weeks later
    seemed to me like spamming. Adding an other message to an old thread
    seemed to me ok.

    ============================================
    Anyhow: Once again the description of my Problem


    I'm not an network expert.

    In our Institut i was able to use rsync with ssh for backup my data from
    PC to linux server. Since we got a new server (new hardware & new IP)
    the ssh version has changed from ssh1 to ssh2. To access the server I
    have to use a vpn-client (Cisco VPN-Client 4.0.3).

    I'm still able to get an ssh2 connection (only with keyboard-interactive
    authentication which is ok for me). rsync is installed on the server as
    well. But when i try to use rsync with ssh2 i fail. (See my tries below.)

    SSH - version on server:
    -------------------------
    user@server~$ openssl version -a
    OpenSSL 0.9.7e 25 Oct 2004
    built on: Sun Nov 14 19:36:52 UTC 2004
    platform: debian-i386-i686/cmov
    options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)
    blowfish(idx)
    compiler: gcc -fPIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
    -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DOPENSSL_NO_IDEA -DOPENSSL_NO_MDC2
    -DOPENSSL_NO_RC5 -DL_ENDIAN -DTERMIO -O3 -march=i686 -mcpu=i686
    -fomit-frame-pointer -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
    OPENSSLDIR: "/usr/lib/ssl"

    I tried to use

    - plink.exe (putty) as a well known client and
    - ssh2.exe ("SSH Secure Shell" Version 3.2.0 (Build 267) by SSH
    Communucations Security Corp.) because of its comprehensive debugging
    information

    as SSH-client.

    Please see my tries below.



    Thank you in advance for every help,
    Bernd

    PS.:
    I've looked at man rsync,
    I've googled
    I've studied especially
    - http://www.samba.org/rsync/
    - http://www.snailbook.com/faq/
    I've tried many hours by my own to get this working,
    but failed.




    ************** Software used **************************************
    =============== Rsync Version on PC ===============================
    C:\rsync>rsync
    rsync version 2.5.1-dev protocol version 26
    Copyright (C) 1996-2002 by Andrew Tridgell and others

    Capabilities: 32-bit files, socketpairs, hard links, symlinks,
    batchfiles, no IP
    v6,
    32-bit system inums, 64-bit internal inums
    rsync is a file transfer program capable of efficient remote update
    via a fast differencing algorithm.

    ======== Rsync Version on server ===========

    user@server:~$ rsync
    rsync version 2.6.6 protocol version 29
    Copyright (C) 1996-2005 by Andrew Tridgell and others

    Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
    inplace, IPv6, 64-bit system inums, 64-bit internal inums

    ************************** SSH2.exe tries **************************
    ======== Login to server works (using SSH2 & keyboard interactive)
    ===========

    C:\rsync>ssh2 -h
    ssh2: SSH Secure Shell 3.2.0 Windows Client
    Copyright (c) 1995-2002 SSH Communications Security Corp
    SSH is a registered trademark and Secure Shell is a trademark of
    SSH Communications Security Corp (www.ssh.com).
    All rights reserved.

    C:\rsync>ssh2 -oallowedauthentications=keyboard-interactive
    xyz.xyz.xyz.xyz -l user
    Keyboard-interactive:
    Password:
    Keyboard-interactive:
    Authentication successful.
    Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.

    Last login: Wed Feb 22 10:33:40 2006 from 192.168.255.10


    ======== Try to use rsync and ssh2 fails ===========


    C:\rsync>rsync -av -e "ssh2
    -oallowedauthentications=keyboard-interactive -l user -d 3"
    user@xyz.xyz.xyz.xyz:/tst tst
    debug: Connecting to xyz.xzy.xyz.xyz, port 22... (SOCKS not used)
    debug: Ssh2/ssh2.c:2297: Entering event loop.
    debug: Ssh2Client/sshclient.c:1421: Creating transport protocol.
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    key_len: 16
    ..
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    key_len: 16
    ..
    debug: SshAuthMethodClient/sshauthmethodc.c:85: Added
    "keyboard-interactive" to
    usable methods.
    debug: Ssh2Client/sshclient.c:1462: Creating userauth protocol.
    debug: client supports 1 auth methods: 'keyboard-interactive'
    debug: Ssh2Common/sshcommon.c:530: local ip = abc.abc.abc.abc, local
    port = 1380
    debug: Ssh2Common/sshcommon.c:532: remote ip = xyz.xyz.xyz, remote port = 22
    debug: SshConnection/sshconn.c:1945: Wrapping...
    debug: Remote version: SSH-2.0-OpenSSH_3.8.1p1 Debian-krb5 3.8.1p1-7
    debug: OpenSSH: Major: 3 Minor: 8 Revision: 1
    debug: Ssh2Transport/trcommon.c:1518: All versions of OpenSSH handle kex
    guesses
    incorrectly.
    debug: Ssh2Transport/trcommon.c:1714: Computing algorithms from key
    exchange.
    debug: Ssh2Transport/trcommon.c:1901: lang s to c: `', lang c to s: `'
    debug: Ssh2Transport/trcommon.c:1967: c_to_s: cipher 3des-cbc, mac
    hmac-sha1, co
    mpression none
    debug: Ssh2Transport/trcommon.c:1970: s_to_c: cipher 3des-cbc, mac
    hmac-sha1, co
    mpression none
    debug: SshProtoTrKex/trkex.c:481: Making first key exchange packet.
    debug: Remote host key found from database.
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    key_len
    : 24.
    debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    key_len
    : 24.
    debug: Ssh2Common/sshcommon.c:331: Received SSH_CROSS_STARTUP packet
    from connec
    tion protocol.
    debug: Ssh2Common/sshcommon.c:381: Received SSH_CROSS_ALGORITHMS packet
    from con
    nection protocol.
    debug: server offers auth methods
    'gssapi-with-mic,publickey,gssapi,keyboard-int
    eractive'.
    Keyboard-interactive:
    Password:
    debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    respons
    e packet.
    Keyboard-interactive:
    debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    respons
    e packet.
    debug: Ssh2Common/sshcommon.c:299: Received SSH_CROSS_AUTHENTICATED
    packet from
    connection protocol.
    debug: Ssh2/ssh2.c:817: forward_x11 = TRUE, forward_agent = TRUE
    debug: Ssh2Common/sshcommon.c:840: num_channels now 1
    debug: SshStdioStream/sshwinstdiostream.c:372: disconnection signaled to
    stdio s
    tream.
    debug: SshConnection/sshconn.c:406: EOF from channel stream
    debug: SshConnection/sshconn.c:674: EOF received on write from channel
    0xb3f258,
    extended stream 0.
    debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    ignoring
    debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    ignoring
    debug: SshStdioStream/sshwinstdiostream.c:286: eof outputted to stdio
    stream.
    debug: Ssh2ChannelSession/sshchsession.c:1923: received exit status : 12
    debug: Ssh2Common/sshcommon.c:807: num_channels now 0
    debug: Got session close with exit_status=12
    debug: destroying client struct...
    debug: Ssh2Client/sshclient.c:1497: Destroying client.
    debug: SshConfig/sshconfig.c:2313: Freeing pki. (host_pki != NULL,
    user_pki = NU
    LL)
    debug: SshCertDB/cert-db.c:727: memory left 0
    debug: SshConnection/sshconn.c:1997: Destroying SshConn object.
    debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b37268 is
    being dest
    royed.
    debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b371f0 is
    being dest
    royed.
    rsync: read error: Connection reset by peer
    rsync error: error in rsync protocol data stream (code 12) at io.c(151)

    C:\rsync>


    ************************** plink.exe tries **************************
    ========== Plink version ======

    C:\rsync>plink
    PuTTY Link: command-line connection utility
    Release 0.58
    Usage: plink [options] [user@]host [command]
    ("host" can also be a PuTTY saved session name)
    Options:


    ========== Using plink to login works ========================

    C:\rsync>plink user@xyz.xyz.xyz.xyz
    Using username "user".
    Using keyboard-interactive authentication.
    Password:
    Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.

    Last login: Wed Feb 22 14:02:40 2006 from xxxxxxxxxxxxxxxx
    user@server:~$

    ========== Using Plink with rsync fails again :-( ==============
    C:\rsync>rsync -av -e plink user@xyz.xyz.xyz.xyz:/tst tst
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    ^C
    Using keyboard-interactive authentication.
    rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)

    ==========




  14. Re: Rsync problem - still unsolved

    Bernd Breitschaedel writes:

    >Hello Unruh!
    >Hello Grant!


    >Unruh wrote:


    >> So what was the point of this thread?


    >Seems that in your newsclient the thread starts with my message from the
    >9.3.2006.


    You know once again you seem not to have gotten the message. People do NOT
    go chasing threads. People are NOT going to try to find out what your
    problem was just because you say you have a problem. People will quickly
    look at a post to see if it is of interest of if they can offer quick
    advice. You suffer from the delusion that just because you ask for help
    people around the world who have never met you will rush to help you. They
    will not.

    Your post below has lots of information. It is not at all clear that it is
    not an ssh problem rather than an rsync problem.

    Have you tried not using the -e option? rsync AFAIK uses ssh automatically.
    Ie most modern compiles have ssh as the default. Noone uses rsh anymore and
    it would be nuts to keep it as the default.

    Also, why specify keyboard-interactive? IF that that is the only one
    available it will be used anyway. If not, then it will fall back to that
    when other things fail.

    Also I note that you use ssh rather than openssh. I use openssh, and your
    commands work perfectly for me. On the other had openssh does not have
    -oallowedauthentications=keyboard-interactive
    as an allowed option. and demands a space after the -o.
    But ssh may be different.




    >My client shows my message from the 22.2.06
    >43fc37b6$0$12384$3b214f66@aconews.univie.ac.at
    >as first posting of the thread, where i tried to expain my problem.


    >I just wanted to reactive this old thread, because someone willing to
    >help me could think this problem is already out of date in our fast
    >living world.


    Yes, so why would you think anyone in the world would have memorized your
    problem?


    >Starting a new thread with exactly the same topic just a few weeks later
    >seemed to me like spamming. Adding an other message to an old thread


    No. "I had this problem with ssh and rsync. Although I have had suggestions
    and have tried x,y,z, none of them worked. Does anyone else have further
    suggestions?" is the way to ask.



    >seemed to me ok.


    Obviously not to a number of members of your audience.


    >============================================
    >Anyhow: Once again the description of my Problem


    When you describe a problem, first post the problem, what you have tried,
    and then post the details of your system and your software. You post the
    details first forcing people to wade through immense amounts of stuff
    simply to discover what the problem is. It is enough to put off the most
    dedicated helper.



    >I'm not an network expert.


    >In our Institut i was able to use rsync with ssh for backup my data from
    > PC to linux server. Since we got a new server (new hardware & new IP)
    >the ssh version has changed from ssh1 to ssh2. To access the server I
    >have to use a vpn-client (Cisco VPN-Client 4.0.3).


    >I'm still able to get an ssh2 connection (only with keyboard-interactive
    >authentication which is ok for me). rsync is installed on the server as
    >well. But when i try to use rsync with ssh2 i fail. (See my tries below.)


    >SSH - version on server:
    >-------------------------
    >user@server~$ openssl version -a
    >OpenSSL 0.9.7e 25 Oct 2004
    >built on: Sun Nov 14 19:36:52 UTC 2004
    >platform: debian-i386-i686/cmov
    >options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)
    >blowfish(idx)
    >compiler: gcc -fPIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
    >-DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DOPENSSL_NO_IDEA -DOPENSSL_NO_MDC2
    >-DOPENSSL_NO_RC5 -DL_ENDIAN -DTERMIO -O3 -march=i686 -mcpu=i686
    >-fomit-frame-pointer -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
    >OPENSSLDIR: "/usr/lib/ssl"


    >I tried to use


    >- plink.exe (putty) as a well known client and
    >- ssh2.exe ("SSH Secure Shell" Version 3.2.0 (Build 267) by SSH
    >Communucations Security Corp.) because of its comprehensive debugging
    >information


    >as SSH-client.


    >Please see my tries below.




    >Thank you in advance for every help,
    > Bernd


    >PS.:
    >I've looked at man rsync,
    >I've googled
    >I've studied especially
    >- http://www.samba.org/rsync/
    >- http://www.snailbook.com/faq/
    >I've tried many hours by my own to get this working,
    >but failed.





    >************** Software used **************************************
    >=============== Rsync Version on PC ===============================
    >C:\rsync>rsync
    >rsync version 2.5.1-dev protocol version 26
    >Copyright (C) 1996-2002 by Andrew Tridgell and others
    >
    >Capabilities: 32-bit files, socketpairs, hard links, symlinks,
    >batchfiles, no IP
    >v6,
    > 32-bit system inums, 64-bit internal inums
    >rsync is a file transfer program capable of efficient remote update
    >via a fast differencing algorithm.


    >======== Rsync Version on server ===========


    >user@server:~$ rsync
    >rsync version 2.6.6 protocol version 29
    >Copyright (C) 1996-2005 by Andrew Tridgell and others
    >
    >Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
    > inplace, IPv6, 64-bit system inums, 64-bit internal inums


    >************************** SSH2.exe tries **************************
    >======== Login to server works (using SSH2 & keyboard interactive)
    >===========


    >C:\rsync>ssh2 -h
    >ssh2: SSH Secure Shell 3.2.0 Windows Client
    >Copyright (c) 1995-2002 SSH Communications Security Corp
    >SSH is a registered trademark and Secure Shell is a trademark of
    >SSH Communications Security Corp (www.ssh.com).
    >All rights reserved.


    >C:\rsync>ssh2 -oallowedauthentications=keyboard-interactive
    >xyz.xyz.xyz.xyz -l user
    >Keyboard-interactive:
    >Password:
    >Keyboard-interactive:
    >Authentication successful.
    >Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux


    >The programs included with the Debian GNU/Linux system are free software;
    >the exact distribution terms for each program are described in the
    >individual files in /usr/share/doc/*/copyright.


    >Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    >permitted by applicable law.


    >Last login: Wed Feb 22 10:33:40 2006 from 192.168.255.10



    >======== Try to use rsync and ssh2 fails ===========



    >C:\rsync>rsync -av -e "ssh2
    >-oallowedauthentications=keyboard-interactive -l user -d 3"
    >user@xyz.xyz.xyz.xyz:/tst tst
    >debug: Connecting to xyz.xzy.xyz.xyz, port 22... (SOCKS not used)
    >debug: Ssh2/ssh2.c:2297: Entering event loop.
    >debug: Ssh2Client/sshclient.c:1421: Creating transport protocol.
    >debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    >key_len: 16
    >.
    >debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: none,
    >key_len: 16
    >.
    >debug: SshAuthMethodClient/sshauthmethodc.c:85: Added
    >"keyboard-interactive" to
    >usable methods.
    >debug: Ssh2Client/sshclient.c:1462: Creating userauth protocol.
    >debug: client supports 1 auth methods: 'keyboard-interactive'
    >debug: Ssh2Common/sshcommon.c:530: local ip = abc.abc.abc.abc, local
    >port = 1380
    >debug: Ssh2Common/sshcommon.c:532: remote ip = xyz.xyz.xyz, remote port = 22
    >debug: SshConnection/sshconn.c:1945: Wrapping...
    >debug: Remote version: SSH-2.0-OpenSSH_3.8.1p1 Debian-krb5 3.8.1p1-7
    >debug: OpenSSH: Major: 3 Minor: 8 Revision: 1
    >debug: Ssh2Transport/trcommon.c:1518: All versions of OpenSSH handle kex
    >guesses
    > incorrectly.
    >debug: Ssh2Transport/trcommon.c:1714: Computing algorithms from key
    >exchange.
    >debug: Ssh2Transport/trcommon.c:1901: lang s to c: `', lang c to s: `'
    >debug: Ssh2Transport/trcommon.c:1967: c_to_s: cipher 3des-cbc, mac
    >hmac-sha1, co
    >mpression none
    >debug: Ssh2Transport/trcommon.c:1970: s_to_c: cipher 3des-cbc, mac
    >hmac-sha1, co
    >mpression none
    >debug: SshProtoTrKex/trkex.c:481: Making first key exchange packet.
    >debug: Remote host key found from database.
    >debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    >key_len
    >: 24.
    >debug: Ssh2Transport/trcommon.c:2522: Allocating cipher: name: 3des-cbc,
    >key_len
    >: 24.
    >debug: Ssh2Common/sshcommon.c:331: Received SSH_CROSS_STARTUP packet
    >from connec
    >tion protocol.
    >debug: Ssh2Common/sshcommon.c:381: Received SSH_CROSS_ALGORITHMS packet
    >from con
    >nection protocol.
    >debug: server offers auth methods
    >'gssapi-with-mic,publickey,gssapi,keyboard-int
    >eractive'.
    >Keyboard-interactive:
    >Password:
    >debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    >respons
    >e packet.
    >Keyboard-interactive:
    >debug: Ssh2AuthKbdInteractiveClient/authc-kbd-interactive.c:244: Sending
    >respons
    >e packet.
    >debug: Ssh2Common/sshcommon.c:299: Received SSH_CROSS_AUTHENTICATED
    >packet from
    >connection protocol.
    >debug: Ssh2/ssh2.c:817: forward_x11 = TRUE, forward_agent = TRUE
    >debug: Ssh2Common/sshcommon.c:840: num_channels now 1
    >debug: SshStdioStream/sshwinstdiostream.c:372: disconnection signaled to
    >stdio s
    >tream.
    >debug: SshConnection/sshconn.c:406: EOF from channel stream
    >debug: SshConnection/sshconn.c:674: EOF received on write from channel
    >0xb3f258,
    > extended stream 0.
    >debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    >ignoring
    >debug: SshConnection/sshconn.c:1338: Received data when close_sent -
    >ignoring
    >debug: SshStdioStream/sshwinstdiostream.c:286: eof outputted to stdio
    >stream.
    >debug: Ssh2ChannelSession/sshchsession.c:1923: received exit status : 12
    >debug: Ssh2Common/sshcommon.c:807: num_channels now 0
    >debug: Got session close with exit_status=12
    >debug: destroying client struct...
    >debug: Ssh2Client/sshclient.c:1497: Destroying client.
    >debug: SshConfig/sshconfig.c:2313: Freeing pki. (host_pki != NULL,
    >user_pki = NU
    >LL)
    >debug: SshCertDB/cert-db.c:727: memory left 0
    >debug: SshConnection/sshconn.c:1997: Destroying SshConn object.
    >debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b37268 is
    >being dest
    >royed.
    >debug: SshStdioStream/sshwinstdiostream.c:316: stdio stream b371f0 is
    >being dest
    >royed.
    >rsync: read error: Connection reset by peer
    >rsync error: error in rsync protocol data stream (code 12) at io.c(151)


    >C:\rsync>



    >************************** plink.exe tries **************************
    >========== Plink version ======


    >C:\rsync>plink
    >PuTTY Link: command-line connection utility
    >Release 0.58
    >Usage: plink [options] [user@]host [command]
    > ("host" can also be a PuTTY saved session name)
    >Options:



    >========== Using plink to login works ========================


    >C:\rsync>plink user@xyz.xyz.xyz.xyz
    >Using username "user".
    >Using keyboard-interactive authentication.
    >Password:
    >Linux viffs1 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux


    >The programs included with the Debian GNU/Linux system are free software;
    >the exact distribution terms for each program are described in the
    >individual files in /usr/share/doc/*/copyright.


    >Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    >permitted by applicable law.


    >Last login: Wed Feb 22 14:02:40 2006 from xxxxxxxxxxxxxxxx
    >user@server:~$


    >========== Using Plink with rsync fails again :-( ==============
    >C:\rsync>rsync -av -e plink user@xyz.xyz.xyz.xyz:/tst tst
    >Using keyboard-interactive authentication.
    >Access denied
    >Using keyboard-interactive authentication.
    >Access denied
    >Using keyboard-interactive authentication.
    >Access denied
    >^C
    >Using keyboard-interactive authentication.
    >rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)


    >==========





  15. Re: Rsync problem - still unsolved

    Hello Unruh,


    Unruh schrieb:
    > Bernd Breitschaedel writes:
    >>Seems that in your newsclient the thread starts with my message from the
    >>9.3.2006.

    >
    > You know once again you seem not to have gotten the message. People do NOT
    > go chasing threads...


    Ok, I've to clearify some points:
    -) I did not expect the readers to have genius memory to remember my
    thread in all detail.
    -) I didn't want to do the readers time consuming resaerch to find my
    thread.
    -) Since the messages in my newsreader expire after about 3 months, I've
    incorrectly thought this would be the same for the majority of the other
    readers in c.s.ssh.
    -) Consequently, I thought the user would just have to do a single click
    at the starting point of the thread to find out about what problem I'm
    refering to. (You might say this is a imperinence as well, but a posting
    with 100+ lines but without any new infomation could IMO be anoying too.)

    > Your post below has lots of information. It is not at all clear that it is
    > not an ssh problem rather than an rsync problem.


    I want to run rsync with ssh, but failed. I don't know wheter my problem
    is mainly caused by ssh, rsync or the interaction of both. Since I've
    found no rsync-newsgroup i've posted in c.s.ssh and put "rsync" in the
    subject.

    > Have you tried not using the -e option? rsync AFAIK uses ssh automatically.
    > Ie most modern compiles have ssh as the default. Noone uses rsh anymore and
    > it would be nuts to keep it as the default.


    Dosn't work either:

    C:\rsync>rsync -av user@server:/tst tst

    Führt Befehle auf Remotehosts aus, auf denen der RSH-Dienst aktiv ist.

    RSH Host [-l Benutzername] [-n] Befehl

    Host Gibt den Remotehost zur Befehlsausführung an.
    -l Benutzername Gibt den Benutzernamen für den Remotehost an. Ohne
    Angabe
    des Parameters wird der aktuelle Benutzername verwendet.
    -n Leitet die Eingabe von RSH nach NULL um.
    Befehl Gibt den auszuführenden Befehl an.

    rsync: read error: Connection reset by peer
    rsync error: error in rsync protocol data stream (code 12) at io.c(151)

    > Also, why specify keyboard-interactive? IF that that is the only one
    > available it will be used anyway. If not, then it will fall back to that
    > when other things fail.


    C:\rsync>ssh2 user@server
    warning: Authentication failed.
    Disconnected; no more authentication methods available (No further
    authentication methods available.).


    > Also I note that you use ssh rather than openssh. I use openssh, and your
    > commands work perfectly for me. On the other had openssh does not have
    > -oallowedauthentications=keyboard-interactive
    > as an allowed option. and demands a space after the -o.
    > But ssh may be different.


    On http://www.openssh.com/windows.html I've found the link to Putty.
    I'm thinking putty uses OpenSSH but i'm not sure.
    My tries with plink also failed:

    C:\rsync>rsync -av -e plink user@xyz.xyz.xyz.xyz:/tst tst
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    Using keyboard-interactive authentication.
    Access denied
    ^C
    Using keyboard-interactive authentication.
    rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)

    >>seemed to me ok.

    > Obviously not to a number of members of your audience.


    seems so.

    > When you describe a problem, first post the problem, what you have tried,
    > and then post the details of your system and your software. You post the
    > details first forcing people to wade through immense amounts of stuff
    > simply to discover what the problem is. It is enough to put off the most
    > dedicated helper.


    Ok.



    Thank you for your technical support and for verbosely bringing me the
    insight, that messages might expire sooner for other readers.

    Greetings,
    Bernd


+ Reply to Thread