From: dpreed@reed.com
To: "David Lang" <david@lang.hm>, "Joel Wirāmu Pauling" <joel@aenertia.net>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Random thought - reactions?
Date: Sun, 17 Dec 2017 21:26:26 -0500 [thread overview]
Message-ID: <mhc18hgbsq3cr00tbmrhsmmn.1513563986058@email.android.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1712151513070.14233@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
Good point about separating concerns. I would suggest that home router to POP encryption would satisfy the first. End to end encryption can be done at the endpoints on, as it should be.
The home router to POP link need not be tappable for the NSA for it to spy. It is not end to end.
Sent from Nine
________________________________
From: David Lang <david@lang.hm>
Sent: Friday, December 15, 2017 6:14 PM
To: Joel Wirāmu Pauling
Cc: David Reed; cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Random thought - reactions?
There are two different issues here.
1. the last mile ISP plays games with the traffic for their own benefit (and
thir competitors detriment)
2. the government wants to spy on everybody
It's possible for the VPN tunnel providers to solve problem #1 without solving
problem #2
k
[-- Attachment #2: Type: text/html, Size: 1871 bytes --]
prev parent reply other threads:[~2017-12-18 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 17:18 dpreed
2017-12-15 19:32 ` tapper
2017-12-15 21:11 ` dpreed
2017-12-15 22:45 ` Joel Wirāmu Pauling
2017-12-15 23:14 ` David Lang
2017-12-18 2:26 ` dpreed [this message]
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=mhc18hgbsq3cr00tbmrhsmmn.1513563986058@email.android.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=joel@aenertia.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