sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-22 13:34:15 +03:00
Code
31de52ed2e
samba-mirror/source4/ntvfs
History
Andrew Bartlett 31de52ed2e s4-ntvfs: Remove untested ntvfs_cifsposix backend 
It had a note:

WARNING: All file access is done as user root!!!
         Only use this module for testing, with only test data!!!

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Gary Lockyer <gary@catalyst.net.nz>

Autobuild-User(master): Gary Lockyer <gary@samba.org>
Autobuild-Date(master): Wed May 22 07:15:43 UTC 2019 on sn-devel-184
2019-05-22 07:15:43 +00:00
..
cifs s4:libcli: allow passing an already negotiated connection to smb_composite_connect() 2018-07-24 06:55:23 +02:00
common Fix spelling s/propogate/propagate/ 2018-05-12 02:09:27 +02:00
ipc s4:libcli/smb2: align struct smb_ioctl.smb2 to [MS-SMB2] names 2019-03-28 23:09:36 +00:00
posix s3/ntvfs: squash 'cast between incompatible function types' warning 2019-05-16 17:55:17 +00:00
simple lib: modules: Change XXX_init interface from XXX_init(void) to XXX_init(TALLOC_CTX *) 2017-04-22 01:17:00 +02:00
sysdep s4: ntvfs: Add a TALLOC_CTX * to sys_notify_register(). 2017-05-13 16:50:13 +02:00
unixuid s4:auth/unix_token: remove unused tevent_context from security_token_to_unix_token() 2017-06-26 08:47:15 +02:00
ntvfs_base.c lib: modules: Change XXX_init interface from XXX_init(void) to XXX_init(TALLOC_CTX *) 2017-04-22 01:17:00 +02:00
ntvfs_generic.c s4:libcli/raw: add RAW_FILEINFO_NORMALIZED_NAME_INFORMATION support 2019-05-01 17:22:26 +00:00
ntvfs_interface.c s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
ntvfs_util.c
ntvfs.h s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
README
wscript_build s4-ntvfs: Remove untested ntvfs_cifsposix backend 2019-05-22 07:15:43 +00:00

README 

This is the base of the new NTVFS subsystem for Samba. The model for
NTVFS backends is quite different than for the older style VFS
backends, in particular:

- the NTVFS backends receive windows style file names, although they
  are in the unix charset (usually UTF8). This means the backend is
  responsible for mapping windows filename conventions to unix
  filename conventions if necessary

- the NTVFS backends are responsible for changing effective UID before
  calling any OS local filesystem operations (if needed). The
  become_*() functions are provided to make this easier.

- the NTVFS backends are responsible for resolving DFS paths

- each NTVFS backend handles either disk, printer or IPC$ shares,
  rather than one backend handling all types

- the entry points of the NTVFS backends correspond closely with basic
  SMB operations, wheres the old VFS was modelled directly on the
  POSIX filesystem interface.

- the NTVFS backends are responsible for all semantic mappings, such
  as mapping dos file attributes, ACLs, file ownership and file times