On the server side (as domain controller) we have the following new options: "allow nt4 crypto" (no by default), "reject md5 client" (no by default). for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs you need "require strong key = no" and "client NTLMv2 auth = no", In addition a strong session key is now required by default, which means that communication to older servers or clients might be rejected by default.įor the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). This is the proper fix for a large number of bugs: The whole concept of maintaining the netlogon secure channel to (other) domain controllers was rewritten in order to maintain global state in a netlogon_creds_cli.tdb. This provides the ability for remote clients to access shadow-copies via Windows Explorer using the "previous versions" dialog. The newly added Snapper VFS module exposes snapshots managed by Snapper for use by Samba. Files flagged for compression are transparently compressed and uncompressed when accessed or modified. With the Btrfs Samba VFS module enabled, SMB2+ compression flags can be set remotely from the Windows Explorer File->Properties->Advanced dialog. Samba 4.2.0 adds support for the manipulation of file and folder compression flags on the Btrfs filesystem. De belangrijkste verandering in versie 4.2 zijn hieronder voor je op een rijtje gezet. Met deze uitgave is ondersteuning voor versie 3 van Samba officieel komen te vervallen. Uitgebreide documentatie, inclusief praktische how-to's voor een iets oudere versie, kunnen op deze pagina worden gevonden. Sinds versie 3 kan Samba file- en print-services aan Windows-clients aanbieden en is het in staat om als domain controller te fungeren. Dit programma draait op Unix-, BSD- en Linux-servers, en is een opensource-implementatie van het smb/ cifs- netwerkprotocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |