Re: SFU3.5 and getting permissions to work


Don't do mapping? You *have* to map at least one user or group, don't you, to determine who has access to the files. I guess you could map the Everyone group to the root user.

Cheers,

Clifff

BobMarley wrote: 
We don't do mapping.
i seem to remember never having to do it before...
I was wondering if this was a new security feature in 3.0 or 3.5

what i'd love to do is have the file created by the unix host, be
available as EVERYONE with full control.

any idea how i can do that?


On Fri, 08 Apr 2005 09:23:06 +1200, Enkidu <enkidu.com@xxxxxxxxxxxxxx>
wrote:


BobMarley wrote:

I have a unix server connecting to an NFS mount point on my
Windows Server. Whenever a file is written there by the unix server,
it typically comes across as having permissions only of SYSTEM and
read. So no one is ever able to access the file

How can i have it come across so that it is a file readable by
Windows users? I thought it did that by default in earlier versions,
but maybe 3.5 changed that?


We use SFU 3.0 and it a major pain in the ... neck! When you add a file or change permissions on the Unix it creates a new Windows ACL. This means that all users/groups with permissions on that directory and the files in it become inaccessible on the Windows for almost all users. The new acl seems to wipe all existing acls and since it is theoretically inherited (don't know why) all you see in the permissions is grey blank boxes which you can't change.

What we have to do periodically is take ownership of the directory and all sub-directories and files and set the permissions back again.

Though having said that, have you checked the mapping between Windows users and groups and Unix users and groups?




--

Barzoomian the Martian - http://barzoomian.blogspot.com
.

Relevant Pages

  • Re: SFU3.5 and getting permissions to work
    ... what i'd love to do is have the file created by the unix host, ... >> Windows Server. ... >> it typically comes across as having permissions only of SYSTEM and ... >between Windows users and groups and Unix users and groups? ...
    (microsoft.public.win2000.active_directory)
  • Re: ubuntu xp vmware cluster f...er...filesharing
    ... Unix and Windows NT/XP is dramatically different. ... of translating these permissions so that a Windows machine can store ... NT/XP acls or Unix acls and SUID, ... tarballs) on your Windows server. ...
    (Ubuntu)
  • Re: Unix Runnable format
    ... hand in a CD holding unix runnable format, rather then just do a simple ... I CD can't have unix permissions or links, so all files must be packaged ... What most windows users don't know at all is that unix will use rock ridge ... most linux users know that windows can't read rock ridge. ...
    (alt.os.linux)
  • Re: SFU3.5 and getting permissions to work
    ... You associate a Windows user with a Unix user (eg root). ... Whenever a file is written there by the unix server, it typically comes across as having permissions only of SYSTEM and read. ...
    (microsoft.public.win2000.active_directory)
  • Re: [Full-disclosure] Privilege escalation in McAfee VirusScanEnterprise 8.0i (patch 11) and CMA
    ... > On Windows 2000 operating systems the default permissions for the root ... Everyone/Full Control permissions on the installation volume are ... with those in MS02-064 are *NOT* susceptible to the attacks you describe. ... Your Windows 2000 system's default ACL ...
    (Full-Disclosure)
Loading