Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] CVE-2014-0160 : heartbleed CVE on openssl - http://heartbleed.com/
Date: Mon, 7 Apr 2014 18:38:58 -0700	[thread overview]
Message-ID: <CAA93jw7aJ0jEgMwSEuS+YddRCW32=-4dzUiZrNcOGW12m_hWAQ@mail.gmail.com> (raw)

This one looks pretty nasty.

see http://lwn.net/Articles/593683/ for more details.

The headache and cost of updating all the gear I maintain is insanely high.

Some of my OSes are so old as to no longer have updates, others have ssl certs
that I can now no longer trust for email or imap, still others work on
the vpn... and I only have a few dozen machines to fix, personally.

On the boxes I can update I see a whole bunch of new certs coming down
and it looks like ubuntu 13.10 has an update for sure...

(I feel for those with thousands or more services to patch.)

In cerowrt's case I cannot easily go back and rebuild a "stable" release, and
the vulnerability is limited (with the default package set) to the
admin web interface, which is by default limited to the local
interfaces...

... and by default we use perfect forward secrecy...

... and an attacker would want to read mips data

so the immediate vulnerabilities for cero are small.

but if this CVE is bad as it looks, vast chunks of the internet are
vulnerable, certs stolen, usernames and passwords exposed, end-sites
not trustable, etc, etc.

Cryptogeddon.






-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

             reply	other threads:[~2014-04-08  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  1:38 Dave Taht [this message]
2014-04-08 17:01 ` Stephen Hemminger

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='CAA93jw7aJ0jEgMwSEuS+YddRCW32=-4dzUiZrNcOGW12m_hWAQ@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