Forum Settings
       
Reply To Thread

[Allakhazam] SSL Certificate Expired? (was forum=10)Follow

#1 Oct 19 2009 at 11:18 AM Rating: Decent
**
602 posts

I've been getting this whenever I try to login at this site. I've added an exception but I'm still wondering. Has anyone else got this message? I know some ssl certificates expire however; it usually can mean a big problem. There's a common trick called man-in-the-middle attacks where someone will set up a computer between allakhazam and the user for example. And they'll sniff all the SSL connections and log them/crack them for information.

I would think this isn't happening to allakhazam. And I know there is no arp poisoning going on at my residence as it's not a wireless connection and only my computer is connected. I'm just putting a warning out, maybe I'm the only one; if that's the case and it's not on your end. Then I should probably call up my ISP and alert them perhaps.

Anyone else get the warning?
#2 Oct 19 2009 at 11:24 AM Rating: Good
***
1,099 posts
Having a look at the cert, its valid from the 13/10/09 to 18/10/09 so its a valid certificate. Go to https://secure.allakhazam.com/ and take a look at the certificate.
#3 Oct 19 2009 at 11:28 AM Rating: Default
**
559 posts
Change the date/time on your computer (or router) to reflect the current date/time and you should stop getting that message.
#4 Oct 19 2009 at 11:29 AM Rating: Decent
**
602 posts
Yeah I've looked at the certificate but Allakhazam is the only secure site that has popped that warning on my end so I'm just wondering why it's doing that. I can go to any other secure site and it let's me through without any warning. And this is a fresh install of Firefox. Haven't changed any settings or anything. I had to manually add exception and click on Get Certificate. I'll provide screenshots when I reproduce it.

Certificate Warning Popup

Pressed Add Exception then this:

Add Security Exception Screen

Notice the 'Certificate is not trusted'

And the next screen shot is pretty much the same but I clicked on Get Certificate. The next screenshot is the information on the certificate:

Certificate Itself


The date is right on my router and my computer. Both are set by internet time servers so there is no discrepancy in that department. Maybe I should just ignore the whole situation but there has to be something going on and I'm a problem solving maniac :-P Need to figure this out. Funny that IE doesn't give a warning and Firefox does. Maybe it's nothing. And just firefox itself. Let me disable noscript and adblock and try.

Nope same message unfortunately even with noscript/adblock turned off.

Edited, Oct 19th 2009 1:51pm by Excenmille
#5 Oct 19 2009 at 12:12 PM Rating: Excellent
***
1,807 posts
Has nothing to do with the date. The first screenshot you posted tells you that the issuer certificate is unknown. Why that happens to be, I don't know, since it appears you are getting a legit alla cert (fingerprints match what I see, and my firefox thinks everything is ok) which has been issued by VeriSign.

Try to find out why firefox doesn't like the VeriSign cert, and you should find what the problem is. Maybe check to see that everything is up to date on your end.
#6 Oct 19 2009 at 12:22 PM Rating: Good
***
1,099 posts
You may need to update your root certificates. The sort of error you are seeing would be for a self signed certificate where the browser cannot confirm the identity of the issuer. To check if you have it, you need to open your Internet Options, quickest way is to open IE and go tools > Options > Content > Publishers, click "Trusted Root Certification Authorities" and scroll down to the bottom where you *should* see VeriSign Class 3, that is the root certificate authority which signed the certificate.

You can download the latest root certificates from here - requires you to validate windows which should give you verisign back.

quick edit - yes I know they are using Firefox, but IE/Chrome both use the built in Windows store for certificates, so I would assume that FF does also.

Edited, Oct 19th 2009 2:23pm by Lexxuk
#7 Oct 19 2009 at 1:00 PM Rating: Good
**
559 posts
This can also sometimes be caused by proxy and/or firewall.
#8 Oct 20 2009 at 6:23 AM Rating: Good
***
1,428 posts
Lexxuk wrote:
Having a look at the cert, its valid from the 13/10/09 to 18/10/09 so its a valid certificate. Go to https://secure.allakhazam.com/ and take a look at the certificate.


You posted this message on 10-19-09 and the date format in message was dd/mm/yy so the date range was actually Oct 13, 2009 to Oct 18, 2009. So the date ended before you posted. Either way. yes there is an issue with certificates that people had reported and they had expired. Now if looking at the screenshot that was proviced in the thread it has dates of 10/12/2009 to 10/17/2010

Edited, Oct 20th 2009 8:28am by shibaaa
#9 Oct 20 2009 at 6:39 AM Rating: Excellent
Spankatorium Administratix
*****
1oooo posts
The certificate has been updated and is fine. We have no other issues reported other than this one and have been trying hard to figure out the issue.
____________________________

#10 Oct 20 2009 at 6:47 PM Rating: Good
**
315 posts
Mine has still been doing it as well since the first reports hit the feedback forum. I have just been adding it manually since then.
#11 Oct 21 2009 at 4:17 AM Rating: Excellent
Guru
***
1,274 posts
I tried making a change on the server that may help. I can't duplicate the problem, so I'm not sure if it worked or not.
#12 Oct 21 2009 at 5:58 PM Rating: Good
**
315 posts
Worked for me!
#13 Oct 21 2009 at 8:14 PM Rating: Excellent
Spankatorium Administratix
*****
1oooo posts
Awesome! Anyone else?
____________________________

Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 187 All times are in CST
Anonymous Guests (187)