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] cerowrt-3.10.36-6 released
Date: Sat, 19 Apr 2014 13:01:41 -0700	[thread overview]
Message-ID: <CAA93jw5btdZNKKKQpAh-tLB3Gxk7A5DNVCTcHjbbEuWBH64M6Q@mail.gmail.com> (raw)

+ felix's wifi patch for bug #442 added
   please break wifi.

+ debloat qlens reduced again to 12 for be and bk wifi queues
+ heartbleed fix from -3 forward

I note that nearly every "secured"-by-openssl network facing daemon has been
shown vulnerable to heartbleed. The hole in openvpn bit *me*, in
particular. I've updated, rekeyed and re-certified the vpns I have in
place, and you should too for any openvpn servers and clients you have
too.

It was a real PITA for me, and I only had a few boxes on it.

For more details, see: http://community.openvpn.net/openvpn/wiki/heartbleed

For more details on the daemons potentially affected by heartbleed in
cerowrt, openwrt, and others, see the advisory at:

http://www.bufferbloat.net/news/50

+ resync with openwrt
   notably there were updates to netifd, and a fix for a strongswan CVE

+ dnscrypt added as an optional package (thx stephen walker and "mailjoe")
+ snort added as an optional package

+/- full dnssec
- upgrade to httping 2.x broke
- no sqm autotuning yet
- neither snort nor dnscrypt tested

If you are not experiencing problems with wifi or with heartbleed
there are few reasons to update to this release.

I wanted to note to those that use sysupgrade without a clean reflash,
in that the
/etc/opkg.conf file is not re-written in this case, and still points
to the old repository.
If you wish to install additional packages after an inplace upgrade,
you will have
to also update /etc/opkg.conf to point to the right place.

-- 
Dave Täht

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

             reply	other threads:[~2014-04-19 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 20:01 Dave Taht [this message]
2014-04-20  7:37 ` Richard O
2014-04-21 19:10   ` Dave Taht
2014-04-20 20:46 ` Sebastian Moeller
2014-04-21 19:09   ` Dave Taht
2014-04-21 19:18     ` Sebastian Moeller
2014-04-21 19:42       ` Dave Taht
2014-04-21 21:34         ` Sebastian Moeller

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=CAA93jw5btdZNKKKQpAh-tLB3Gxk7A5DNVCTcHjbbEuWBH64M6Q@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