From: David Dombrowsky <6thstreetradio@gmail.com>
To: davek@6thstreetradio.org, cygwin@cygwin.com
Subject: Re: sshd error "seteuid: No such device or address"
Date: Wed, 13 Mar 2019 00:18:00 -0000 [thread overview]
Message-ID: <bb45b850-a1df-42f0-30b7-461e904fe1ca@gmail.com> (raw)
In-Reply-To: <20190312213051.GR3785@calimero.vinschen.de>
[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]
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 able to logon without the
> passwd -R method again.
>
> This is a side effect of changing how Cygwin switches the user
> context by default. See
>
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1
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.
For me, this is acceptable risk since this is a single user machine and
the administrators of the domain already know my domain password :)
--
David Dombrowsky, Software Engineer
davek@6thstreetradio.org | 518-374-3204
https://www.linkedin.com/in/david-dombrowsky-94334415
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2019-03-13 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:09 David Dombrowsky
2019-03-12 21:31 ` Corinna Vinschen
2019-03-13 0:18 ` David Dombrowsky [this message]
2019-03-13 0:54 ` Bill Stewart
2019-03-13 2:02 ` David Dombrowsky
2019-03-13 2:11 ` Bill Stewart
2019-03-13 18:32 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb45b850-a1df-42f0-30b7-461e904fe1ca@gmail.com \
--to=6thstreetradio@gmail.com \
--cc=cygwin@cygwin.com \
--cc=davek@6thstreetradio.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).