![]() |
|
|
#45 |
|
Oct 2017
++41
53 Posts |
There is really no good reason to stick with http, it has basically become obsolete. Additionally, https allows http2 for low latency page rendering.
And google degrades page ranking for http-only sites. |
|
|
|
|
|
#46 |
|
Aug 2002
Buenos Aires, Argentina
25268 Posts |
The next to last graph in https://transparencyreport.google.com/https/overview shows that more than half of Web pages viewed in the world are secured by HTTPS and it is increasing.
They use Chrome to gather the statistics, but since most people use that browser, I believe that there should be a little difference with respect to the usage by all Web browsers. |
|
|
|
|
|
#47 |
|
∂2ω=0
Sep 2002
República de California
101101011101112 Posts |
FYI to those folks who kindly made suggestions re. my upgrading from my current soon-to-be-completely-useless-for-https FF v22: I ended up up-versioning to v37, the latest FF version which runs under my old MacOS 10.6,8, which I refuse to update because Apple massively crapified the OS with iOS-influenced crap starting with 10.7. (I have a backup macbook running 10.7.5 and pray I never need it because everything runs so godawfully slow.)
I'm not sure why I missed this previously (ended up going with an image-blocking 3rd-party add-on which was annoying because if I enabled images for any given article, it insisted on doing same for every single other open page and tab), but a little online digging turned up how to access the no-longer-exposed-in-user-options-menu image-render toggle via about:config -> permissions.default.image [change from default 1 (display all) to 2 (block all) or 3 (block only 3rd-party)]. Also needed the interwebs to tell me how to disable the annoying user-tracking new-tab 'tiles' feature. With those fiddles, so far, so good. |
|
|
|
|
|
#48 |
|
Oct 2017
++41
53 Posts |
As I said earlier, you really shouldn't use an old version of firefox, as they have known vulnerabilities, which are already being exploited in the wild, so it may be sufficient to visit a contaminated website and you have a virus/worm/spyware/whatever on your computer.
You should use Palemoon instead as suggested by S485122, or Firefox ESR; any version that gets regular security updates. But this is getting offtopic here. |
|
|
|
|
|
#49 | |
|
∂2ω=0
Sep 2002
República de California
103·113 Posts |
Quote:
|
|
|
|
|
|
|
#50 | |
|
"Forget I exist"
Jul 2009
Dumbassville
26×131 Posts |
Quote:
|
|
|
|
|
|
|
#51 | |
|
∂2ω=0
Sep 2002
República de California
103·113 Posts |
Quote:
|
|
|
|
|
|
|
#52 | |
|
Just call me Henry
"David"
Sep 2007
Cambridge (GMT/BST)
23×3×5×72 Posts |
Quote:
|
|
|
|
|
|
|
#53 |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
37·263 Posts |
Could we please have a definitive statement from the forum owner(s)?
It has been clearly communicated that users of this forum would like MersenneForum to be served over HTTPS. Is there an action plan for this? Is there a show stopper preventing this? With all due respect, Mike (AKA Xyzzy) acknowledges that he is not terribly strong in SysAdmin. Perhaps he could gather a group he trusts to migrate the forum to HTTPS? Statements, rather than silence, would be appreciated....
|
|
|
|
|
|
#54 | ||
|
Dec 2012
The Netherlands
170210 Posts |
Quote:
Quote:
The biggest threats the forum has faced up to now have been from DDoS attacks. TLS would not help there - if anything, it would make them worse. In reality, there are very few truly independent implementations of TLS, and virtually all of them are so bloated that they are weak, either accidentally or deliberately. Pretending to be secure when you are not is not a good way to go. |
||
|
|
|
|
|
#55 |
|
Oct 2006
Berlin, Germany
617 Posts |
It sounds to me as you would let the door to your flat open because any lock can be broken.
|
|
|
|
![]() |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Why is https://www.mersenne.org so damn buggy? | jxsl13 | Information & Answers | 2 | 2017-02-22 03:06 |
| https and www etc etc | Uncwilly | Forum Feedback | 1 | 2012-03-12 20:46 |
| https access to www.mersenne.org failed | LLL | PrimeNet | 17 | 2008-12-26 20:34 |