www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1999/08/16/09:14:25

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>,
<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID: <37B7DDB3.21672361@vinschen.de>
Date: Mon, 16 Aug 1999 11:45:23 +0200
From: Corinna Vinschen <corinna AT vinschen DOT de>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>
CC: Chris Faylor <cgf AT cygnus DOT com>
Subject: ntsec documentation (including patch)

This is a multi-part message in MIME format.
--------------F8FF7C0068D78CB6BC61C73D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

While working at nt security I felt that the ntsec documentation
isn't as understandable as I want. So I have rewritten some parts
and described something in a more detailed manner. I would like
to here your opinion. This mail contains a simple text version
for everyone and the patch relative to the previous version as
attachment for Chris.

One additional point: Would it be a good idea, to publish this
text in the cygwin users group? Michael Hirmke inspired that
because the ntsec setting may result in some surprises for the
users when they don't have a correct /etc/passwd and /etc/group
file.

Ok, the text follows.

Regards,
Corinna

--------- SNIP ----------

NTSEC Documentation
===================

The design goal of the ntsec patch was to get a more UNIX like
permission structure based upon the security features of Windows NT.
To describe the changes, I will give a short overview of NT security in
chapter one.
Chapter two discusses the changes in ntsec related to privileges on
processes.
Chapter three shows the UNIX like setting of file permissions.

The setting of UNIX like object permissions is controlled by the new
CYGWIN variable setting (no)ntsec.

On NT ntsec is now turned on by default.


1. NT security
--------------

The NT security allows a process to allow or deny access of different
kind to `objects'. `Objects' are files, processes, threads, semaphores,
etc.

The main data structure of NT security is the `security descriptor'
(SD) structure. It explains the permissions, that are granted (or
denied) to an object and contains information, that is related to so
called `security identifiers' (SID).

An SID is a unique identifier for users, groups and domains. 
SIDs are comparable to UNIX UIDs and GIDs, but are more complicated
because they are unique across networks. Example:

SID of a system `foo':

  S-1-5-21-165875785-1005667432-441284377

SID of a user `johndoe' of the system `foo':

  S-1-5-21-165875785-1005667432-441284377-1023

The above example shows the convention for printing SIDs. The leading
`S' should show that it is a SID. The next number is a version number
which is always 1. The next number is the so called `top-level
authority' that identifies the source that issued the SID.

While each system in a NT network has it's own SID, the situation
is modified in NT domains: The SID of the domain controller is the
base SID for each domain user. If an NT user has one account as domain
user and another account on his local machine, this accounts are under
any circumstances DIFFERENT, regardless of the usage of the same user
name and password! 

SID of a domain `bar':

  S-1-5-21-186985262-1144665072-740312968

SID of a user `johndoe' in the domain `bar':

  S-1-5-21-186985262-1144665072-740312968-1207

The last part of the SID, the so called `relative identifier' (RID),
is used as UID and/or GID under cygwin. As the name and the above
example implies, this id is unique only relative to one system or
domain.

Note, that it's possible, that an user has the same RID on two
different systems. The resulting SIDs are nevertheless different, so
the SIDs are representing different users in an NT network.

There is a big difference between UNIX IDs and NT SIDs, the existence
of the so called `well known groups'. For example UNIX has no GID for
the group of `all users'. NT has an SID for them, called `Everyone' in
the English versions. The SIDs of well-known groups are not unique
across an NT network but their meanings are unmistakable.
Examples of well-known groups:

