| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Luckily the build farm caught this
|
|
|
|
|
|
|
|
|
|
| |
- Adds new -c <custom conf> option to selftest.sh that when specified
adds a line to make test's server.conf: "include <custom conf>"
- Adds getopts processing to selftest.sh
- Changes selftest.sh shrdir arg to use -s <shrdir>
- Changes selftest.sh smbtorture4_path arg to use -t <smbtortur4 path>
- Adds configure option --with-selftest-custom-conf=<custom conf>
- Updates Makefile.in to take advantage of the new/changed parameters
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The caller might have over-allocated reply->outbuf. Deal with that.
Sorry, Günther, for giving you so much pain ...
Volker
|
|
|
|
|
| |
entry->data_record.strings is type smb_ucs2, so the pointer arithmetic
increments by two :-)
|
| |
|
|
|
|
|
|
|
|
|
| |
1) Add in smb_file_time struct to clarify code and make room for createtime.
2) Get and set create time from SMB messages.
3) Fixup existing VFS modules + examples Some OS'es allow for the
setting of the birthtime through kernel interfaces. This value is
generically used for Windows createtime, but is not settable in the
code today.
|
|
|
|
| |
resolution in the FreeBSD stat structure
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
|
|
| |
rpc_server."
This reverts commit c0f1309010b79be67557af5ffbd1c429a3f3d99a.
|
|
|
|
| |
Guenther
|
|
|
|
|
|
| |
This broke with f6fa3080fee1b20df9f1968500840a88cf0ee592 back in April 2007...
Guenther
|
|
|
|
|
|
|
|
| |
version
Eventually these two other definitions should be removed and all of
the TALLOC macros should live in the same header. Until then, this
patch eliminates some build warnings.
|
|
|
|
|
|
|
|
|
| |
failures this week
The bug was introduced when converting samba3's ldb_search interface
to match samba4:
47951fc5d0085e124666b7667715bba98076820e
f3ecb701335b1129947127d4c45eef970b66875c
|
|
|
|
| |
Saved around 10kb of code on my box :-)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updates the onefs vfs module to add configurable behavior to deal
with sids that are unknown to us. The best examples are aces that
come from robocopy/xcopy.
Adds the following share level options (which are specific to the vfs_onefs
module):
onefs: ignore unmappable sids (Default = false)
If this option is set to true, sids which could not be resolved to
a uid/gid are ignored. If an unmappable sid is encountered as the owner
or group, the owner/group is converted to BUILTIN\Administrators.
onefs: unmappable sids ignore list (Default = empty)
Only the sids in the list are ignored.
onefs: ignore sacls (Default = false)
SACLs are ignored
onefs: unmappable sids deny everyone (Default = false)
If an unmappable sid is found in a deny ACE, the ACE's identity is
changed to Everyone.
|
| |
|
|
|
|
|
| |
to NFSv4 ACL code as this uses the same flawed logic as posix_acls.c.
Jeremy.
|
|
|
|
|
| |
to ourselves unless that was passed in.
Jeremy.
|
|
|
|
|
|
|
|
| |
ACLs.
If the chown succeeds then the ACL set should also. Ensure this is the case
(refactor some of this code to make it simpler to read also).
Jeremy.
|
|
|
|
|
| |
Sorry for the monster checkin, I could not really find a way to do this in
steps.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Simo is completely correct. We should be doing the chown *first*, and fail the
ACL set if this fails. The long standing assumption I made when writing the
initial POSIX ACL code was that Windows didn't control who could chown a file
in the same was as POSIX. In POSIX only root can do this whereas I wasn't sure
who could do this in Windows at the time (I didn't understand the privilege
model). So the assumption was that setting the ACL was more important (early
tests showed many failed ACL set's due to inability to chown). But now we have
privileges in smbd, and we must always fail an ACL set when we can't chown
first. The key that Simo noticed is that the CREATOR_OWNER bits in the ACL
incoming are relative to the *new* owner, not the old one. This is why the old
user owner disappears on ACL set - their access was set via the USER_OBJ in the
creator POSIX ACL and when the ownership changes they lose their access.
Patch is simple - just ensure we do the chown first before evaluating the
incoming ACL re-read the owners. We already have code to do this it just wasn't
rigorously being applied.
Jeremy.
|
| | |
|
| |
| |
| |
| | |
metze
|
| |
| |
| |
| | |
metze
|
| |
| |
| |
| | |
metze
|
| |
| |
| |
| |
| |
| | |
triggered now
metze
|
| |
| |
| |
| |
| |
| | |
triggered now
metze
|
| |
| |
| |
| |
| |
| | |
triggered now
metze
|
| |
| |
| |
| |
| |
| | |
instead
metze
|
| |
| |
| |
| |
| |
| | |
tevent_loop_once()
metze
|
| |
| |
| |
| |
| |
| | |
interfaces
metze
|
| |
| |
| |
| |
| |
| |
| |
| | |
This converts the irix oplocks code to use a fd event
and removes the last special case for file descriptors
for the main sys_select().
metze
|
| |
| |
| |
| |
| |
| | |
And always setup the fd events.
metze
|
| |
| |
| |
| |
| |
| | |
We might have pending signal events not only timed events.
metze
|
| | |
|
|\| |
|