From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: George McCollister <george.mccollister@gmail.com>,
Armin Kuster <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Update Samba
Date: Mon, 25 Apr 2016 10:01:48 -0400 [thread overview]
Message-ID: <20160425140147.GB5188@mentor.com> (raw)
In-Reply-To: <CAFSKS=OrhdjemW+1t1uMpGUbcnP0s5JX59Z4mvv_hqPpwBXG_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
[Re: [oe] Update Samba] On 16.04.22 (Fri 11:30) George McCollister wrote:
> I'm looking forward to seeing these changes in krogoth as what is in
> there now is unusable from a security standpoint. I cherry picked the
> patches to krogoth and my builds suceeded but haven't gotten around to
> doing any operational testing yet.
Agreed.
Armin: I've already done one merge directly to krogoth to resolve a
build breakage, but since you're maintaining the branch I didn't want to
do any additional ones (even though we started talking about samba
specifically in the krogoth context) without an explicit go-ahead from
you.
Do you want me to send you a patch set, a pull request or do you want me
to merge the samba changes directly?
-J.
>
> -George
>
> On Mon, Apr 18, 2016 at 4:00 PM, Joe MacDonald <joe_macdonald@mentor.com> wrote:
> > I'm still doing some testing on this and I haven't built for all the
> > architectures yet, but it passed at least the most basic smoke-test. Given the
> > number of outstanding CVEs against our current version of Samba (thanks Armin!
> > :-)) I think it's best fo rus to update this rather than trying to do any
> > back-ports, but that also introduces a not-inconsiderable level of risk for
> > Samba users. So please, if you're one of them, kick the tires on this as soon
> > as you can (or ping me back letting me know what your thoughts are on this, at
> > least).
> >
> > Thanks all.
> >
> > --
> > -Joe MacDonald.
> > :wq
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2016-04-25 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 21:00 Update Samba Joe MacDonald
2016-04-18 21:00 ` [meta-networking][PATCH 1/5] libtalloc: Update to latest stable Joe MacDonald
2016-04-18 21:00 ` [meta-networking][PATCH 2/5] libtdb: " Joe MacDonald
2016-04-18 21:00 ` [meta-networking][PATCH 3/5] libtevent: " Joe MacDonald
2016-04-18 21:00 ` [meta-networking][PATCH 4/5] libldb: " Joe MacDonald
2016-04-18 21:00 ` [meta-networking][PATCH 5/5] samba: " Joe MacDonald
2016-04-19 9:15 ` Martin Jansa
2016-04-19 13:01 ` Joe MacDonald
2016-04-20 9:27 ` Martin Jansa
2016-04-20 13:06 ` Joe MacDonald
2016-04-27 18:30 ` Mark Asselstine
2016-04-22 16:30 ` Update Samba George McCollister
2016-04-25 14:01 ` Joe MacDonald [this message]
2016-04-25 14:38 ` akuster808
2016-04-25 14:54 ` Joe MacDonald
2016-04-25 14:43 ` akuster808
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=20160425140147.GB5188@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=akuster808@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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