everyone                        S-1-1-0
creator/owner                   S-1-3-0
batch process (via `at')        S-1-5-3
authenticated users             S-1-5-11
system                          S-1-5-18

The last important group of SIDs are the `predefined groups'. This
groups are used mainly on systems outside of domains to simplify the 
administration of user permissions. The corresponding SIDs are not
unique across the network so they are interpreted only locally:

administrators                  S-1-5-32-544
users                           S-1-5-32-545
guests                          S-1-5-32-546
...

Now, how are permissions given to objects? A process may assign an SD
to the object. The SD of an object consists of three parts:

- the SID of the owner 
- the SID of the group 
- a list of SIDs with their permissions, called `access control list'
  (ACL) 

UNIX is able to create three different permissions, the permissions
for the owner, for the group and for the world. In contrast the ACL
has a potentially infinite number of members. Every member is a so
called `access control element' (ACE). An ACE contains three parts:

- the type of the ACE 
- permissions, described with a DWORD 
- the SID, for which the above mentioned permissions are set 

The two important types of ACEs are the `access allowed ACE' and the
`access denied ACE'. The ntsec patch only uses `access allowed ACEs'.

The possible permissions on objects are more complicated than in
UNIX. For example, the permission to delete an object is different
from the write permission.

With the aforementioned method NT is able to grant or revoke
permissions to objects in a far more specific way. But what about
cygwin? In a POSIX environment it would be fine to have the security
behaviour of a POSIX system. The NT security model is able to reproduce
the POSIX model. The ntsec patch tries to do this in cygwin.

The creation of explicit object security is a bit complicated, so
typically only two simple variations are used:

- default permissions, computed by the operating system 
- each permission to everyone 

For parameters to functions that create or open securable objects
another data structure is used, the `security attributes' (SA). This
structure contains an SD and a flag, that specifies whether the
returned handle to the created or opened object is inherited to child
processes or not. This property is not important for the ntsec patch
description, so in this document SDs and SAs are more or less identical.


2. Process privileges
---------------------

Any process started under control of cygwin has a semaphore attached
to it, that is used for signaling purposes. The creation of this
semaphore can be found in sigproc.cc, function `getsem'. The first
parameter to the function call `CreateSemaphore' is an SA. Without
ntsec patch this SA assigns default security to the semaphore. There
is a simple disadvantage: Only the owner of the process may send
signals to it. Or, in other words, if the owner of the process is not
a member of the administrators' group, no administrator may kill the
process! This is especially annoying, if processes are started via
service manager.

The ntsec patch now assigns an SA to the process control semaphore,
that has each permission set for the user of the process, for the
administrators' group and for `system', which is a synonym for the
operating system itself. The creation of this SA is done by the
function `sec_user', that can be found in `shared.cc'. Each member of
the administrators' group is now allowed to send signals to any process
created in cygwin, regardless of the process owner.

Moreover, each process now has the appropriate security settings, when
it is started via `CreateProcess'. You will find this in function
`spawn_guts' in module `spawn.cc'. The security settings for starting a
process in another user context have to add the sid of the new user,
too. In the case of the `CreateProcessAsUser' call, sec_user creates
an SA with an additional entry for the sid of the new user.


3. File permissions
-------------------

If ntsec is turned on, file permissions are set as in UNIX. An SD is
assigned to the file containing the owner and group and ACEs for the
owner, the group and `Everyone'. If the group of the file is not the
administrators' group, the administrators' group gets the permissions
to read the permissions (yes, this is an own permission flag
:-)) and to take the ownership on this file.
If the file's group is the administrators group itself, this behaviour
is modified to support the typical behaviour of NT better:
As you know, if one is member of admin group, all her files are owned
by the group instead of by her. This is not the case with ntsec but the
other admins should have easier access to the administrative files.
So in this case the admin group gets additionally the permissions to
write permissions and to write extended attributes, also in the case
where group permissions are set to 0.

