From: stanley lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] inquery: plans for phasing out cpu, rx and import
Date: Tue, 09 Aug 2016 13:59:45 -0400 [thread overview]
Message-ID: <edc592be-efef-4bd9-a058-9c285262b7f9@email.android.com> (raw)
In-Reply-To: <0708b70b1ecfa9b6866bde2d5b038acb@felloff.net>
cinap_lenrek@felloff.net wrote:
>> Disabling the listeners on 9front is obvious, and since Plan 9 is
>dead, maintenance is not really needed, but why remove it, exactly?
>Just to feel "clean"?
>
>i just recently fixed a bug in devssl.c. its not like if labs doesnt
>change
>the protocol anymore, the impementation was bugfree. worse, this bug
>could
>be used to disrupt the whole system, not just break security of the
>weakly
>encrypted connection.
>
>--
>cinap
I guess I did not grasp that leaving the old cpu kernel bits in place still represented a security risk even if nobody is running the old listeners. If that is the case then I agree we should remove the stuff (and perhaps make it available in /n/extra).
sl
next prev parent reply other threads:[~2016-08-09 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 19:39 cinap_lenrek
2016-08-07 2:25 ` [9front] " sl
2016-08-07 23:55 ` kokamoto
2016-08-08 1:37 ` sl
2016-08-08 7:38 ` kokamoto
2016-08-08 15:22 ` stanley lieber
2016-08-08 15:53 ` hiro
2016-08-08 16:33 ` cinap_lenrek
2016-08-09 9:45 ` hiro
2016-08-09 14:57 ` Kurt H Maier
2016-08-09 15:12 ` stanley lieber
2016-08-09 17:46 ` cinap_lenrek
2016-08-09 15:09 ` stanley lieber
2016-08-09 15:33 ` Kurt H Maier
2016-08-11 8:47 ` Steve Simon
2016-08-09 17:44 ` cinap_lenrek
2016-08-09 17:56 ` stanley lieber
2016-08-09 17:49 ` cinap_lenrek
2016-08-09 17:59 ` stanley lieber [this message]
2016-08-10 10:04 ` hiro
2016-08-08 15:54 ` cinap_lenrek
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=edc592be-efef-4bd9-a058-9c285262b7f9@email.android.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).