public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: archie.cobbs@gmail.com
Cc: cygwin@cygwin.com
Subject: Re: SSL not required for setup.exe download
Date: Mon, 11 Mar 2019 13:22:00 -0000	[thread overview]
Message-ID: <5C866129.1090605@tlinx.org> (raw)
In-Reply-To: <CANSoFxtRQrwe4TAWweswXC94d5hzyt--M6BaR4Dcg1yBVqh1GQ@mail.gmail.com>

On 3/10/2019 8:53 PM, Archie Cobbs wrote:
> On Sun, Mar 10, 2019 at 6:20 PM L A Walsh <cygwin@tlinx.org> wrote:
>   
>>>> It would be safer if http://www.cygwin.com always redirected you to
>>>> https://www.cygwin.com, where the page and the link are SSL.
>>>> Is there any reason not to force this redirect and close this security hole?
>>>>         
>>     I think the point is that if you redirect and a client can't
>> speak https, what happens?  Wouldn't they get an error that would
>> prevent them from using the site?
>>     
>
> I guess so. Can you name any such client?
>   
---
    Depends on the site, but for several months my browser would get
an error if I tried to goto my distro's website.  They implemented
hsts, but were using an insecure encryption that my browser had
enabled.  So now I try to only use their unencrypted channels for
distro-download, among other things.
 
As for others, and companies, such information is proprietary. 
Why would people advertise they are
using a browser that doesn't speak the latest fad?  If you are
asking for a mainstream browser, forget it, you'd have to
write your own software or make changes in one.  But any browser that
is open source could be configured to disable https on non-sensitive
sites, though eventually, intercepting only encrypted material and
ensuring that the browsers honor well-known CA's, that have
had keys requested under government security letters that forbid
any spread of such interception will get them most of what they
want.

    It's all in the name of protecting the citizens, of course...and
the children: think of the children (yeah, a bit of hyperbole here,
but that doesn't mean it can't be true).





--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2019-03-11 13:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10  4:54 Archie Cobbs
2019-03-10 13:35 ` Andrey Repin
2019-03-10 16:35   ` Archie Cobbs
2019-03-10 14:16 ` Brian Inglis
2019-03-10 16:40   ` Archie Cobbs
2019-03-11  3:51     ` Brian Inglis
2019-03-11  5:16       ` Mark Geisert
2019-03-11 11:50         ` Brian Inglis
2019-03-11 13:13         ` SSL should not be " L A Walsh
2019-03-11 13:44       ` SSL not " Archie Cobbs
2019-03-11 19:42         ` Brian Inglis
2019-03-11 22:14           ` Archie Cobbs
2019-03-11 22:59             ` Lee
2019-03-12 13:47               ` Archie Cobbs
2019-03-12 14:31                 ` Brian Inglis
2019-03-12 14:58                   ` Archie Cobbs
2019-03-15 12:25                     ` Brian Inglis
2019-03-28 18:13                       ` Erik Soderquist
2019-03-12 19:21                 ` Achim Gratz
2019-03-12 19:59                 ` Lee
2019-03-12  0:20             ` Andrey Repin
2019-03-12 19:45               ` Lee
2019-03-12 20:35                 ` Andrey Repin
2019-03-12 21:14                   ` Lee
2019-03-12 21:35                     ` Andrey Repin
2019-03-12 22:01                       ` Lee
2019-03-12 20:42                 ` Achim Gratz
2019-03-12 21:32                   ` Lee
2019-03-12 21:35                 ` Andrey Repin
2019-03-12 21:50                   ` Lee
2019-03-13 20:50                     ` Andrey Repin
2019-03-11 20:24         ` SSL should not be required for open source downloading L A Walsh
2019-03-10 14:16 ` SSL not required for setup.exe download Brian Inglis
2019-03-10 23:20   ` L A Walsh
2019-03-11  3:53     ` Archie Cobbs
2019-03-11 13:13       ` Brian Inglis
2019-03-11 13:22       ` L A Walsh [this message]
2019-03-11 13:39         ` L A Walsh

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

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

  git send-email \
    --in-reply-to=5C866129.1090605@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=archie.cobbs@gmail.com \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).