On 2017-02-01 17:34, Ian McWilliam wrote:
Without going through the Samba code and trying to determine what and
why the changes were made by the Samba devs, I don't have an answer.
There have been a lot of changes to the internals of samba from
release to release e.g. 4.1 branch vs 4.5 branch, etc. I once knew the
samba 3 series internals quite well having made them work on OpenBSD
for many years. The 4 series is a slightly different beast.
Do to the fact that Samba has a lot of security updates, not just bug
fixes from month to month, rolling back to
a working 4.1 is definitely not the answer.
The current port should contain a message that simple file server
services work only. Anything else is a bonus.
If I knew enough about kernel hacking, resurrecting the initial work
that Dale Rahn did on implementing ACLS and finishing it would be the
way to move forward. Unfortunately I do not.
Working with upstream is the way to get some answers. Sorry I can't
shed anymore light on the subject at present.
Ian McWilliam
I'm gonna spin up a -current vm and start hacking away at samba to see
what is viable. Staying on 5.9 with S4.1 isn't viable long term and i
more or less need AD functionality out of it. I'd much prefer not having
to ditch openbsd for this job.
