similar to: Wide links and insecure wide links

Thanks - that much I (pretty much) got. Its really the "wide links" option that isn't well distinguished/clarified. *insecure* wide links is much more clear, although the detail you've given helps a lot. What exactly is the "ordinary" "wide links = yes" option going to do (with or without Unix extensions), and how does it compare/how much exposure to

Thank you. So, If I understand correctly, "ordinary" "wide links = yes", means Samba *will* traverse an existing symlink that points outside the root of the share, if permissions allow. However because it *also* disables SMB1 Unix extensions, it *also* prevents the user from creating or modifying symlinks on the share, so in wffect it inherently prevents this being

On Wed, Feb 28, 2018 at 08:36:14PM +0000, Stilez wrote: > Thank you. > > So, If I understand correctly, "ordinary" "wide links = yes", means Samba > *will* traverse an existing symlink that points outside the root of the > share, if permissions allow. However because it *also* disables SMB1 Unix > extensions, it *also* prevents the user from creating or

In the vfs pages for aio_pthread, it gives as an example for aio read/write size, 1024 for each and states an "appropriate" value must be set. Byt in smb.conf it states that the only reasonable values are 0 or 1 (also that there's a default = 1 so no value need be given explicitly). Which of these is correct? Thanks, Stilez

As mentioned in another thread, I notice that the params used to control symlinks feel a bit inefficient and inelegant, and quite limited. I think there might be a good opportunity to simplify and also make their management in Samba more powerful and adaptable to use-cases. I'm guessing this list is a good enough starting point to propose a smb.conf param change to this area and see what

Does the 'allow insecure wide links' parameter work in the Samba in RHEL 6.5 (which is 3.6.9-167.el6_5)? I need 'unix extensions' to be yes and also follow wide links. So I set 'allow insecure wide links' but it doesn't seem to work. By the way (and this may be a known issue that's been resolved in later releases) after we upgraded our Macs to 10.9 (which rolled

Louis, Last lines in /etc/default/ufw: IPT_MODULES="nf_conntrack_ftp nf_nat_ftp nf_conntrack_irc nf_nat_irc nf_conntrack_netbios_ns" Looks like nf_contrack_netbios_ns is already loaded. iptables -S requires more arguments. Suggestions? Marty

Meanwhile it appears to contradict. Is there any reason not to update the vfs doc to reflect the old situation pre-bugfix and the current suggested values? On 8 March 2018 9:28:30 pm Jeremy Allison <jra at samba.org> wrote: > On Thu, Mar 08, 2018 at 09:00:48PM +0000, Stilez via samba wrote: >> In the vfs pages for aio_pthread, it gives as an example for aio read/write >>

On 24/04/19 19:51, L.P.H. van Belle wrote: > Hai, > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Rowland Penny via samba >> Verzonden: woensdag 24 april 2019 12:13 >> Aan: samba at lists.samba.org >> Onderwerp: Re: [Samba] User mapping/login issue >> >> On Wed, 24 Apr 2019 11:38:58 +0200

I've been running Samba 4 in NT4 Domain mode for a few years, and it's been working fine with Windows 7 PCs. I now need to join a new Windows 10 PC to the domain, but I'm not having any success! When I try to join the domain, the Windows 10 PC says "An Active Directory Domain Controller could not be contacted...." I've tried a few things, including:- Setting

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

Hi friends, I updated our old sparc Solaris 9 server running samba 2.2.8a to 3.6.15 so that Mac 10.7+ users could access this file server. However now we can't see files in folders that are links to NFS mounts from other servers. I can access folders/files that are links outside the share but local to the samba server, but for links to folders that are mounted to the server via NFS from

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland Penny via samba > Verzonden: donderdag 25 april 2019 11:09 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] User mapping/login issue > > On Thu, 25 Apr 2019 10:24:36 +0200 > L.P.H. van Belle <belle at bazuin.nl> wrote: > > > Ps.

Andreas, On Thu, Aug 24, 2017 at 03:37:07PM +0200, awl1 via samba wrote: > Before I follow your advice to move this whole issue/topic to the > samba-technical alias and start over there with a clean description of the > scenario and the findings, I have two simple questions: > > 1) I plan to use a new, reproducible test scenario with 2000 random small > files with a file length

Hi We've got drbd going between 2 nodes:) ATM there is un-partitioned space on each node but (we think) they are syncing OK. It looks as though it has synced the whole partition (2GB) from the primary node 1 to the other node: node 1 smb1:/home/steve # cat /proc/drbd version: 8.4.4 (api:1/proto:86-101) GIT-hash: 3c1f46cb19993f98b22fdf7e18958c21ad75176d build by SuSE Build Service 1:

Hi everyone, I'm having the following situation: I need to migrate all SMB file services to a new appliance that only supports the SMB2+ protocol. Unfortunately, there are still some very old Linux clients ("modinfo cifs" says version 1.60) that do only speak SMB1 and need to access these shares after the migration. Is it possible to have a Linux with a modern Samba

I have a classic NT4 domain with the PDC also the wins server. With the recent ransomware problem, we're trying to remove SMB1 and below protocols. However when I do this, the browse list is gone. Hosts can access properly the shares, but they have to know exactly \\machine\share in order to to connect. The same thing from a linux client: smbclient -L {PDC} -m SMB2 Domain=[{MYDOMAIN}]

I conducted many tests and I noticed that I lose the domain-join on SMB1 soon as I joined SMB2 in the domain. Step 1: SMB1 "net ads join -Uadministrator" -> OK Step 2: SMB1 "net ads testjoin" -> OK Step 3: SMB2 "net ads join -Uadministrator" -> OK Step 4: SMB2 "net ads testjoin" -> OK Step 5: SMB1 "net ads testjoin" ->

Hai, ... > > As I said, where is the fault, is it something that Windows 10 is or > isn't doing, or is it Samba ? > > Well, we cannot change Windows, so on that basis, I think you should > make a Samba bug report and let it work through the system. > > Rowland Well, yes, we can change windows, by allowing/disallowing SMB1. Which might help in detecting whats

Hi Samba list! I was very excited that SMB2 is finally working with samba 3.6.0 - great job!! I just know that SMB2 has a smaller command set compared to SMB1 and this, beside many other rebuilds of the code makes it faster As I am completely new to the file transfer protocol world, I want to ask a few basic things: - is Samba backward compatible ... xp can't use SMB2 as far as I