From: Andrey Repin <anrdaemon@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Cygwin AD integration home/shell changes
Date: Wed, 03 Dec 2014 07:35:00 -0000 [thread overview]
Message-ID: <946685207.20141203102637@yandex.ru> (raw)
In-Reply-To: <20141126205658.GA9157@calimero.vinschen.de>
Greetings, Corinna Vinschen!
> Here's what you get:
I finally realized, what was tingling me all this time.
The implicit fallback mechanics. I'd rather want to have explicit declaration
and a failure message in case something isn't right. Much easier to fix system
issues, when the system tell you about them.
Shouldn't be a big change, considering you already have all the facilities in
order to make it works.
> db_home:
> windows AD and SAM: Utilizes the setting of the homeDrive or
> homeDirectory attributes, or their SAM "Home folder"
> counterparts. The Windows path is converted to a
> POSIX path.
> cygwin AD only: Shortcut for the cygwinHome attribute from
> the predefined cygwinUser auxiliary class. POSIX path
> expected.
> unix AD only: Shortcut for the unixHomeDirectory attribute
> from the posixAccount auxiliary class. POSIX path
> expected.
> desc AD and SAM: Fetch the home="..."
> setting from the user's description attribute.
> POSIX path expected.
> @ad_attribute AD-only: Read AD attribute "ad_attribute" as POSIX
> path.
>
> However, I'm contemplating to allow a Windows path
> here, too. Does this make sense to you?
> /path POSIX path. Remember the wildcards.
> fallback If nothing works, the fallback is /home/$USERNAME
> (Windows username).
> db_shell:
> windows Ignored. Do you want CMD instead?
> cygwin AD-only: Shortcut for the cygwinShell attribute
> from the cygwinUser class. POSIX path.
> unix AD-only: Shortcut for the loginShell attribute
> from the posixAccount class. POSIX path.
> desc AD and SAM: Fetch the shell="" setting from the
> user's description attribute. POSIX path.
> @ad_attribute See above.
> /path See above.
> fallback If nothing works, the fallback is /bin/bash.
> db_gecos:
> windows AD and SAM: displayName attribute, or "Full Name"
> setting in SAM.
> cygwin AD-only: cygwinGecos attribute from cygwinUser class.
> unix AD-only: gecos attribute from posixAccount class.
> @ad_attribute Read AD attribute "ad_attribute" and prepend
> to pw_gecos.
> /path Skip the slash, prepend the reminder of the string
> to pw_gecos. Note that the wildcards are still
> evaluated.
> fallback If nothing works, the fallback is no fallback.
> Examples:
> db_home: cygwin desc
> The default. Try the cygwinHome attribute first. If it's empty,
> evalaute the description field and see if the home dir is set via
> the cygwin XML-style text. If that fails, fallback is /home/$USERNAME
> (Windows username).
> db_home: unix @msTSHomeDirectory /home/%u
> Try the unixHomeDirectory attribute first. Empty? Try the
> (otherwise unused) msTSHomeDirectory attribute. Empty? Fall back
> to /home/$USER (Cygwin username).
> db_gecos: @comment /Hallo%_%U
> Try the comment attribute. Empty? Fall back to the string
> "Hallo <Windows username>". Example passwd entry:
> corinna:*:1049577:1049701:Hallo
> corinna,U-MY_DOM\corinna,S-1-5-21-yada-yada:/home/corinna:/bin/bash
> Is this new stuff basically clear? Questions?
> Please give it a try.
> Thanks,
> Corinna
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 03.12.2014, <10:11>
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:[~2014-12-03 7:35 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 20:52 RFC: 1.7.33 problem with user's home directory Corinna Vinschen
2014-11-10 21:18 ` Achim Gratz
2014-11-10 21:39 ` Corinna Vinschen
2014-11-11 7:30 ` Achim Gratz
2014-11-11 0:50 ` Andrey Repin
2014-11-11 2:42 ` Andrew DeFaria
2014-11-11 6:35 ` Andrey Repin
2014-11-11 9:15 ` Frank Fesevur
2014-11-11 15:20 ` Andrey Repin
2014-11-11 1:39 ` Jeffrey Altman
2014-11-11 6:19 ` Warren Young
2014-11-11 9:33 ` Corinna Vinschen
2014-11-11 10:00 ` Corinna Vinschen
2014-11-11 13:52 ` Jeffrey Altman
2014-11-11 16:19 ` Corinna Vinschen
2014-11-11 4:26 ` Yaakov Selkowitz
2014-11-11 6:05 ` Warren Young
2014-11-11 6:50 ` Andrey Repin
2014-11-11 9:00 ` Marco Atzeri
2014-11-11 6:09 ` Warren Young
2014-11-11 10:18 ` Corinna Vinschen
2014-11-11 11:06 ` Achim Gratz
2014-11-11 11:14 ` Corinna Vinschen
2014-11-11 12:48 ` Habermann, David (D)
2014-11-12 16:27 ` Warren Young
2014-11-12 16:31 ` Warren Young
2014-11-12 17:55 ` Habermann, David (D)
2014-11-12 21:28 ` cyg Simple
2014-11-12 21:51 ` Habermann, David (D)
2014-11-13 9:06 ` Corinna Vinschen
2014-11-12 22:35 ` Andrey Repin
2014-11-11 16:45 ` Achim Gratz
2014-11-11 16:55 ` Corinna Vinschen
2014-11-26 21:16 ` Corinna Vinschen
2014-11-26 21:29 ` Cygwin AD schema and configuration extensions (was Re: RFC: 1.7.33 problem with user's home directory) Corinna Vinschen
2014-11-26 21:56 ` Achim Gratz
2014-11-27 9:36 ` Corinna Vinschen
2014-11-27 14:52 ` Corinna Vinschen
2014-11-27 19:23 ` Achim Gratz
2014-11-27 20:12 ` Corinna Vinschen
2014-11-28 2:21 ` Achim Gratz
2014-11-26 21:58 ` Habermann, David (D)
2014-11-26 23:15 ` Corinna Vinschen
2014-11-27 16:12 ` RFC: 1.7.33 problem with user's home directory Corinna Vinschen
2014-11-27 17:41 ` Corinna Vinschen
2014-11-28 12:48 ` Andrey Repin
2014-11-28 16:20 ` Corinna Vinschen
2014-11-28 17:04 ` Andrey Repin
2014-11-28 18:34 ` Corinna Vinschen
2014-11-29 9:36 ` Andrey Repin
2014-12-01 17:50 ` cyg Simple
2014-12-02 5:35 ` Andrey Repin
2014-12-03 14:05 ` cyg Simple
2014-12-03 20:20 ` Andrey Repin
2014-12-04 12:21 ` Linda Walsh
2014-12-04 13:47 ` Corinna Vinschen
2014-12-02 16:03 ` Corinna Vinschen
2014-11-28 16:17 ` Andrey Repin
2014-12-03 7:35 ` Andrey Repin [this message]
2014-12-03 9:16 ` Cygwin AD integration home/shell changes Corinna Vinschen
2014-12-03 13:50 ` Andrey Repin
2014-12-04 9:40 ` Corinna Vinschen
2014-12-05 5:20 ` Andrey Repin
2014-12-05 10:13 ` Corinna Vinschen
2014-12-05 20:20 ` Andrey Repin
2014-12-06 10:08 ` Corinna Vinschen
2014-12-04 15:49 ` RFC: 1.7.33 problem with user's home directory Corinna Vinschen
2014-12-05 5:35 ` Andrey Repin
2014-12-05 10:15 ` Corinna Vinschen
2014-12-05 21:20 ` Andrey Repin
2014-12-06 11:08 ` Corinna Vinschen
2014-12-10 20:52 ` cyg Simple
2014-12-10 22:50 ` Andrey Repin
2014-12-10 23:29 ` David Stacey
2014-11-11 11:09 ` Corinna Vinschen
2014-11-11 12:11 ` Bryan Berns
2014-11-11 12:31 ` Corinna Vinschen
2014-11-11 15:35 ` Andrey Repin
2014-11-11 16:57 ` Corinna Vinschen
2014-11-11 20:20 ` Andrey Repin
2014-11-12 10:30 ` Corinna Vinschen
2014-11-12 20:35 ` Andrey Repin
2014-11-13 9:07 ` Corinna Vinschen
2014-11-13 21:50 ` Andrey Repin
2014-11-14 10:32 ` Corinna Vinschen
2014-11-17 4:05 ` Andrey Repin
2014-11-12 16:45 ` Warren Young
2014-11-13 9:27 ` Corinna Vinschen
2014-11-13 22:05 ` Andrey Repin
2014-11-14 10:35 ` Corinna Vinschen
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=946685207.20141203102637@yandex.ru \
--to=anrdaemon@yandex.ru \
--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).