From owner-freebsd-isp Mon Dec 11 15: 3:21 2000 From owner-freebsd-isp@FreeBSD.ORG Mon Dec 11 15:03:18 2000 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from inago.swcp.com (inago.swcp.com [198.59.115.17]) by hub.freebsd.org (Postfix) with ESMTP id 16A1637B400 for ; Mon, 11 Dec 2000 15:03:18 -0800 (PST) Received: from localhost (deichert@localhost) by inago.swcp.com (8.8.7/8.8.7) with ESMTP id QAA18453; Mon, 11 Dec 2000 16:02:58 -0700 (MST) X-Authentication-Warning: inago.swcp.com: deichert owned process doing -bs Date: Mon, 11 Dec 2000 16:02:58 -0700 (MST) From: Diana Eichert X-Sender: deichert@inago.swcp.com To: Jim King Cc: tom.oneil@instantisp.net, Free Subject: Re: SMB over internet In-Reply-To: <012c01c063b7$5d0ea620$524c8486@jking> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There is also a way to tunnel SMB via SSL. http://www.google.com/search?q=samba+ssl On Mon, 11 Dec 2000, Jim King wrote: > "Tom ONeil" wrote: > > > Anyone ever allow SMB to be used, either NT or Samba, for a server? I > > have a client who wants to share a database with remote employees. > > My gut reaction is no, but I don't know the protocol well enough to > > detail why it's a bad idea and what alternatives to offer. > > I've done it with Samba and NT; it works. > > Of course it's best to do this via a VPN setup. If you can't do that at > least tell Samba to use encrypted passwords and make sure the Windows boxes > are setup the same way; NT 4.0 SP3 or later defaults to encrypted > passwords, and I think Win98 and later default that way also. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message