General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] The press release is working
Date: Thu, 15 Oct 2015 15:21:19 -0400	[thread overview]
Message-ID: <561FFCAF.5080305@rogers.com> (raw)
In-Reply-To: <E89FDF87-7F78-4C1E-A0F4-56BD0214342F@gmx.de>

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

The slashdotties (of which I'm included) saw it and started a discussion 
on "Why Cybersecurity Experts Want Open Source Routers"
> derekmead <http://hardware.slashdot.org/%7Ederekmead>writes:/A 
> coalition of 260 cybersecurity experts is taking advantage ofa Federal 
> Communications Commission (FCC) public comment period 
> <http://www.engadget.com/2015/10/07/fcc-wifi-router-lockdown/>to push 
> for open source Wi-Fi router firmware.
>
> The cybersecurity expertsasked the FCC 
> <http://motherboard.vice.com/read/heres-why-cybersecurity-experts-want-open-source-routers>on 
> Wednesday to require router makers to open-source their firmware, or 
> the basic software that controls its core functionality, as a 
> condition for it being licensed for use in the US. The request comes 
> amida wider debate 
> <http://arstechnica.com/information-technology/2015/09/fcc-accused-of-locking-down-wi-fi-routers-but-the-truth-is-a-bit-murkier/>on 
> how the FCC should ensure that Wi-Fi routers' wireless signals don't 
> "go outside stated regulatory rules" and causeharmful interference 
> <http://www.cisco.com/c/en/us/products/collateral/wireless/spectrum-expert-wi-fi/prod_white_paper0900aecd807395a9.html>to 
> other devices like cordless phones, radar, and satellite dishes./
http://hardware.slashdot.org/story/15/10/15/1620243/why-cybersecurity-experts-want-open-source-routers

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


[-- Attachment #2: Type: text/html, Size: 5396 bytes --]

  reply	other threads:[~2015-10-15 19:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 20:11 [Bloat] Another comment re FTC and weather radar from / David Collier-Brown
2015-10-08 20:20 ` David Collier-Brown
2015-10-08 21:36   ` Rosen Penev
2015-10-08 22:18     ` David Collier-Brown
2015-10-08 22:26   ` David Collier-Brown
2015-10-13 16:09 ` Simon Barber
2015-10-13 17:29   ` Matt Mathis
2015-10-13 18:18     ` Jonathan Morton
2015-10-13 18:19     ` Sebastian Moeller
2015-10-15 19:21       ` David Collier-Brown [this message]
2015-10-15 19:44         ` [Bloat] The press release is working Dave Taht
2015-10-18 23:13       ` [Bloat] Another comment re FTC and weather radar from / 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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=561FFCAF.5080305@rogers.com \
    --to=davec-b@rogers.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.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