public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Cygwin List <cygwin@cygwin.com>
Subject: Re: ntsec: changing the everyone user
Date: Mon, 15 Sep 2003 17:14:00 -0000	[thread overview]
Message-ID: <20030915171438.GK9981@cygbert.vinschen.de> (raw)
In-Reply-To: <04ce01c37ba7$5b1e67a0$a500000a@chrismob>

On Mon, Sep 15, 2003 at 05:35:20PM +0100, Chris Rodgers wrote:
> OK. Here is an example of the way permissions leak out to "Everyone". I
> create a new file, with no permissions granted to "other". Cygwin shows this
> to have worked OK. Yet in actual fact there is an ACL there giving Everyone
> some access rights. I usually choose not to have "Everyone" authorised to do
> anything on my Windows NT/2000 boxes, using Authorised Users instead. This
> way, without a valid login, you cannot get any information, including
> usernames and ACLs.
> 
> How can I stop cygwin setting these ACLs?

Did you have a close look to the access rights granted to everyone?
Otherwise, just don't use ntsec.

Corinna

> [...]
>                 Everyone:(special access:)
>                          READ_CONTROL
>                          FILE_READ_EA
>                          FILE_READ_ATTRIBUTES

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

  reply	other threads:[~2003-09-15 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 11:58 Chris Rodgers
2003-09-15 14:56 ` Larry Hall
2003-09-15 16:35   ` Chris Rodgers
2003-09-15 17:14     ` Corinna Vinschen [this message]
2003-09-22 22:33       ` Chris Rodgers
2003-09-22 22:33         ` Larry Hall

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=20030915171438.GK9981@cygbert.vinschen.de \
    --to=corinna-cygwin@cygwin.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).