Re: sshd error "seteuid: No such device or address"

2019-03-13 Thread Achim Gratz
David Dombrowsky writes: > If I'm reading this correctly, using the SYSTEM account will deny access > to user-level shares. Using the cyg_server account (or another service > account) will allow access, but requires a password stored in the > registry. That was already the case if you logged in a

Re: sshd error "seteuid: No such device or address"

2019-03-12 Thread Bill Stewart
On Tue, Mar 12, 2019 at 8:02 PM David Dombrowsky wrote: > > Surely you don't mean they have a plain-text copy of your password? > > If only I were kidding. Security through Oblivity :) (?!) There is no reason that anyone else should have your password. This means (among other things) that someo

Re: sshd error "seteuid: No such device or address"

2019-03-12 Thread David Dombrowsky
On 3/12/19 8:54 PM, Bill Stewart wrote: > On Tue, Mar 12, 2019 at 6:19 PM David Dombrowsky wrote: > >> For me, this is acceptable risk since this is a single user machine and >> the administrators of the domain already know my domain password :) > > I hope you really mean that they can _reset_ yo

Re: sshd error "seteuid: No such device or address"

2019-03-12 Thread Bill Stewart
On Tue, Mar 12, 2019 at 6:19 PM David Dombrowsky wrote: > For me, this is acceptable risk since this is a single user machine and > the administrators of the domain already know my domain password :) I hope you really mean that they can _reset_ your domain password if needed? Surely you don't me

Re: sshd error "seteuid: No such device or address"

2019-03-12 Thread David Dombrowsky
On 3/12/19 5:30 PM, Corinna Vinschen wrote: >> Was that the correct solution? Is that expected? This windows box is >> on a domain, so that might have something to do with it. > > Just switch the account sshd is running under from "cyg_server" to > SYSTEM (or "LocalSystem") and you should be abl

Re: sshd error "seteuid: No such device or address"

2019-03-12 Thread Corinna Vinschen
On Mar 12 17:09, David Dombrowsky wrote: > 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" b

sshd error "seteuid: No such device or address"

2019-03-12 Thread David Dombrowsky
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