Comic Discussion > QUESTIONABLE CONTENT
Website Issue
Aziraphale:
I haven't had any problems up to this point, but when I went on the homepage just now, my antivirus (Norton) showed a warning message.
Rghfrgl:
--- Quote from: Carl-E on 06 Oct 2014, 20:12 ---Actually, I was getting a notice that my malware filter was catching something after being on the comic page for a couple of seconds, and yes, only in the archives. But seemingly on every page in the archive...
Well, every one I visited.
--- End quote ---
I, hopefully, didn't get any malware, but a long time ago when I was catching up on archives I got a lot of intrusive ads that other people were saying they weren't. I wonder if the providers intentionally target bad ads there where JJ is less likely to notice and veto them.
I think he should consider new ad providers. I'd love to actual turn adblock off for qc.
bhtooefr:
I'll note that I haven't seen any weirdness with Flash disabled by default (I have to click on something Flash for it to run), although I am on OS X (meaning most of the drive-by malware won't target me).
I disable adblock for questionablecontent.net, for what it's worth, so I'd suspect a malicious Flash ad specifically.
BenRG:
New Issue
I can't currently access the site properly because of some SSL certificate error. Chrome blocks me and I keep on having to reasure IE that I don't mind.
pwhodges:
Two things have happened simultaneously.
(1) Yesterday the forum was made accessible by https only; this means that (2) is a pain. Eighteen months ago, after a DoS attack on the comic server, the comic and forum were placed behind a CloudFlare cache, to mitigate the effects of such attacks in the future. A while later, I requested https access to the forum for reasons I won't elaborate on here; this was provided, but required removing the forum from the CloudFlare system because the free option (which is being used) didn't support https. CloudFlare has now added https to the free option, and so the forum has been moved back to it, and a new certificate that is not self-signed has been provided. BUT...
(2) Yesterday a major security breach in the old SSL3 protocol was announced (called Poodle). Many servers are now disabling SSL3 to force the use of the more modern TLS protocol. However, some clients still default to SSL3, and may not be graceful about it no longer being available. So, I have one machine at home that can't see the forums today, and another that can; Tapatalk on the iPhone is OK, but not on Android; I have problems with Thunderbird with one university's mail server; there will be a new release of FireFox to handle this shortly (v34); the list goes on and on.
However, I'm puzzled by your seeing SSL certificate errors (I am not, in either of those browsers), because there is now a proper certificate as opposed to the previous self-signed one that would have generated that warning. In this case I suspect that you have been forced to https because of the forum change, but that the CloudFlare server that you are going through still has the old certificate cached. I suggest you either wait for a day or so for it to clear, or delete the self-signed certificate from your certificate store and see if you then get a new one.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version