From: Andrey Repin <anrdaemon@yandex.ru>
To: renaud.rolles@giraudbtp.com, cygwin@cygwin.com
Subject: Re: sshd: fatal: seteuid XXX : No such device or address
Date: Thu, 14 Mar 2019 15:07:00 -0000 [thread overview]
Message-ID: <1365721707.20190314175652@yandex.ru> (raw)
In-Reply-To: <018f01d4da73$97704ac0$c650e040$@giraudbtp.com>
Greetings, renaud.rolles@giraudbtp.com!
>> Please remove /etc/passwd and /etc/group files. They are no longer
>> necessary, unless you have some very special needs, and even then, they
>> only needed for that one or two accounts you need special treatment for.
> They dont exists.
Then my next guess is that you'll have to reestablish your trust with
`passwd -R`. There's not many places where and what can be "saved" :)
>> The main security concern is, why your Administrator user:
>> 1. have password, and
>> 2. is not disabled?
> Why would i disable Administrator, it's the only local account, the server
> isn't in any domain and without password it doesn't seem secure at all.
Create a different local account, with necessary password and permissions,
then reset password on local Administrator account and disable it.
As for why, Administrator is the only local account with super-user
permissions that is guaranteed to exist. Windows uses it in case something
gone REALLY wrong, such as AD database recovery procedures.
It is easy enough to enable a locked account with offline tools, if your system
gone into such disrepair, that you can no longer even boot it, and need a
LiveCD to login to local SAM environment.
But recovering a lost Administrator password is a nontrivial endeavor, and
chances to brind system into a working state without complete reinstall are
diminishing rather quick.
--
With best regards,
Andrey Repin
Thursday, March 14, 2019 17:49:16
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2019-03-14 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 11:39 renaud.rolles
2019-03-14 12:10 ` Corinna Vinschen
2019-03-14 13:26 ` renaud.rolles
2019-03-14 13:53 ` Corinna Vinschen
2019-03-14 14:03 ` renaud.rolles
2019-03-14 14:20 ` Andrey Repin
2019-03-14 14:24 ` David Dombrowsky
2019-03-14 14:27 ` Corinna Vinschen
2019-03-14 14:50 ` Andrey Repin
2019-03-14 14:38 ` renaud.rolles
2019-03-14 15:07 ` Andrey Repin [this message]
2019-03-14 15:29 ` renaud.rolles
2019-07-10 16:10 ` schleprock
2019-03-14 15:53 ` Houder
2019-03-14 17:29 ` Corinna Vinschen
2019-03-15 13:06 ` Houder
2019-03-15 13:42 ` Corinna Vinschen
2019-03-15 19:39 ` Houder
2019-03-15 20:41 ` Corinna Vinschen
2019-03-16 9:21 ` Houder
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=1365721707.20190314175652@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=renaud.rolles@giraudbtp.com \
/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).