Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 16 Oct 2001 10:25:47 +0200 From: Corinna Vinschen To: cygwin Subject: Re: rsh: "Permission denied" on file creation. Cygwin 1.3.3 on W2 K Adv Srv SP2. Message-ID: <20011016102547.S1696@cygbert.vinschen.de> Mail-Followup-To: cygwin References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhje@novonordisk.com on Mon, Oct 15, 2001 at 06:40:11PM +0200 On Mon, Oct 15, 2001 at 06:40:11PM +0200, JHJE (Jan Holst Jensen) wrote: > OK. Now, from what I've gathered, there seems to be some dispute as to what > SYSTEM can do. But, since I can write to an existing file with an rsh > invocation, it would seem that enough privileges are set in this case. > > >Or, much easier, the process running under System account activates > >its SeRestorePrivilege and reads the file or activates its > >SeBackupPrivilege and writes the file using FILE_FLAG_BACKUP_SEMANTICS. > >System has both rights set by default. They are just not activated > >by default as it's given for most dangerous privileges in NT. > > Is it then a bug/oversight that rsh cannot create a file, or is it intended > (cryptic) behavior ? It's intended NT behaviour. No password on logon <-> no authentication on network shares. Corinna -- 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 Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/