Re: sshd: fatal: seteuid XXX : No such device or address

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]

On Mar 14 16:53, Houder wrote:
> On Thu, 14 Mar 2019 12:39:30, XXXXX wrote:
> > Hello the list, 
> > 
> > Thanks for all the work and effort put into this.
> > Since two days i cannot login anymore (password less) with ssh into my
> > server
> > 
> > Server is : 
> > Microsoft Windows Server 2012 R2 Essentials / 6.3.9600 N/A version 9600
> > 
> > Cygwin was not up to date, but I have since updated it
> > CYGWIN_NT-6.3 [MACHINE NAME] 3.0.3(0.338/5/3) 2019-03-09 19:12 x86_64 Cygwin
> > 
> > I can login via password, it work and lets me in.
> > But if i tried with my keys, I get in the event viewer :
> > sshd: PID 3777: fatal: seteuid 1049076: No such device or address
> 
> Corinna,
> 
> As far as I know, seteuid() can either return EINVAL or EPERM in case of
> an error.
> 
> EPERM (=  1) "Operation not permitted"
> EINVAL(= 22) "Invalid argument"
> 
> "No such device or address" appears to correspond to ENXIO (=  6). Is it
> sshd, or is it Cygwin, that is confused here?

No confusion as such.  The underlying Windows function returns a NT
status code, which is converted to a Win32 error code by a Windows
function, and that Win32 error code is converted to a POSIX errno by
Cygwin.  There are much more NT status codes than Win32 error codes, and
there are much more Win32 error codses than POSIX errno values, so the
mapping is inevitably unsatisfying.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]