From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] bufferbloat.net prep
Date: Thu, 4 Jan 2018 14:49:39 -0800 [thread overview]
Message-ID: <CAA93jw40sKWePRFasxTvGpVDSk1OuqcjvDw_YSGTtXctpX1CdQ@mail.gmail.com> (raw)
Most of the bufferbloat.net servers are on linode. They are planning a
fleet-wide reboot:
https://blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre/
'Course this doesn't help as much as you'd like if one or more of your
servers is already compromised, and had keys or shared passwords. So -
sigh - theoretically I'm on vacation - I'm planning on revoking those
keys, and rebuilding others from scratch.
I might, like other big providers do, end up building my own cloudy
kernels again.
There's only one server I seriously care about the security of in the
cloud, the vpn server. Maybe it's time to truly decentralize the vpn
this time around. I think of how exposed others must be, and shudder.
"If your provider does not have a fix then now is a good time to
practice that recovery plan you should have for what to do when your
cloud provider goes down....." - Alan Cox
https://plus.google.com/+AlanCoxLinux/posts/Z6inLSq4iqH
On Thu, Jan 4, 2018 at 2:35 PM, Joel Wirāmu Pauling <joel@aenertia.net> wrote:
> I was too busy skateboarding holding on to the bumper of my Limo to take
> notice obviously.
>
> On 5 January 2018 at 11:26, Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>> > On 5 Jan, 2018, at 12:09 am, dpreed@deepplum.com wrote:
>> >
>> > I should point out here that I was one of the researchers that helped
>> > develop the original multi-level security systems then. Those "colored
>> > books" come from us.
>>
>> Obligatory: https://www.youtube.com/watch?v=4U9MI0u2VIE
>>
>> - Jonathan Morton
>>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
reply other threads:[~2018-01-04 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw40sKWePRFasxTvGpVDSk1OuqcjvDw_YSGTtXctpX1CdQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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