summaryrefslogtreecommitdiff
path: root/source3/client
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2002-05-17 12:42:39 +0000
committerAndrew Bartlett <abartlet@samba.org>2002-05-17 12:42:39 +0000
commiteed5094264945ca8ccf47030375cc56808ae8ea3 (patch)
tree4a39aca15191b1a857e60f5a4b761fce29867688 /source3/client
parenta64932dfc06af46d4a4eebd6fb537e229466b00b (diff)
downloadsamba-eed5094264945ca8ccf47030375cc56808ae8ea3.tar.gz
samba-eed5094264945ca8ccf47030375cc56808ae8ea3.tar.bz2
samba-eed5094264945ca8ccf47030375cc56808ae8ea3.zip
This removes --with-ssl from Samba.
This option was badly maintained, useless and confused our users and distirbutors. (its SSL, therfore it must be good...) No windows client uses this protocol without help from an SSL tunnel. I can't see any reason why setting up a unix-side SSL wrapper would be any more difficult than the > 10 config options this mess added to samba in any case. On the Samba client end, I think the LIBSMB_PROG hack should be sufficient to start stunnel on the unix side. We might extend this to take %i and %p (IP and port) if there is demand. Andrew Bartlett (This used to be commit b04561d3fd3ee732877790fb4193b20ad72a75f8)
Diffstat (limited to 'source3/client')
-rw-r--r--source3/client/client.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/source3/client/client.c b/source3/client/client.c
index 0630bbb44b..8834f7d3f4 100644
--- a/source3/client/client.c
+++ b/source3/client/client.c
@@ -2635,10 +2635,6 @@ static void remember_query_host(const char *arg,
}
DEBUGLEVEL = old_debug;
-#ifdef WITH_SSL
- sslutil_init(0);
-#endif
-
pstrcpy(workgroup,lp_workgroup());
load_interfaces();