DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 47V0ARxc4047163 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=gE1wnc7Y X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 463A2384DEC2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1725063026; bh=ujM2fcsDVJC8yXSc9ZxwCfO13Zp4gd8J4/PcMO4+yXk=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=gE1wnc7YHQvdED0xFt1IYWDjLJCSzTSsxctsDPhz6rP1kGAL0xt3uo9ie/LjJ+E/f qwLA4HsUz+SbKCtXrdcbpqq58tJ9p2Advsw7PhFkDfnCsMaS9WX0Tifnlxz7EenHKB OYogE6+OIFj8yTjJDWYpBuNOXzxMvHz6OpTz7ewI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5375E385020A ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 5375E385020A ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1725062959; cv=none; b=KnVvuUqHpJvKfImPsLw3mPOUmmLK1kizd1Z2VlkGFXk8A6p6wPijrvOvvhwWMzhDrIlIGahYODAp2AhNUIORiqcorVHQ8w3EMKo8YLBuBumN+vgEulIxLGTpoMthEp1jo9lm85ObMYyV8IUD1piIj6IEIHVZxJ7TPdFe/8EUTAw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1725062959; c=relaxed/simple; bh=1jDHAo245A4AGWRZEQXlrb4gnughgTUYN8L6GJ7MIR4=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=cCvN6ZhMj9SZL+vv51nuDJoLvA+DXVYNdZdIEL4CuCzxHzkcl45JBLkT7E49FEbQLynvQlOaPTTiDuAz0Z8SmN4VJVdkd3PMOTi3z6F5sRS9IkChDeyTrNOC2kmUWvu6jZvbMLtZGFl9FjHNRSPybtMfP5sE6CKGbcJwPUcXqo4= ARC-Authentication-Results: i=1; server2.sourceware.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725062956; x=1725667756; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1NJE4Wbehx9ifQedCg1H3opb1CRCeFOCP7OUpneJyaE=; b=aDSUeKNyqHwqQjPjA80LKWUCJ6xhLOBIn8Ukw5CZwYd+OlByNhHAb5lKWPeMqII53P bzZl0TbOfXBudDZjgYhoV1VitTc8ZP4dKWGSQbBSu7QWddAbSJf/5tL0rQnZdYrPXeWR 46jdqUVidACrWnWf8vmdma6+cl1QRrHds3pgLITxnyPQogTWkYtcbGhcb7Td2uQ4kRlE fyklt30QfC6lTy9YdVschtLFuviaWswc4GmS1X6nLN5w2zyVdZdJhV1Ue5arnZAgCDSW SOAaHFP5L6bCvsQrxzRcvz+z7FlXHJOf5PFBoKXpy8jTsR1DTbODbwbkSu4Yisk9LqrR VRbQ== X-Gm-Message-State: AOJu0YylSLwuhe1OWY0Jg0AwE7OMJTTs89eMagIslNQAV914DRZTKqbm d2SJpbCMrbY64ABMZ/xGawjW4+tj/qrqz9GHqZGKJNGSArwcf0KHQZFcjCY4NnQa1Fjw3KGEhSL xzIzrl0rgd+NAp0/XYP7SHjvlUC9cNwPBd6GULA== X-Google-Smtp-Source: AGHT+IHPp4menFqL2hIoqk6OrybV/r2TCpGxUn+QV90Xkoqn/IrVH+HUZ+WgvETqL6DWLEEtWNyu1QftfhavI/A2LxM= X-Received: by 2002:a05:6602:1686:b0:81f:75bf:6570 with SMTP id ca18e2360f4ac-82a36ee0e9dmr50964639f.5.1725062956508; Fri, 30 Aug 2024 17:09:16 -0700 (PDT) MIME-Version: 1.0 References: <66d1eac5 DOT 050a0220 DOT 148618 DOT fa1cSMTPIN_ADDED_BROKEN AT mx DOT google DOT com> In-Reply-To: <66d1eac5.050a0220.148618.fa1cSMTPIN_ADDED_BROKEN@mx.google.com> Date: Fri, 30 Aug 2024 20:09:04 -0400 Message-ID: Subject: Re: ssh broken after updating cygwin To: cygwin AT cygwin DOT com X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Lee via Cygwin Reply-To: Lee Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 47V0ARxc4047163 On Fri, Aug 30, 2024 at 11:52 AM ASSI via Cygwin wrote: > > Lee via Cygwin writes: > > OK.. I didn't read the release notes. If I knew the upgrade was going > > to break ssh I wouldn't have upgraded, but hopefully there's a > > work-around besides downgrading. > > As noted in the announcement, you can build your own openssh that still > has the code active, but it will finally get removed at the beginning of > 2025 most likely. These ciphers have been deprecated since at least > 2015… > > https://lwn.net/Articles/958048/ Me building my own openssh is very much a last resort. I'd be tempted to use telnet instead :0 Thankfully it isn't going to come to that; tech support got me sorted out - I've got the latest software installed and I can ssh in again :) > > I already went poking around on the vendor's website and I can't find > > anything about a software upgrade that has something later than > > ssh-dss :( > > They surely would also support RSA keys or how old is that software and > still has an active vendor website? It's TP-Link switch. Silly me, the release notes say Upgraded SSH algorithms. duh.. I should have known. Thanks Lee -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple