Thanks for clearing this up Juan and Shawn.
I noticed I could change smbd to run in inetd mode if I flip the switch
in /etc/default/samba, but I don't known how this would improve things,
eventually create new drawback in cifs performance ... so I'll keep it
as it is with additional smb.conf entries + daemon mode.
The server is behind a router/firewall, it should be safe as it is.
On 26.04.2012 12:54, shawn wilson wrote:
Juan is correct. However my two cents - don't rely on hosts.allow and
hosts.deny for anything. Just use iptables rules to do this type of thing.
Also, most don't consider samba to be a very secure service (last CVE
was only a few weeks ago) so be very careful with this service.
On Apr 26, 2012 5:37 AM, "Juan Sierra Pons" <juan@elsotanillo.netwrote
I think the problem here is between tcpwrapper linux implementation
and the the samba package.
Are you running samba as a daemon or from then inetd?
I think you are running it as a daemon and I believe (check on the
internet) samba must be compiled in a tcpwrapper friendly way (I don't
know if this is the default)
Running samba from inetd must work OK as inetd is tcpwrapper friendly.
If this doesn't help you you can try iptables (but your workaround
is OK too)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/blu0-smtp43485cca6a02a0ab00e9db0d8...@phx.gbl
