sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-03-08 04:58:40 +03:00
Code
samba-mirror/source3/librpc/gen_ndr/xattr.h

35 lines
813 B
C
Raw Normal View History

Implement vfs_ea_tdb This is an option for file systems that do not implement xattrs: in lockdir/eas.tdb an array of xatts per inode is stored. It can not solve the problem that xattrs might reappear if a posix-level process deletes a file and happens to re-create it under the same name. On file systems with birthtime we might have a chance to detect this, but not with standard posix. A future version might put relief on file systems that do have xattrs but where these are severely limited in size/speed/whatever: We can put a simple marker as a native xattr, but the xattrs proper are stored in the tdb. Volker (This used to be commit 2036b4c5ad677b8a477b34b0f076febab0abff5e)
2007-10-22 18:14:57 +02:00
/* header auto-generated by pidl */
#include <stdint.h>
#ifndef _HEADER_xattr
#define _HEADER_xattr
Add XATTR_NTACL_NAME constant. Jeremy. (This used to be commit 9c21756f9e841fd996590619b5eedc659f849626)
2008-07-10 17:19:01 -07:00
#define XATTR_NTACL_NAME ( "security.NTACL" )
Implement vfs_ea_tdb This is an option for file systems that do not implement xattrs: in lockdir/eas.tdb an array of xatts per inode is stored. It can not solve the problem that xattrs might reappear if a posix-level process deletes a file and happens to re-create it under the same name. On file systems with birthtime we might have a chance to detect this, but not with standard posix. A future version might put relief on file systems that do have xattrs but where these are severely limited in size/speed/whatever: We can put a simple marker as a native xattr, but the xattrs proper are stored in the tdb. Volker (This used to be commit 2036b4c5ad677b8a477b34b0f076febab0abff5e)
2007-10-22 18:14:57 +02:00
struct tdb_xattr {
const char * name;/* [flag(LIBNDR_FLAG_STR_UTF8|LIBNDR_FLAG_STR_NULLTERM)] */
DATA_BLOB value;
}/* [public] */;
struct tdb_xattrs {
uint32_t num_xattrs;
struct tdb_xattr *xattrs;
}/* [public] */;
Add in the IDL to store a NT Security descriptor in a blob. Use the same format as S4, but a new version as we'll need to store the timestamp to check for validity against the POSIX st_ctime. Jeremy. (This used to be commit 5c4ce1dac3769bfe533a4ea778c916d117603603)
2008-07-09 16:54:38 -07:00
struct security_descriptor_timestamp {
struct security_descriptor *sd;/* [unique] */
NTTIME last_changed;
}/* [public] */;
union xattr_NTACL_Info {
struct security_descriptor *sd;/* [unique,case] */
struct security_descriptor_timestamp *sd_ts;/* [unique,case(2)] */
}/* [switch_type(uint16)] */;
struct xattr_NTACL {
uint16_t version;
union xattr_NTACL_Info info;/* [switch_is(version)] */
}/* [public] */;
Implement vfs_ea_tdb This is an option for file systems that do not implement xattrs: in lockdir/eas.tdb an array of xatts per inode is stored. It can not solve the problem that xattrs might reappear if a posix-level process deletes a file and happens to re-create it under the same name. On file systems with birthtime we might have a chance to detect this, but not with standard posix. A future version might put relief on file systems that do have xattrs but where these are severely limited in size/speed/whatever: We can put a simple marker as a native xattr, but the xattrs proper are stored in the tdb. Volker (This used to be commit 2036b4c5ad677b8a477b34b0f076febab0abff5e)
2007-10-22 18:14:57 +02:00
#endif /* _HEADER_xattr */
Copy Permalink