On Jun 7, 2018, at 8:24 PM, George <[email protected]> wrote:
>
> On Thu, 7 Jun 2018 14:31:22 -0400
> Richard Hipp <[email protected]> wrote:
>
>> As an experiment, I have reconfigured the sqlite.org website to
>> redirect all HTTP requests over to HTTPS.
>>
>> Let me know if this causes anybody any unnecessary grief. It is easy
>> enough to undo the setting.
>>
>
> Why can't we have both? I mean the software is in the public domain
> there is nothing to hide so what's the point of encrypting the site?
“Why HTTPS Matters,” published by Google, the entity that controls the
market-majority web browser and search engine, and thus is in a position to
determine how the web works to a large extent:
https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https
Additionally, SQLite’s web site *does* have sensitive information: official
tarballs, checksums, logins on the Fossil instance, etc. Someone who could
interfere with the integrity of SQLite could do a *lot* of damage worldwide.
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
