Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <37B7F632.C179DBD4@vinschen.de> Date: Mon, 16 Aug 1999 13:29:54 +0200 From: Corinna Vinschen X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: de,en MIME-Version: 1.0 To: igoresha AT iwmail DOT com CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: post b20.1: How to disable umask and access UNC path References: <9908160610167W DOT 20877 AT webb1 DOT iname DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit igoresha AT iwmail DOT com wrote: > [...] > And in any case does the fact that new code does not work accross network should be considered as a bug? > I.e. if I make a new file of a different computer it > should be created under the ownership of the account under which I connected to that computer and not the account under which I logged in locally. This is a illegal implication. You have accessed the other computer via smb. This has NOTHING to do with NT security. The correct behaviour is to use the SID under which you are logged into the NT network and in your example it's the SID of your local login. The resulting `Unknown' account on the other computer is a logical consequence because it has no access to your local SAM. Moreover, what you do is possible but not correct in a NT domain. You should login as domain user when you work in a domain. If you use your local login you are mixing two worlds and you have to live with the results. Regards, Corinna -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com