From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] samba: deprecate package due to EOL
Date: Fri, 6 Mar 2015 09:19:32 +0100 [thread overview]
Message-ID: <20150306091932.2ec87e37@free-electrons.com> (raw)
In-Reply-To: <54F8F0AA.5020902@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 05 Mar 2015 21:11:22 -0300, Gustavo Zacarias wrote:
> There's no pretty way out of this, the 3.6.x codebase is going
> completely unmaintained upstream.
> It's basically sheer luck that upstream fixed CVE-2015-0240 (which is
> pretty severe) on the 3.6.x branch, just because 4.2.0 was delayed.
> The best solution i can think of is either use samba 3.6.x as a fallback
> libsmbclient (not very nice looking forward) or switch everything to
> samba4 with the added size and restrictions.
> kodi and mpd aren't small so i don't think it should be a deciding
> factor, gvfs is meh, but then it's optional.
> I'd favor the 2nd option.
> Another factor to consider is that eventually (maybe already) the old
> libsmbclient won't be able to talk to newer windows servers anyway,
> specially when older versions of the protocol are disabled for security
> reasons.
Switching everything to Samba 4 is fine for me: that's the upstream
decision, and in Buildroot we generally try to follow upstream
decisions. If people are unhappy with Samba 4 being much bigger than
Samba 3, then it's up to them to work with the Samba folks upstream to
solve this. One guy posted some Buildroot patches at some point to only
install certain parts of Samba 4 to reduce the installed size, and we
invited him to work with upstream to resolve this.
So in my side, I'm fully OK with a solution that consists in switching
kodi, mpd and gvfs over to Samba 4.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-06 8:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 20:44 [Buildroot] [PATCH 1/2] samba: deprecate package due to EOL Gustavo Zacarias
2015-03-05 20:44 ` [Buildroot] [PATCH 2/2] samba4: bump to version 4.2.0 Gustavo Zacarias
2015-03-05 22:29 ` Thomas Petazzoni
2015-03-06 0:11 ` Gustavo Zacarias
2015-03-06 8:40 ` Thomas Petazzoni
2015-03-06 9:04 ` Gustavo Zacarias
2015-03-06 9:26 ` Thomas Petazzoni
2015-03-06 9:34 ` Gustavo Zacarias
2015-03-06 9:40 ` Thomas Petazzoni
2015-03-06 10:32 ` Gustavo Zacarias
2015-03-06 11:35 ` Thomas Petazzoni
2015-03-06 13:13 ` Gustavo Zacarias
2015-03-10 22:04 ` Peter Korsgaard
2015-03-10 21:53 ` Peter Korsgaard
2015-03-10 21:56 ` Thomas Petazzoni
2015-03-10 22:08 ` Peter Korsgaard
2015-03-10 21:49 ` Peter Korsgaard
2015-03-10 21:35 ` Peter Korsgaard
2015-03-06 10:03 ` Thomas Petazzoni
2015-04-09 10:33 ` Bernd Kuhls
2015-04-09 10:49 ` Gustavo Zacarias
2015-04-09 20:20 ` Waldemar Brodkorb
2015-04-10 12:16 ` Gustavo Zacarias
2015-04-16 19:55 ` Waldemar Brodkorb
2015-04-16 19:58 ` Gustavo Zacarias
2015-04-16 20:09 ` Waldemar Brodkorb
2015-04-16 20:13 ` Gustavo Zacarias
2015-04-16 20:19 ` Bernd Kuhls
2015-03-05 21:53 ` [Buildroot] [PATCH 1/2] samba: deprecate package due to EOL Arnout Vandecappelle
2015-03-05 22:06 ` Thomas Petazzoni
2015-03-05 22:10 ` Arnout Vandecappelle
2015-03-05 22:23 ` Thomas Petazzoni
2015-03-06 0:11 ` Gustavo Zacarias
2015-03-06 8:19 ` Thomas Petazzoni [this message]
2015-03-06 9:07 ` Gustavo Zacarias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150306091932.2ec87e37@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox