From: Michael Richardson <mcr@sandelman.ca>
To: dpreed@reed.com
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Nokia decrypts user's HTTPS to compress to improve speed
Date: Thu, 10 Jan 2013 10:44:47 -0500 [thread overview]
Message-ID: <17284.1357832687@sandelman.ca> (raw)
In-Reply-To: <1357829880.67618376@apps.rackspace.com>
>>>>> "dpreed" == dpreed <dpreed@reed.com> writes:
dpreed> However, it points out that there is a man-in-the-middle
dpreed> problem with HTTPS alone. Your phone's browser should be
dpreed> checking the certificates more rigorously than it does. It
dpreed> can do that quite easily, and I think the destination can do
dpreed> that in Javascript that comes with the pages.
The problem is that you have to trust someone, and in this case, if you
have a nokia phone (I guess, a windows phone), then you have to trust
it. The browser could lie to the Javascript just as easily.
BTW: microsoft lets one force new trusted root CAs into desktops via
Active Directory "group policy", and they've been doing this exact thing
for years in order to enable "virus scanning"
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2013-01-10 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 14:46 Maciej Soltysiak
2013-01-10 14:58 ` dpreed
2013-01-10 15:44 ` Michael Richardson [this message]
2013-01-10 16:50 ` Maciej Soltysiak
2013-01-10 21:51 ` dpreed
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=17284.1357832687@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
/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