From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] removing vulnerable versions of dev-lang/v8
Date: Fri, 8 Nov 2013 10:00:16 -0500 [thread overview]
Message-ID: <CAGfcS_kszbifgRuPRLxh+jOS+47GdM-_eK7a=JY1n4mELkT+jg@mail.gmail.com> (raw)
In-Reply-To: <527CF847.20608@gentoo.org>
On Fri, Nov 8, 2013 at 9:42 AM, Ian Stakenvicius <axs@gentoo.org> wrote:
> I'm still a little concerned about the potential security issues
> caused by embedded V8's in projects, but as we've already concluded in
> that other thread, there's no other way until the API stabilizes..
Yup. When a project uses a library with an unstable API, they're
basically taking on a commitment to fork it unless upstream backports
all fixes. If the alternative is re-implementing the library the
project is no worse off (at least with embedded libs we know about the
vulnerabilities). If there are other alternatives, then they should
probably rethink their strategy.
Rich
next prev parent reply other threads:[~2013-11-08 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 5:22 [gentoo-dev] removing vulnerable versions of dev-lang/v8 "Paweł Hajdan, Jr."
2013-11-08 14:42 ` Ian Stakenvicius
2013-11-08 15:00 ` Rich Freeman [this message]
2013-11-08 15:18 ` Diego Elio Pettenò
2013-11-08 15:25 ` Peter Stuge
2013-11-08 21:49 ` hasufell
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='CAGfcS_kszbifgRuPRLxh+jOS+47GdM-_eK7a=JY1n4mELkT+jg@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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