If you tried to email me about the SSL error when commenting on a post, please be aware that I’m an idiot. I mistyped the contact email address (I have too bloody many domain, methinks). The correct address is
bear–at–bussjaeger–dot–us
Fortunately, a very determined person reached me via an alternate channel and let me know about my screw up.
Regarding the SSL error itself: I still haven’t managed to duplicate it.
Update:
I can partially duplicate the issue now. I only have so many OS/browser combinations available, so I can’t verify everyone’s set up.
1. Enable Javascripting. At a minimum, you must allow clairewolfe.com, wp.com, AND wordpress.com.
2. Enable SSL/TLS. The module that is actually generating the error is WordPress Jetpack. That must be enabled, and it attempts to default to the highest security protocol available. I don’t have anything that still uses SSL 2.0, but if your browser is trying to use it, that’s likely a big part of the problem. You’ll need to upgrade your browser since you should not be using SSL 2.0 (most security types will tell you not to use SSL 3.0, too).
If you’re using a Firefox variant, you can find general instructions on configuring SSL/TLS here:
https://support.mozilla.org/en-US/questions/967266
e-mail sent.
Maybe trying2b-amused could repeat the experiment, and verify JavaScript status? I, for example, typically have JavaScript “enabled” in the browser, but the NoScript plugin active.
For reference, maybe? http://www.clairewolfe.com/blog/2016/11/17/thursday-links-60/ — November 17, 2016 4:54 pm
jed: While I usually web surf with javascript turned off, I always assume it is required for commenting – I use a separate browser instance for the purpose. I’m trying to post this comment by extracting the URL for the comment form, then accessing it by pasting in the URL as http rather than https (in the unlikely event this comment actually gets posted) My “usual” browser allows me to bring up the form as such – we’ll see if it works . . .
Well, that’s all interesting, given that clairewolf.com doesn’t use https. So the scripty gunk being used employs SSL/TLS anyway? Piggybacking on a WordPress certificate? Well, can’t be entirely based on JavaScript, as it still POSTs somehow figuring out the form ACTION as an https target. Bleh! 🙂
Not sure I see the point of needing TLS to comment, given that the content comes back down unencrypted anyway. Somebody trying to be too fancy, I guess. Well, JMHO.
@t2b-a: Your browsing habits appear to mimic mine pretty well. My blog commenting has gone down quite a lot too.
@HWFIW: But but .. I want to be able to use Mosaic on an old DEC Alpha machine running Digital Unix. 😛
Screw Mosaic. I still have Lynx on one machine. [grin]
And I need to look around… I may have an old CoCo D board machine around here.
But yeah, clairewolfe.com doesn’t use SSL, but a script calls Jetpack (for antispam and other functions) which is on wordpress.com; that one wants SSL (TLS 1.2).