Security settings blocked application launch with outdated or outdated Java version

Greetings.

I am facing a Java error that is actually giving me a nightmare.

It says:

"Application blocked by security settings"

"Security settings blocked application launch with outdated or outdated Java version"

Java version: 1.7_25 (recommended for my job, not old one I believe)

The workaround I followed (which didn't work):

  • Reduced security level to medium.
  • Cleared browser cache and cookies.
  • Several options were checked on the Advanced tab of the Java Control Panel, for example:

    General: Allow the user to grant permissions to the signed content.

  • Java Cache has also been cleared.
Even after following the above workarounds one by one the issue does not go and there is no list of exceptions in the security tab (information only).

Most of the bug-related issues will come after the security level is lowered to the environment level. But I have not.

Hope someone can help me. Always be grateful.

Thank!

AK

+3


source to share


5 answers


"[Java 1.7.0_25] is recommended for my job, not the old one I believe."

Unfortunately, your belief is wrong. As of now (when you asked the question) Java 1.7.0_u25 is over a year old and there have been 4 security versions released since this version, starting with this version.

In fact, you probably have no option other than updating ... if you want to use this app through your web browser. Version checking cannot be overridden (AFAIK) for Java applications launched through your web browser and / or using Java Web Start. It's also good.


So how does this go with your "work recommendation"?

You need to talk to system administrators or security people or those who made this recommendation. Under normal circumstances, it is bad to use an outdated version of Java, especially if you enable it in your web browser. This leaves you open to all kinds of security counterfeits.

It might seem that there is a good reason for this "recommendation"; for example, a compatibility issue for some other Java-based applications that they need to support. If so, you have a tough choice:



  • You can upgrade to the latest Java 1.7 and risk not using applications that (in fact) require an older version of Java.

  • You cannot update and abandon the idea of ​​using the application that is giving you problems.

  • You install a second web browser and configure it to use the latest version of Java, and the other to use the older "recommended" version. It might be messy, but (at least) Java is designed to have multiple JREs or JDKs installed at the same time on your system.


... but my application (which I am working on unfortunately supports up to this version (i.e. 7_25).

Developing an application that only runs on older versions of Java doesn't seem like a good business strategy.

But if you have a good reason, you should install BOTH 1.7.0_25 and later on your system ... and use that for your development and the other for running web applications.

Or, if not attractive, use different virtual machines or different physical machines to do the different kinds of work you need to do.

+3


source


"Security settings blocked the application from launching with an outdated or expired Java version

Java version: 1.7_25 (Recommended for my job, not the old one).

From Java SE Download :



Java SE 7u67 This release covers the regression introduced in the latest security update. Oracle strongly recommends that all Java SE 7 users upgrade to this version.

In the latest version 1.7, you are not .

Since version 1.7.25, 7 has been released .

+2


source


The actual problem may not be outdated Java, but the jar sign / manifest / jnlp applicator.

Workaround:

1.Install the latest JRE from Oracle website.

2.Uncheck "Enable Java content in browser" in old java / jre (javacpl.exe)

3. Make sure the applet works correctly with the latest JRE

4.Turn on "Enable Java content in browser" in the latest JRE and check it in the old JRE

0


source


I had the same problem, I lowered the security level from high to medium and allowed the app to run at risk, it worked for me.

0


source


I recommend adding the site URL to the list of security exclusions without compromising overall security.

0


source







All Articles