From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: ssh login no longer allowed by local accounts other than main administrator account after taking machine off domain
Date: Wed, 07 Aug 2013 16:22:00 -0000 [thread overview]
Message-ID: <52027450.7000906@etr-usa.com> (raw)
In-Reply-To: <CABSJGg3HywZZrXNfQHmivJOH0GrySZSBxA95XyjPmcngF6EHFA@mail.gmail.com>
On 8/6/2013 16:50, Yuki Ishibashi wrote:
>
> a) what are the standard permissions *supposed* to be on everything on
> the cygwin terminal-side (i.e. 'ls -l /etc/*', etc),
Unless you existing Cygwin installation is complex, it's probably
simplest to just rename c:\cygwin to c:\oldcygwin, reinstall, copy /home
over [*], and manually merge any configuration files in /etc. The copy
would fix the permissions on the user data, and the reinstall will fix
everything else.
I know "reinstall" is a way of giving up, but reinstalling Cygwin isn't
nearly as bad as reinstalling a complete OS. It should actually be
easier than reinstalling some *applications*, since everything's nice
and collected under c:\cygwin. You don't have to go digging under
%USER%\AppData and in the registry to find things, as when attempting a
clean reinstall of some other apps.
[*] Do a pure file-data-only copy. Don't use cp -p, or tar/cpio, or
rsync -a. You want the copied files to end up owned by the one who did
the copy. If multiple users own files under /home, do each section of
/home separately, as that user.
> d) Do i need to re-sync the mkpasswd -l with /etc/passwd and mkgroup
> -l with /etc/group ? I had previously appended the newly created local
> accounts (with associated SSIDs) to /etc/passwd using something like
> "mkpasswd -l | grep newusername >> etc/passwd" (and something similar
> for the /etc/group)
I would think that when switching between domains and local users -- or
vice versa for that matter -- you'd want to completely regenerate this
file. Then, *maybe*, copy some entries over selectively by hand.
--
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:[~2013-08-07 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 22:51 Yuki Ishibashi
2013-08-07 4:00 ` Larry Hall (Cygwin)
2013-08-07 16:22 ` Warren Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-07 16:55 Yuki Ishibashi
2013-08-07 17:26 ` Larry Hall (Cygwin)
2013-08-02 19:13 Yuki Ishibashi
2013-08-03 11:16 ` Linda Walsh
2013-08-05 1:31 ` Larry Hall (Cygwin)
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=52027450.7000906@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin@cygwin.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).