Insecurity by blindly patching non-existant security holes. Ich habe in meinem Netzwerk eine NAS bei der ich das Problem habe, das die integrierte FTP Funktion nicht das tut was sie soll. In Samba 3.6.25 I just didn't apply the breakage (so-called 'fix'), in Samba 4.x I had to shoot holes into its config, because now it will also allow true wide links (E.g. NAS Ordner (Bestimmte) sollen mit Raspberry Pi an Proftpd als FTP Freigeschaltet werden Sun 12:47 pm Hallo zusammen. Starting with some broken security 'fix' in Samba 3.6.25, Samba now considers everything that isn't a regular file or directory as a wide link, so even if you share '/' (Which is everything, nothing below can be wide), Samba will consider even /tmp as a wide link, although it's a non-wide link, pointing to /var/tmp (Which is also below '/'). Originally Samba correctly interpreted wide links in exactly this way. If you share /media, neither /media/hdd nor /media/autofs are wide links, as they are below the share '/media'. if you share '/media/hdd' and there is a link /media/hdd/movie/NAS pointing to /media/autofs/NAS/movie, that would be a wide link, as /media/autofs is not shared (it's one level up from /media/hdd). 'Media' shared /media and everything below is considered a wide link (although in fact it's mount points).Į.g. 'Harddisk' shares /media/hdd, most stuff below are regular files and directories. I still claim it is related to Samba 4.x considerung about everything as a wide link.
