|
|
2010-04-21
, 01:39
|
|
Posts: 336 |
Thanked: 610 times |
Joined on Apr 2008
@ France
|
#2
|
| The Following User Says Thank You to CrashandDie For This Useful Post: | ||
|
|
2010-04-21
, 07:12
|
|
Posts: 49 |
Thanked: 15 times |
Joined on Mar 2010
@ Scotland
|
#3
|
First of all, you shouldn't be trusting certificates on a "per-certificate" basis. Trust the CA, and be done with it.
Secondly, a certificate shouldn't have the same serial number as another one from the same CA. This goes against RFC 2459, and you should contact the website owner to make sure they look into this. The only way for this to happen is by having faulty generation services (such as a broken CA), or a broken self-signed algorithm.
Lastly, there is nothing we can do: just go through all the certificates, and delete the right one. There is no magic trick.

|
|
2010-04-21
, 07:29
|
|
Posts: 336 |
Thanked: 610 times |
Joined on Apr 2008
@ France
|
#4
|

|
|
2010-04-21
, 12:49
|
|
Posts: 49 |
Thanked: 15 times |
Joined on Mar 2010
@ Scotland
|
#5
|
HammY,
What application did you use to generate the certificate? You might want to purchase an SSL certificate -- they're seriously cheap these days.
Also, if this is inside a company, and you control the distribution of the CA certs (you can push them through Windows GPO), you may want to deploy your own CA, and push that to all your clients. Windows Server 2003 Enterprise comes with Microsoft Certificate Authority.
It's a simple CA, but it does the job for most things. Based on your security needs, you may not need to have it signed by anyone else (= no fees).
You may want to expose your requirements a bit more, I can advise
Source: I'm a security expert, specialised in PKI.
|
|
2010-10-06
, 12:06
|
|
Posts: 14 |
Thanked: 1 time |
Joined on Sep 2009
|
#6
|
|
|
2010-10-06
, 13:02
|
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#7
|
|
|
2010-10-08
, 09:58
|
|
Posts: 14 |
Thanked: 1 time |
Joined on Sep 2009
|
#8
|
|
|
2010-10-08
, 11:07
|
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#9
|
|
|
2010-10-09
, 14:28
|
|
Posts: 14 |
Thanked: 1 time |
Joined on Sep 2009
|
#10
|
I connect to a SSL site which uses a self-signed certificate which has just expired. and a new self-signed certificate has been re-created. My N900 was previously connecting fine - I suspect I installed the certificate or added some trust/exception, but I can't recall.
Now when I connect, the inbuilt browser & Firefox both complain about an invalid certificate saying that the certificate contains the same serial number as another certificate issued by the CA. (true)
I have scanned through all the certificates in "Certificate Manager" hoping to find and delete the old certificate, but I can't find it - or don't recognise it.
I had the same problem with the SSL site on my desktop with Firefox, but I found and deleted the certificate and this solved the problem.
Anyone got any suggestions for fixing same problem on N900 ?
Last edited by HammY; 2010-04-21 at 00:30.