public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Maayan Apelboim <Maayan.Apelboim@clarizen.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: getent doesn't show all domain users
Date: Tue, 28 May 2019 08:36:00 -0000	[thread overview]
Message-ID: <AM6PR07MB5334AC0D9083A5425E6CA390951E0@AM6PR07MB5334.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <3a2c51fe-894d-8959-70b9-22a9d8f980aa@SystematicSw.ab.ca>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1585 bytes --]

Systems may have tens to hundreds of local user accounts, and domains may have hundreds to hundreds of thousands of user accounts.
The system probably caches only active users, and getent enumerates those if no /etc/passwd file exists, as it was designed to enumerate only a few entries from local files.
As it is, getent will not even enumerate hosts from the local hosts files or resolver.

It appears that mkpasswd enumerates all local and system accounts in the Security Accounts Manager file at $SYSTEMROOT/System32/config/SAM loaded into /proc/registry/HKEY_LOCAL_MACHINE/SAM/, so it probably does the same for domain accounts from Active Directory Domain Service.

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.

----

Ok, I understand why it won't display all users, but even when I query for this specific user that exists in the domain - it returns nothing.
It only works when I have /etc/passwd file in place (generated by mkpasswd -d), but I was told in a previous thread that I should not use mkpasswd -d anymore, and use getent instead.
Is there something I need to do with getent to get access for all my domain users?
Should I keep my previous passwd file generated by mkpasswd -d?

Thanks
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-05-28  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27  9:15 Maayan Apelboim
2019-05-27 15:59 ` Brian Inglis
2019-05-28  8:36   ` Maayan Apelboim [this message]
2019-05-28 15:15     ` Brian Inglis
2019-05-29  9:16       ` Maayan Apelboim
2019-05-29 13:25         ` Brian Inglis
2019-05-30 22:05         ` Andrey Repin
2019-06-03 11:14   ` Corinna Vinschen
2019-06-03 14:52     ` Jose Isaias Cabrera

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=AM6PR07MB5334AC0D9083A5425E6CA390951E0@AM6PR07MB5334.eurprd07.prod.outlook.com \
    --to=maayan.apelboim@clarizen.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).