The complete settings of UNIX like permissions can be found in the
file `security.cc'. The two functions `get_nt_attribute' and
`set_nt_attribute' are the main code. The reading and writing of the
SDs is done by the functions `ReadSD' and `WriteSD'. They are using
the Backup API functions `BackupRead' and `BackupWrite', that have the
advantage not to crash, if they are used on non NTFS file systems!
These crashes are the default behavior of the security API, if it's
used on, e.g., FAT or SAMBA file systems :-(

Unfortunately, the settings of NT file security are only available
on NTFS. SAMBA doesn't support them.

If you are creating a file `foo' outside of cygwin, you will see
something like the following on ls -ln:

If your login is member of the administrators' group:

  rwxrwxrwx 1  544  513  ... foo

if not:

  rwxrwxrwx 1  1000  513  ... foo

Note the user and group IDs. 544 is the UID of the administrators'
group. This is a `feature' :-P of WinNT. If one is a member of the
administrators' group, every file, that he has created is owned by the
administrators' group, instead by him.

The second example shows the UID of the first user, that has been
created with NT's the user administration tool. The users and groups
are sequentially numbered, starting with 1000. Users and groups are
using the same numbering scheme, so a user and a group don't share the
same ID.

In both examples the GID 513 is of special interest. This GID is a
well known group with different naming in local systems and domains.
Outside of domains the group is named 'None' (`Kein' in German, `Aucun'
in French, etc.), in domains it is named 'Domain Users'. 
Unfortunately, the group `None' is never shown in the user admin tool
outside of domains! This is very confusing but it seems that this has
no negativ influences.

To work correctly the ntsec patch depends on reasoned files
/etc/passwd/ and /etc/group.  The names and the IDs must correspond to
the appropriate NT IDs! The IDs used in cygwin are the RID of the
NT SID, as aforementioned.
An SID of e.g. the user `corinna' on my NT workstation:

  S-1-5-21-165875785-1005667432-441284377-1000

Note the last number: It's the RID 1000, the cygwin's UID.

Unfortunately, workstations and servers outside of domains are not
able to set primary groups! In these cases, where there is no
correlation of users to primary groups, NT returns 513 (None) as
primary group, regardless of the membership to regular groups of
these users.

when using mkpasswd  -l -g on such systems, you have to change the
primary group by hand if `None' as primary group is not what you want
(and I'm sure, it's not what you want!)

To get help in creating correct passwd and group files, look at
the following examples, that are part of my files. With the exception
of my personal user entry, all entries are well known entries. For a
better understanding, the names are translated to the equivalents of
the English NT version:

/etc/passwd:

everyone:*:0:0:::
system:*:18:18:::
administrator::500:544::/home/root:/bin/bash
guest:*:501:546:::
administrators:*:544:544::/home/root:
corinna::1000:547:Corinna Vinschen:/home/corinna:/bin/tcsh

/etc/group:

everyone::0:
system::18:
none::513:
administrators::544:
users::545:
guests::546:
powerusers::547:

Groups may be mentioned in the passwd file, too. This has two
advantages:

- Because NT assigns them to files as owners, a ls -l is often better
  readable. 
- Moreover it's possible to assigned them to files as owners with chown. 

The group `system' is the aforementioned synonym for the operating
system itself and is normally the owner of processes, that are started
through service manager. The same is true for files, that are created
by processes, which are started through service manager.
--------------F8FF7C0068D78CB6BC61C73D
Content-Type: application/octet-stream;
 name="ntsec.sgml-patch.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="ntsec.sgml-patch.bz2"

QlpoOTFBWSZTWU+Xa2QABV//gAQxhYBw7//3/6ve4P////BgD46GqH2XbidqddwW5323bUaY
UhbGpQkUlAqS165WZqowlBCZEYEnqnkyaNASekNPUGgZAab0U0aNA0BNGkmKj0yJp6jahpkD
TQAAAAABwDCMJpiGAQDIAYRpkyYRgIaCTUhATQmpqnptKb1Mp6mD0U0bU00A0AAAAySQAGgA
AAAAGgAAAACREECZT0TQNBNJHpNHqHqAyMTIA0DTJPV7RuAIW5u/vVk8VAbPk4a/f+nl/X70
h7dMJfz7nIXyl0dHhv0BgeXl2D0eWCd+Pmz+A0MjtVMfCpRosVKMdUtTx1cdmiWetds59+2q
+zZo2LQzsh5pd8jfiGiSkxdFLq4cfdfHKMND6Pl2XWLl9GXwmB2iJPSyDiIcLjzR6nJb6lSa
XhnFUaSdHD0735ofSiSPh/fdwlHl2d2drdmRkTWeLDqiJhitOs7uafxsKVsWG3thfMiR4qn8
E0O9c/RGesosm4zDsEyCIHYtpBVSFbrGhA8ERLII3hsWTo0UxC2qmSgO2KYEsq7x00LTvLpY
F8ao1Goq6hix6VMYmcsOZlJiFaGDGDFUqw3JQ2QPaHDFCbVjKtlpRmWDscnX3XQBdBF0YlY4
tXPdYQIp09ddqkEvUdf9UhNlWCjrTB4YY6O+FlByvcS8yvYZno/yHJpqxuoqOaRS+9kZVYVs
M0seGibPislkae1x3g2VjkhjC9xrT8BcrCM7LFS9NWxyOUy5hnWi4WMUuY0nHTTKppsR3xhD
08eumJbjfDNje3bFGMM9pwVeJGjxZvu8FxjvnGjmzN69sHiTsIG5kUtztViYmRnK4qOQONWO
hNdFQZ0DMqBxZsEyWNnLtsJmoOyzYUI13lVU2Ncn02Wor26Y8eF76VwYWoogiAeR2HQl0IQ0
KIiI+NqPk+/+D5r6mzztY4rlyrgqjt0begMOeKEFDPKmyRAdqalEmW/SzhsLCV16MLHp0J0e
gj7uiTBcCSRFLxatpEdCyokzPo6Vx2b8eqeRXokQnYQXNS9Wk21VFFx3YXStyu01i1W6pXkg
qWgzI3SxisyUdB12FBSvCNNSmGqqZdYEtbWkrVVp3NDBroNRnqisGujmhpWqswaEVCha04Xc
lCCHlqpm0B7g6qiCWhA2s3wPqjALWqCzYJJKJMI4ODDWWmZw86x4YwUqDfY7Y2N3cr00J5mU
NtMIGPfqO+l9jLZXfUlMzQSoWkthy51bjDPApdZU6hr04v+JcOpOY4ZKcqe6OJwx58MFZ+TV
jE+MM1YuKA9tEFvNv6t0l5xW3gh1ClERUQQLp4c2k5a5GeMnTn/Vax6buh+TOObQHYtj6SOm
+8q3jxSKjU7D0nh4fJ6HVfAXt4fF4+6NtNz7sJy98fVXB77TKN6GFNMvKkGFtlATsW0hBXRV
IMwKtvVu2HZrS/sIVbtko7ZNzwd66cGZ0KdKRBvKDrjmjPisQFOK9+Q014Tnw6aDOs0R0EEe
w6F/oVJ7SUpaHTaQAlgeDNfwnsORCbGL1ftPbRez1PoOreMODv0hmFtCEMFagv2Rv+UirGht
WZqtTWfJ6EayENPMrfcd/cYi9xJijHeI5bGY7IzWt5yjDE0UqxCbdqYxmVWcyuSrgqEFlyxs
rJGpvlQxqs1mrrLYtfIqSqmiiVoWMMa2KmLhxcMUE5SUsdUgCxWKRMCpVgzpQnaBUgTiVY8A
XDY2347dS0sws3Tr87PNuDmtDl62kdPs3iOp4ov11URixOxmKL8HHO8vBB0cWChjVVEGqoEs
ew9v0z6fMivpqSl8e+3y3q6FCqIoyCRkEEKjIw7JmWSRJFvpJFVg2gsy3Xwgl0S8J1BLSIEX
D5SllBqPI4hjqsWjBBRAVkM/lKlkgY/hv4fv1Nb4z+svIf11/l/blSoFlpgVaQ1EANsKEH7f
sChm+TcQc2dWxxJtmF5QVUEgqeKpkTg6jLKbbUrnUnbye8r48fv8ZocfHyhzEScmHYGUgUkP
PAidmIsVIoWaYubIb9CAh+YRHyfUQFmYjMGkL7Rpe8aVz8wEn3kt+321J4zP6LG1woWUryZZ
mp1z/ppApjZRihbGnDWVIYx0YoKXmci4xpHzgGtENosZQkiBf31lUNThe5U+0+YQl/UlC4tI
zaKGSHeSjbaV9kaFFY4osI48iiw5GCxZNkxBy/yi1tqpePAkyF3jXi5giXFnliSSSEAFF9gf
8Z8q5NsoxoNUaM3TRtF3JckdkoaICfowR1mFoV0YtNpYYl2MqWjwflncr9S/yukgHYYcRDtv
CbzYhyQ8J060WkONYFTJIkViKCj6EK6Ua0VLF6pbn27WViIapPPbMSZaCWhWGiJeMfooOacT
PG2xreQ5Z5CQG2b4Bzeb9pKTJ9DIvckurHlRi5AWGU42lXdAmFDCPJQiYiGlcmTB1qlUYoME
NHSx0hr8NtsqEOrKRGGryaGS7d3vtc9TmUUbYOFdLxeKDGs6K5GHXe9gwudRIlcGXUp1UulI
QVEvPy/8qOiIhQkXxx0yCKBWp2wUckD3cFCIUYzPFz97uHfAjmMuZbI+0167BDxWKMxFG01J
tNSgchzEXpIjIIp1EHE1x3KLZq1c2jTTA7OuuA3a8xjvAb4oWXTC2uWMc3cc787mY4vmlsqM
ORkhbBH4IkG9REB5JOdHQYdCPqIOhZdO9wpIudp+siXc7Tdb4d41W40MaRHW8MfZzPIrq+HN
YA+tGg1573k3zWa9WMIXIqcjkdzSXxvg0GgwJTSHJ4VSqBzIIAyEaGhArMzH7U0j1LQ5Wo0b
qyUwPjMwvZrG7c74Zy0kN2eZCqI+7vQcvDuggY2MMhp4IJEM0RAL5xURBYLAVQikVUViMkUF
ihMJH11umSOKux+rK2hgqSMyex6y+DDVnK9CY8ShYnvbOngY2GNDRylbZFZRfK54yG0L+Ocr
w0OSBzYHY3z5vKaNkKFEMFVFPitQFFu8uStPk3rOV06LNx2NeOL9yoa8s5HAykC2aXwaLFYD
FhpDYvNScd19FI9KKCKRpUkpIUnU04AtavKprJvjsoOC8LBsLegVVL9QKiO6NMkvMlHLxZkH
q3RFw51DQbT71ENUZFmGHad+SMQ8yeDtO0BI3BEVKsrATLaF4LLiZ37it2YhfqY8x61G+nPS
VUoYdVQ2xN5850Opl5zCdarYKQ9SQ13IosDvneS5ztjlLobkpCyDMk33UDAsBnXiiyWAZNQY
GTEoUDZYW2Je16UGGDybDPxh4YyT40MO6F752IxyFjVFFTIUsVLXVFKMUViq2Khe3pMFJGrw
PewiNSnlrUGlkEGLCIQjEdmlKznzLQgtlETvOo8h2ShHaxXXzBUgQafKQLZtwSpMClUZh50h
iJ7CZBhZFjFTO9iBQ1BQdCCQIaIHSyPrGHi0q1v2T1bdngdjIYMIiIIAI/BYMg9X4+CySUeI
MKJdrSQe8ws352/eMS09yF2oxy9IlNMbYaXlHxHSq+BDeVSuRYJQQB18F1rZ2IXf8JK/ojFy
Iuu727qh9JPAdRfka1tVGCNhSGygqg7eS+SdWdZ9w8NTRQkluHPAMT2F8vGI0c2hFCBvtYqT
4ewgbjDryrQkntRkh6DaWZplONC4D7Dse7USLj5gy5oFz1y68yyNPSAhhkYgdSDBQ5mkBgkp
CrWLFhWMiIiIbCSs6liEnhQfO1Jzz00ziiIZDAuNmBZC2S5P513o2L62oIsq9UGRlh6DFJR4
xcpE/riDZ0sRkuAiXMJFBsCZF/BjTCx1QrrXdJLDWCqIIyHOgUZTKCtIwbUG1a9x6ehUsHOU
1+zXZSuAydDsCrBmOwJYlcoJ51dYQZLcIX0Dm7Jj3a24OpUzpKukc6shuhTZRhSdQiC7y3HF
sblaguiMDFXQCMoyrTBqRWjGtDwCb65dMGmNkUuutr4HA8Z1dnNsvuZfpcsrljDyMzl3I9fV
DC64t1awBW8rF1KlNFga9LKDB0QHvGJjUZrJwj9KOZHMYqDMUWlSZmMrlMFeuNhgZtciqOPf
8NiKRYCZTZA1mwpJywRzDPokVSKK0ayTWAkZ8TDVgYXrCcB6AfC1KTGxOWgiGURBipnYzNig
UTSaDGLyDDpaENDFgoaVgrg2sbztqpCzWGqCXEG4YGsMiaRlnJu4VUl5NgQ8nWWDMwlQ0dQk
7khFkkNUOeAoN2SWZmBw5a04yDhJRni1pJHBdp0JRhYMM0jbpAmwOehgTlyk60VFWter0cBO
UvDPKSxkGU2usLkoxTmbo1qvE+8XDkR6SXXs1nqS2DMOzURggVlBhLzEg3M0J3s+pihSGh4+
0mRxsfhT/fMr2bxUoQ6PfnWhEPgEsfuI+F6YIfLBEDOznz7ufTRLkgw8pFAjRtgYYujBqTMN
mIbSp2HGJbw1pxOyxBEBRUcHbSVLQ+s05IL64qioJYiG5/xdyRThQkE+Xa2Q
--------------F8FF7C0068D78CB6BC61C73D--

- Raw text -


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