public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: www-client/phantomjs and dev-ruby/poltergeist
Date: Tue, 6 Jun 2017 05:49:23 +1200	[thread overview]
Message-ID: <20170606054708.1f811680@katipo2.lan> (raw)
In-Reply-To: <ba629594-f7d5-9435-7e7d-7113a33c9852@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 439 bytes --]

On Mon, 5 Jun 2017 13:42:50 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:

> Hans was
> attempting to fix it, but now that upstream is dead, it will remain
> insecure forever.

IME, as long as that's clear from the pmask, and its clear what those
security vectors are, as long as an end user makes sure those vectors
can't happen, having an insecure-in-theory-but-not-in-practice
phantomjs is better than having no phantomjs. 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-06-05 17:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  7:11 [gentoo-dev] Last rites: www-client/phantomjs and dev-ruby/poltergeist Hans de Graaff
2017-06-05 11:06 ` Kent Fredric
2017-06-05 11:38   ` Vadim A. Misbakh-Soloviov
2017-06-06  5:31     ` Hans de Graaff
2017-06-05 17:42   ` Michael Orlitzky
2017-06-05 17:49     ` Kent Fredric [this message]
2017-06-06  8:30     ` Pacho Ramos
2017-06-06  5:28   ` Hans de Graaff
2017-06-06  9:11     ` Kent Fredric
2017-06-11  6:38       ` Hans de Graaff
2017-06-11 17:41         ` Kent Fredric
2017-09-19 13:44       ` Tony Vroon
2017-09-21  4:57         ` Kent Fredric

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=20170606054708.1f811680@katipo2.lan \
    --to=kentnl@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