Adobe/Secunia Problem?

Java/Secunia Problem?

I am receiving this when I attempt to access Secunia:





My operating system is Windows XP Pro, SP3. For java I have installed jre-6u24-windows-i1586. According to what I can find that is supposed to be the latest java version. I visit the Secunia website at least on a weekly basis and I have never had any problems until yesterday. Anyone have any idea what this is?

As always I will appreciate all replies and would thank you in advance.

John

 

Re: Java/Secunia Problem?

Someone? Anyone? Hazard a guess, something would be better than nothing. I have no idea but then I don't have that much experience.

John

 

I'm not understanding something. Did you run Secunia online service to check for outdated applications? It requires Java, and that message appeared?

 

mOOnblOOd,

That is exactly what happened. I access Secunia OSI at least once a week looking for updates.

Do you know if jre-6u24-windows-i586.exe is a 32 bit or 64 bit file. When I go to java.com and let the website check to see if I have the right version it indicates I do. I am able to access other websites that require java, example: US Time Clock

I have asked for help on the Secunia forum but so far I have struck out.

It appears that an "OCSP Responder" checks the certificate for accuracy. I did find that out. But other than that I am at a complete loss.

Thanks very much for replying.

John

 

I'm not that much into Java, as I do not use it, and therefore I never felt compelled to know exactly how it treats Java applets. But, from the image you provided, my very wild guess is that Secunia's Java applet is not digital signed... or not part of Java's known publishers (If it has such list?).

Basically, Java is letting you know that Secunia's Java applet isn't signed (or isn't part of its known list of trusted publishers, if it has such list), and therefore is treating it as unknown code and restrict its action in the system.

But, you say it hasn't happened before, so my guess is as blind as yours, and only Secunia would be able to provide a proper answer why it's happening, if the problem is on their side.

Maybe someone else will shed a few more lights on it, and report if they have the same problem.

-edit-

It could also be some problem in the way Secunia's service lets Java known its signed

 

This morning everything is back to the way it should be. I believe mOOnblOOd was right and that my problem had something to do with the certificate. I try to keep my programs up to date and hated to think that I would no longer be able to access Secunia. I want to thank everyone who tried to help me.

John