Sebastian Pipping wrote:
On 11/28/2011 02:41 AM, Mike Edenfield wrote:
Since I didn't write it at work it's all yours. :)
Thanks. Posted here:
https://blog.hartwork.org/?p=1516
Best,
Sebastian
*cough cough* Maybe a good burp too. I get this:
This Connection is Untrusted
You have asked SeaMonkey to connect
securely to blog.hartwork.org, but we can't confirm that your connection
is secure.
Normally, when you try to connect securely,
websites will present trusted identification to prove that you are
going to the right place. However, this website's identity can't be
verified.
What Should I Do?
If you usually connect to
this website without problems, this error could mean that someone is
trying to impersonate the website, and you shouldn't continue.
Technical Details
I Understand the Risks
If you understand what's going on, you
can tell SeaMonkey to start trusting this website's identification.
Even if you trust the website, this error could mean that someone is
tampering with your connection.
Don't add an exception unless
you know there's a good reason why this website doesn't use trusted
identification.
Just thought I would let you know in case you don't see that on your end.
Dale
:-) :-)
P. S. I guess I trust you. lol
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
