delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2015/01/06/10:59:39

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:message-id:date:from:mime-version:to:subject
:references:in-reply-to:content-type:content-transfer-encoding;
q=dns; s=default; b=Z0SXFmnz3ATOp3SSSs7/8BOC7Z9gPLpx2mJDyqEuoIC
W1sAOSmQvJedLxVXijhpG6eGUmCO29JdmbjWArsHKK7QfEm2CJ+N9oFBLl7uKROp
Kh847VL4BWI4GneFSDNZwNQYOx+JSTCUY+DDSAmxkSVCOtFV3xCBFq806MAFdBZY
=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:message-id:date:from:mime-version:to:subject
:references:in-reply-to:content-type:content-transfer-encoding;
s=default; bh=rLD5oL/lMXyfdgKauUpre0uEW5g=; b=uxCd8OPVMaAACBSis
76zWrZ9bXhc+WLfomhZwxTTu+v4xEtC1zrFw1E+d6xHk6wpoTSMmIAar5L1xpuaF
Wx95rltcxjryaAubqlGi4SthWZqvbp6Jdykb9l5Ec0k0O0Djb8SW6cLPFAXxTue0
CNl6ODBCr2K/z67+nozlPL8GZQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-wi0-f175.google.com
X-Received: by 10.181.13.42 with SMTP id ev10mr37594813wid.78.1420559951347; Tue, 06 Jan 2015 07:59:11 -0800 (PST)
Message-ID: <54AC0645.2000001@gmail.com>
Date: Tue, 06 Jan 2015 16:59:01 +0100
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: SFTP Cipher Mismatch
References: <CAARiEzdZwOh8BrB0HpoFZ-Xz5Qcdiy_ARnhHf3jStgOOdRPrug AT mail DOT gmail DOT com>
In-Reply-To: <CAARiEzdZwOh8BrB0HpoFZ-Xz5Qcdiy_ARnhHf3jStgOOdRPrug@mail.gmail.com>
X-IsSubscribed: yes


On 1/6/2015 2:47 PM, Chris Johnston wrote:
> Hello,
>
>   I am attempting to set up Cygwin for Cisco’s Disaster Recovery System
> (9. 1.2.10000-28) to run SFTP backups through. I have followed this
> guide that I found through online searches
> (https://supportforums.cisco.com/sites/default/files/legacy/0/3/2/41230-Cygwin%20Setup.pdf)
> and think I have everything set up correctly. I can use Filezilla
> through port 22 and the user account I set up through the Cygwin
> terminal to access the server I’d like to back up to. However when I
> attempt to set up the DRS on Cisco’s site I get an error message
> saying that “Update Failed: Unable to access SFTP server. Please
> ensure the Username and Password are correct.”
>
> I know what you’re thinking, “This is a Cisco Question, this guy sent
> to the wrong list”. Well I talked to Cisco TAC and after the run
> around they said to reach out to you folks because our CUCM is sending
> in aes-128-cbc, whereas Cygwin is replying back with aes-128-ctr,
> which they say is a mismatch and causing my problem. I checked my
> ssh_config and aes128-cbc is listed under Ciphers. Is there a way to
> change how Cygwin is replying? When searching I haven’t found a clear
> command that lets me change the default.  Cisco’s suggestion was...
>
> To check if aes-128-cbc is enable , go to C:\cygwin\etc\sshd_config
> and check if the following line is there:
>
> Ciphers aes256-ctr,aes192-ctr,aes128-ctr,arcfour256,aes128-cbc

aes-128-ctr is the first reported on my config
eventually it is used as default;
have you tried to put only a single line

Ciphers aes128-cbc

and check if that works ?


> If the line is there make sure you have aes128-cbc in there
>
> ...There was not a line specifying aes128-cbc in SSHD_Config, but as I
> understand it that means it would go to the default which was in the
> SSH_Config, which did include aes128-cbc. Cisco’s suggestion of copy
> and pasting that line in the sshd_config didn’t work. Any help would
> be greatly appreciated.
>
> All the best,
>
> cojohnst
>


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019