delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/09/24/12:56:44

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <200409241851570191.073810B3@email.uni-linz.ac.at>
In-Reply-To: <e9686dd60409240739566dd279@mail.gmail.com>
References: <e9686dd604092311424a08a8d6 AT mail DOT gmail DOT com> <Pine DOT GSO DOT 4 DOT 61 DOT 0409231643310 DOT 2707 AT slinky DOT cs DOT nyu DOT edu> <20040923210113 DOT GP12802 AT cygbert DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 61 DOT 0409231718100 DOT 7682 AT slinky DOT cs DOT nyu DOT edu> <e9686dd60409231432258a067c AT mail DOT gmail DOT com> <Pine DOT GSO DOT 4 DOT 61 DOT 0409231817400 DOT 7682 AT slinky DOT cs DOT nyu DOT edu> <e9686dd60409240739566dd279 AT mail DOT gmail DOT com>
Date: Fri, 24 Sep 2004 18:51:57 +0200
Reply-To: cygwin AT cygwin DOT com
From: "Benjamin Lindner" <lindner AT flll DOT uni-linz DOT ac DOT at>
To: cygwin AT cygwin DOT com
Subject: Re: Inheriting parent ACLs?
X-Scanned-By: MIMEDefang 2.44
X-IsSubscribed: yes

On 24.09.2004 at 09:39 Gabe Rosenhouse wrote:
>Thanks.
>Is there something I can read that contrasts the functionality
>implications of ntsec vs nontsec? 
>http://cygwin.com/cygwin-ug-net/ntsec.html doesn't go into details on
>the differences between the two settings.
>One question specifically is, under nontsec, will domain users will
>still be able to login via SSH and be recognized as members of their
>domain groups?
>

I am no expert on cygwin internal details so I won't guess on 
the functionality implications.

But I have a system with NT4Server, the sshd daemon running with the
environment variable set to CYGWIN=nontsec binmode tty, and it works.
Clients can log in via ssh and are correctly recognized in the domain.
and because the sshd daemon has CYGWIN=nontsec, all bash logon shells
started via ssh also inherit the environment setting 'nontsec' and
everything works fine.
(mind, I just see that it works, I cannot give the exact reasons, it 
just works)

If you do not want your sshd daemon running with 'nontsec', but with 
'ntsec' but still require all login shells to have the environment
variable set to 'nontsec' it gets a bit tricky.
I experimented a bit, but take everything with the usual grain of salt.

There is a setting in sshd_daemon called 'PermitUserEnvironment' which
is set to 'no' per default. check out the man pages on this.

You can also edit one of the startup scripts which are read by bash at 
program start (I suppose other shells have something equivalent).
see man bash for a list of those files. one of them is /etc/profile IIRC.

HTH
benjamin


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019