From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50433 invoked by alias); 12 Mar 2019 21:09:57 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 50418 invoked by uid 89); 12 Mar 2019 21:09:57 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=sudden, HX-Google-DKIM-Signature:reply-to, Senior, ssh X-HELO: mail-ot1-f68.google.com Received: from mail-ot1-f68.google.com (HELO mail-ot1-f68.google.com) (209.85.210.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 12 Mar 2019 21:09:56 +0000 Received: by mail-ot1-f68.google.com with SMTP id q24so3892492otk.0 for ; Tue, 12 Mar 2019 14:09:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=6kciy4MYnfohXUzQELOhQvG8w/OI3Z/wgIyTIHqVY24=; b=NDJaDj5q9NmN5ngbQerYhch1ikOIwTH5giYUg11PgaCTKYHyMymX7frQ1+8p0k8O1r /cUk995fpPpPgmmRQkZFqOiPdeJEvNF/iBds9wSy+atmpLb+XZ0kPPVzSbkJLiMXBfBt 2HoCKdVd8iZV2JUqbOpB3x7OkIyrzXOYsttOD+zzaJSmAy+2lt/DA1BsEPHHqUXE3BiZ Ti5YUNXoK6p3Y9blK1E1ddJDld46PxBOaVNpmv5F4MJDHSKuU7G+wJQO7VSgXkFA0rbC 5/I5orCoCVOv39GJK/Vj85YgFn9BKCnNLE8+qZTv9jbf9768bGY2pJeoMJeJSVFbzXTd gCHw== MIME-Version: 1.0 Reply-To: davek@6thstreetradio.org From: David Dombrowsky <6thstreetradio@gmail.com> Date: Tue, 12 Mar 2019 21:09:00 -0000 Message-ID: Subject: sshd error "seteuid: No such device or address" To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00316.txt.bz2 I managed to solve this problem, but I'd love some confirmation that I solved it the right way. After updating cygwin and rebooting, all of a sudden I couldn't ssh into my windows box. The remote gave the usual "connection closed by port 22" before anything happened. Running in debug mode from an admin shell didn't yield anything, but looking in the windows application logs, I saw: sshd: PID 2588: fatal: seteuid 1056480: No such device or address The google suggested that the error was pty related, but it was not. By accident, I noticed that I could log in from an account that I hadn't set up public key auth, using my password. So I forced ssh to prompt for my password and viola! I got in just fine. On the server, I started another admin shell and did `passwd -R my.username` and input my password. That was the key. I can now log in using public key auth as I could a few hours ago. Was that the correct solution? Is that expected? This windows box is on a domain, so that might have something to do with it. -- David Dombrowsky, Senior Software Engineer email: davek@6thstreetradio.org Cell: 518-374-3204 https://www.linkedin.com/in/david-dombrowsky-94334415 http://6thstreetradio.org/ -- 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