Re: mkpasswd: option to force the 'primary' domain?

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

On Mar 20 11:58, Tim Magee wrote:
> Now then,
> 
> Since Cygwin 1.7.34 dropped, mkpasswd has been problematic for us.  Our
> problem is with the way user names pulled from outside the primary domain
> get decorated.  My question is: will there ever be a way to tell
> mkpasswd/mkgroup "make <some non-primary domain> the one whose users get
> undecorated names"?
> 
> We have Windows machines in one AD domain, and all our users in a different
> AD domain.  According to the 'POSIX accounts, permissions and security'
> page, the machine's domain is considered the primary one. "mkpasswd -d" will
> generate undecorated names for that domain, and decorated names for any
> other named domain.
> 
> We use SSH-based tools a great deal here, and we use Cygwin to make our
> Windows machines behave like members of our POSIX machine community, so
> having our usernames appear the same on all machines is very desirable.
> 
> I think I can recreate the pre-1.74 behaviour with a little seddery, but I'd
> bet folding money that my seddery isn't future-proof.  So, are
> mkpasswd/mkgroup ever likely to get an option to force the "undecorated
> users" domain?

I'm not planning this.  The idea is that mkpasswd/mkgroup create account
names compatible with the "db"-based accounts and everyhing else is left
to post-creation manipulation.

Having said that, the new account handling is supposed to be stable on
the user level for quite some time, ideally at least as many years as
the old /etc/passwd&/etc/group-only based code.  Therefore using some
sed script to filter the output of mkpasswd/mkgroup if you dislike the
new account handling is the way to go.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]