IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
docs/faq.
Replaced all reference to samba.canberra.edu.au/pub/samba/samba.html
with samba.anu.edu.au/samba/
Replaced references to ictinus@lake.canberra.edu.au
with ictinus@samba.anu.edu.au
Added 3 new mirrors, Greece, Poland, Romania
Paul.
setting applies to all shares regardless of any settings on other
shares. This allows us to immediately drop a connection if it does not
come from a allowed host, without even parsing the first SMB
packet. The next time we get a nasty security hole we can offer people
the option of just setting their hosts allow line.
If we drop a connection in this way we generate a "Not listening for
calling name" response and then exit.
add a per share "oplocks" option in smb.conf. I think its important to
be able to disable oplocks on a per-share basis as there are occasions
then they are definately not wanted, for example when sharing data
between a windows box and a unix application. This also allows us to
tell people "try disabling oplocks" when diagnosing problems.
fix a bug in process_smb(). It was taking the length of the packet
from outbuf, not inbuf (this bug was introduced with the oplocks
code). Jeremy, I assume this wasn't deliberate?
\\SAMBA_SERVER\%U\profile for the profile path. documented default
profile path changing to \\%L\%U\profile, so that w95 and NT can use
the same profile directory: you cannot use \\%L\%U for NT profiles.
lkcl
workgroups (domains are a superset of workgroups: workgroups have no
concept of security at all)
- updated comments about profiles from conversations with john t, and from
samba digest input. this includes the need for encrypted passwords when
supporting NT workstation, and enlisting the assistance of an NT server
to tell workstations that their profile is on a samba server.
lkcl
authentication. NT SAM is only one case of many kinds of distributed
authorisation database. Domain logons, RAP etc should all work perfectly
from NT workstations to Samba servers no matter what username/passwd
database lies underneath (once the protocols have been implemented, of
course.... :-)
