DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 484AC0Ym2140163 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=dEpxX1yP X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5FD76385F032 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1725444718; bh=Qh/pwcAbO1TL0I1FVA08bhOq99Aeac41VxSaDDC87/M=; h=References:In-Reply-To:Date:Subject:To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=dEpxX1yPZmd4Y8gAQm0bP3ZJRzRiUzrLIvmkxSeQ+6EV1h6Lx4IiXNL/R/X7s8qoa loZ76FODauhAa5N/MQXJa6Da7ft06MxGwyCavebSFnDK12jT0Tp68sLEdwTABA/RFO v9oo7LD2xKDduKzPgWZUVoNjCKRcOtkfNBLWGgOQ= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2A4893858CDB ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 2A4893858CDB ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1725444697; cv=none; b=duXQI7rn7Rx0yt8SUDqXJMJ4kMNqZJHAqfwf6sBbmX14kCZpe3DCx8O3CxsXnt5uFv9cmFJKsjk6drkZ6KwsFRAdzw07CdMAejTs2EcPj076uJkrJnISme53jGCjPogCFwkrfretmm+UzHLjTnL7c7Af4xnJmQqW3qLAxvVIE2A= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1725444697; c=relaxed/simple; bh=MPjPt7BwKo7vI3MRRG1C4Hbe3hKqWybKM65SV97+VPY=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=VOwro+LKQkF0PZGl7WYAcTl0inthqlDdXnqikAWdQe/8WYIi/CIYi4KFLd3stenhekardOvzR/09V2ZvsmAOfajHoBtzzCQ0qD9tEKgnkJrNGnjE8NZKuRrP3lAzz7i+nU87zY8EEp9ly8t5N0ztYgrIn4PXsTz5ExQrOsQLsbI= 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=1725444694; x=1726049494; h=content-transfer-encoding:cc: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=AO5poJd5RCq8DQNDTcKLO0+Usu6PoDpAjwTmQrU6bkE=; b=pAPSF13du/XWoWMNG6j4pogxQvJHSj6bWla5gRJ3MLX44O2zZ09Ci9IjiiP5Vbr0DI prVvUJ+iwP4fx6lo0CimqoPg2TM6vlZ0l1tzSfvEocx4fuELh7sTw82Qd5GdESHf16f6 /5/9CiADRKCXE715qtmy4T0uQLx7xaptRFuZ47ikP+Y5NcL4KyCJzplS2EeMtQ053JfU g098K4wwyzbfPpARelsgQU1XczVQ8stCRtZxnTJKTG3bzHpeAQKgYxg+wMV/yPnfason NuSYbnXClFLAIHvzFgc7wEMTaJNIUw6he5H3hJ1XfncP5enw8S64S2hngGJLWkZsVEaS aUSg== X-Gm-Message-State: AOJu0YyBNt9YGCLjiRHAUslu0NHtddfsJO/fmIbyFu0vi6qpQ9oS7yY2 AK6JC3KQl8tH9g8GWwVOS5g+M3fGJFNQW+tYh2ZoHgvIgKcEhHNjTAp5LTs91iz2iOOuY5XI/BM gWI5rEzT3LheRi/82M57OcZHy7Xc= X-Google-Smtp-Source: AGHT+IFwazMv45A4C+TUrspawtQX/rCJG6HJUPS965Euuir2N9Njebg3c226wFWQSKVhSpgzourMwl7KY0BvHDwyvxs= X-Received: by 2002:a5d:59a4:0:b0:368:75:2702 with SMTP id ffacd0b85a97d-374ecc6774bmr6417196f8f.13.1725444693535; Wed, 04 Sep 2024 03:11:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 4 Sep 2024 11:11:22 +0100 Message-ID: Subject: Re: sshd not working properly To: Jim McNamara Cc: "cygwin AT cygwin DOT com" X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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: Andy Wood via Cygwin Reply-To: Andy Wood Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 484AC0Ym2140163 Hi Jim, Many thanks for that. The recent posts in the archive seem to be about problems different to mine. However, googling the terms "cygwin" and "seteuid" eventually took me to this page: https://cygwin.com/pipermail/cygwin/2019-February/240238.html Running "passwd -R" for 'other_user', as suggested by the subject of the post, fixed the problems for me. It looks like sshd isn't handling a login failure properly. Andy. On Tue, Sep 3, 2024 at 7:57 PM Jim McNamara via Cygwin wrote: > > >>This looks like a bug. Can anyone help? Is there a work-around? > Hi Andy, > > There was some chatter the last week or 2 on someone trying to get ssh to work. At the archive mailing list, you can read and see if that answers any of it. > > I thought the gist of it is that a cipher is being swapped out or something. > > Please read archives at the mailing list while you are waiting for a reply for the past week or 2 msgs. > > Also, the other person said they found out information in the release notes for cygwin that were kind of recent. > > Please check out the 2 links i found for you below and read to the bottom of the second link to see if it helps at all! > > https://cygwin.com/pipermail/cygwin/ > https://cygwin.com/pipermail/cygwin-announce/2024-July/011846.html > > > thanks, > J. McNamara > > > > > Sent with Proton Mail secure email. > > -- > 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 -- 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