aboutsummaryrefslogtreecommitdiffstats
path: root/package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch
diff options
context:
space:
mode:
authorRosen Penev <rosenp@gmail.com>2019-08-31 18:50:48 -0700
committerStijn Tintel <stijn@linux-ipv6.be>2020-05-08 03:32:52 +0300
commit73fa1aba94f5cf566007ac18cee3ef08b3ae64bc (patch)
tree12d94da20915031cd34260409e6355c8e05b66b7 /package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch
parent79da9d78b98e1cd4574a37e2c4c5f8315b91563d (diff)
downloadupstream-73fa1aba94f5cf566007ac18cee3ef08b3ae64bc.tar.gz
upstream-73fa1aba94f5cf566007ac18cee3ef08b3ae64bc.tar.bz2
upstream-73fa1aba94f5cf566007ac18cee3ef08b3ae64bc.zip
samba36: Remove
Samba 3.6 is completely unsupported, in addition to having tons of patches It also causes kernel panics on some platforms when sendfile is enabled. Example: https://github.com/gnubee-git/GnuBee_Docs/issues/45 I have reproduced on ramips as well as mvebu in the past. Samba 4 is an alternative available in the packages repo. cifsd is a lightweight alternative available in the packages repo. It is also a faster alternative to both Samba versions (lower CPU usage). It was renamed to ksmbd. To summarize, here are the alternatives: - ksmbd + luci-app-cifsd - samba4 + luci-app-samba4 Signed-off-by: Rosen Penev <rosenp@gmail.com> [drop samba36-server from GEMINI_NAS_PACKAGES, ksmbd rename + summary] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Diffstat (limited to 'package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch')
-rw-r--r--package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch40
1 files changed, 0 insertions, 40 deletions
diff --git a/package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch b/package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch
deleted file mode 100644
index 055a15e87e..0000000000
--- a/package/network/services/samba36/patches/030-CVE-2017-15275-v3.6.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From c1a22e59f87783d88dfbaeeb132b89be166b2754 Mon Sep 17 00:00:00 2001
-From: Jeremy Allison <jra@samba.org>
-Date: Wed, 20 Sep 2017 11:04:50 -0700
-Subject: [PATCH 2/2] s3: smbd: Chain code can return uninitialized memory when
- talloc buffer is grown.
-
-Ensure we zero out unused grown area.
-
-CVE-2017-15275
-
-BUG: https://bugzilla.samba.org/show_bug.cgi?id=13077
-
-Signed-off-by: Jeremy Allison <jra@samba.org>
----
- source3/smbd/srvstr.c | 14 ++++++++++++++
- 1 file changed, 14 insertions(+)
-
---- a/source3/smbd/srvstr.c
-+++ b/source3/smbd/srvstr.c
-@@ -70,6 +70,20 @@ ssize_t message_push_string(uint8 **outb
- DEBUG(0, ("srvstr_push failed\n"));
- return -1;
- }
-+
-+ /*
-+ * Ensure we clear out the extra data we have
-+ * grown the buffer by, but not written to.
-+ */
-+ if (buf_size + result < buf_size) {
-+ return -1;
-+ }
-+ if (grow_size < result) {
-+ return -1;
-+ }
-+
-+ memset(tmp + buf_size + result, '\0', grow_size - result);
-+
- set_message_bcc((char *)tmp, smb_buflen(tmp) + result);
-
- *outbuf = tmp;