From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Joe MacDonald <Joe.MacDonald@windriver.com>, rongqing.li@windriver.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH v2] Upgrade vsftpd to 3.0.0
Date: Wed, 17 Jul 2013 21:48:17 +0100 [thread overview]
Message-ID: <12162896.r64JGkun5K@helios> (raw)
In-Reply-To: <20130717184315.GA31259@windriver.com>
On Wednesday 17 July 2013 14:43:16 Joe MacDonald wrote:
> This adds (unconditional) support for tcp-wrappers and makes it a
> requirement for the upgraded vsftp. Is this something we could make
> conditional based on tcp-wrappers being present? Or does anyone think
> this is something worth doing? tcp-wrappers is coming from oe-core and
> I don't have any systems where the new requirement would be a problem,
> but does anyone else have a system they'd want vsftp without
> tcp-wrappers?
We've recently added tcp-wrappers to a number of recipes in OE-Core; at the
time there was a discussion about a possible follow-up to add a
DISTRO_FEATURES item to disable it system-wide. I guess whether or not it's
worth it depends on what the overhead of having it enabled is.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-17 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 12:51 [meta-networking][PATCH v2] Upgrade vsftpd to 3.0.0 rongqing.li
2013-07-17 18:43 ` Joe MacDonald
2013-07-17 20:48 ` Paul Eggleton [this message]
2013-07-18 7:59 ` Rongqing Li
2013-07-18 13:18 ` Joe MacDonald
2013-07-18 8:22 ` Rongqing Li
2013-07-18 13:17 ` Joe MacDonald
2013-07-19 0:30 ` Rongqing Li
-- strict thread matches above, loose matches on Subject: below --
2013-07-19 2:19 rongqing.li
2013-07-19 14:58 ` Joe MacDonald
2013-07-19 15:22 ` Joe MacDonald
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=12162896.r64JGkun5K@helios \
--to=paul.eggleton@linux.intel.com \
--cc=Joe.MacDonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=rongqing.li@windriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.