Обязательно проверяйте все загружаемые программы с помощью антивируса. Если у вас возникли проблемы с загрузкой, обязательно напишите нам. Мы сразу все исправим. Мы не осуществляем техническую поддержку размещенных на сайте программ. Пожалуйста используйте эту форму только для сообщения об ошибках на swdb. Информация по размещению рекламы здесь: Java JRE программная среда необходимая для запуска приложений написанных с испоьзованием языка программирования Java. Mac OS X Разрядность ОС: О проекте Размещение рекламы. Проект Студии Электронных Развлечений. Ваше сообщение не может быть отправлено.
This page highlights changes impacting end users for Java 7 releases. More information about changes can be found in the release notes for each release. The expiration date for 7u79 is July 14, Java expires whenever a new release with security vulnerability fixes becomes available. For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u79 on August 14, After either condition is met new release becoming available or expiration date reached , Java will provide additional warnings and reminders to users to update to the newer version. This release contains fixes for security vulnerabilities. For more information, see Oracle Java SE Critical Patch Update Advisory. For a list of bug fixes included in this release, see JDK 7u79 Bug Fixes page. The expiration date for 7u75 is April 14, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u75 on May 14, For a list of bug fixes included in this release, see JDK 7u75 Bug Fixes page. The expiration date for 7u71 is January 20, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u71 on February 20, For a list of bug fixes included in this release, see JDK 7u71 Bug Fixes page. The expiration date for 7u67 is October 14, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u67 on November 15, For a list of bug fixes included in this release, see JDK 7u65 Bug Fixes page. The expiration date for 7u65 is October 14, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u65 on November 15, The expiration date for 7u60 is July 15, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u60 on August 15, For a list of bug fixes included in this release, see JDK 7u60 Bug Fixes page. The expiration date for 7u55 is July 15, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u55 on August 15, The expiration date for 7u51 is April 15, For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE version 7u51 on May 15, The expiration date for 7u45 is February 14, After this date, Java will provide additional warnings and reminders to update to the newer version. The expiration date for 7u40 is December 10, The expiration date for 7u25 is November 15, The expiration date for 7u21 is July 18, For more information, see Oracle Security Alert for CVE When updating from Java 6, the update mechanism will not only install the latest version of Java 7 but will also remove the highest version of Java 6 on the system. This change will happen when the system is updated via the auto-update mechanism or by checking from updates directly from the Java Control Panel. The default security level for Java applets and web start applications has been increased from Medium to High. This affects the conditions under which unsigned sandboxed Java web applications can run. Previously, as long as you had the latest secure Java release installed applets and web start applications would continue to run as always. With the High setting the user is always warned before any unsigned application is run to prevent silent exploitation. Starting with 7u10, all JREs will contain a hard-coded expiration date. The expiration date is calculated to end after the scheduled release of the next Critical Patch Update. If users have a version of Java on their systems that is below the security baseline, a warning message is displayed before an application or an applet can be run. For more information, please see Oracle Java SE Critical Patch Update advisory. Java 7 Release Highlights This article applies to: For more information, refer to Timezone Data Versions in the JRE Software. Improve jar file handling. See not public. Java Expiration Date The expiration date for 7u79 is July 14, Bug Fixes This release contains fixes for security vulnerabilities. SSLv3 is disabled by default Starting with JDK 7u75 release, the SSLv3 protocol Secure Socket Layer has been deactivated and is not normally available. Please see the jdk. If SSLv3 is absolutely required, the protocol can be reactivated by removing "SSLv3" from the jdk. Changes to Java Control Panel Starting with 7u75 release, SSLv3 protocol is removed from Java Control Panel Advanced options. If the user needs to use SSLv3 for applications, re-enable it manually as follows: Enable SSLv3 protocol on JRE level: Enable SSLv3 protocol on deploy level: Java Expiration Date The expiration date for 7u71 is January 20, Java Expiration Date The expiration date for 7u67 is October 14, In this release, a new Java Control Panel JCP option to disable sponsors is available. To use this option, go to the JCP Advanced tab, and check or uncheck Suppress sponsor offers when updating Java. This option is applicable to and bit Windows operating systems. New JAXP processing limit property - maxElementDepth A new property, maxElementDepth , is added to provide applications the ability to set limit on maximum element depth in an xml file that they parse. This may be helpful for applications that may use too much resources when processing an xml file with excessive element depth. Limit the maximum element depth Value: Negative numbers are treated as 0. Using RMI from a restricted environment may cause a NullPointerException If an application uses RMI and runs in a restricted environment i. Java Plugin, Java Web Start , it may not work. In particular, if you run a UI from an RMI callback, a NullPointerException is likely to be thrown. ORBSingletonClass loading no longer uses context class loader The system property org. In this release, the handling of this system property has been reverted to match the behavior found in JDK versions prior to 7u55 release, i. The change is made to support applications which depend on this behavior. Note that this change is applicable to 8u20, 7u65, 6u85 and 5. Java Expiration Date The expiration date for 7u65 is October 14, To ensure that expiration check is disabled, use the following Java Web Start command: See Deployment Configuration File and Properties for more information. New flags added to Java Management API The flags MinHeapFreeRatio and MaxHeapFreeRatio have been made manageable. This means they can be changed at runtime using the management API in Java. Support for these flags have also been added to the ParallelGC as part of the adaptive size policy. Java Expiration Date The expiration date for 7u60 is July 15, Bug Fixes For a list of bug fixes included in this release, see JDK 7u60 Bug Fixes page. For more information, see JAR File Manifest Attributes for Security documentation. Disabling Sponsor Offers in the Java Installer During the installation of Java, users may be presented with the option of downloading and installing sponsor offers, such as browser add-ons, or security software. Manually download the 32bit online installer for 7u55 to your local machine. A list of matches will appear. Navigate to the folder containing the downloaded installer, e. Note that sponsor offers, and therefore this functionality, is only applicable to online 32bit JRE installers and Auto Update mechanisms for the Windows operating system. Java plugin compatibility with Windows 8. You should no longer see any warning related to EPM when trying to run an applet in Internet Explorer IE. There is a special case for bit Windows - EPM requires both bit and bit Plug-in installed. Please make sure you have both bit and bit JRE installed, otherwise there will be a warning from IE, but Java Plug-in will still run under EPM. Java Expiration Date The expiration date for 7u55 is July 15, It is recommended that users restore security prompts every 30 days to ensure better protection. A trust decision occurs when the user has selected the Do not show this again option in a security prompt. To show the prompts that were previously hidden, click Restore Security Prompts. When asked to confirm the selection, click Restore All. The next time an application is started, the security prompt for that application is shown. See Restore Security Prompts under the Security section of the Java Control Panel. Exception Site List The Exception Site List feature allows end users to run Java applets and Java Web Start applications also known as Rich Internet Applications that do not meet the latest security requirements. Rich Internet Applications that are hosted on a site in the exception site list are allowed to run with the applicable security prompts. See the Exception Site List FAQ for more information. Other Changes Update jarsigner to encourage timestamping Timestamping for a signed jar is now strongly recommended. The Jarsigner tool will print out an informational warning at signing or verifying when timestamp is missing. For more information see Signing JAR Files. The jarsigner tool prints out more messages when there are severe warnings and -strict is on. Read the tooldoc link for details. Java Expiration Date The expiration date for 7u51 is April 15, Protections Against Unauthorized Redistribution of Java Applications Starting with 7u45, application developers can specify new JAR Manifest file attributes which: If the attribute is not present or if the attribute and location do not match, then the location of the JNLP file or HTML page is displayed in the security prompt shown to the user. Developers can refer to JAR File Manifest attributes for more information. Java Expiration Date The expiration date for 7u45 is February 14, Unlike previous versions, users cannot suppress the security dialog for an unsigned application and will have to select the option, I accept the risk and want to run this app each time to run the unsigned application. New Security Warning for Unsigned and Self-signed Applications Message added Running unsigned applications like this will be blocked in a future release because it is potentially unsafe and a security risk. In order to avoid the compatibility issue, users who use X. User Experience Enhancements Retina Display support on Mac OS X Other Changes Bug fix: Aborting the update after clicking Update on the Java version is insecure warning message forwards all applets to java. When an older Java version is installed on the system, launching a web page with an applet prompts the user with Java version is insecure message. If the user clicks on the Update button on the message but later aborts the update process, the user is automatically redirected to java. This is not expected behavior. The issue is fixed in the 7u40 release. Expired but otherwise valid certificate are not blocked at Very High Security Level. Deployment Rule Set for System and Desktop Administrators Starting with 7u40, a new Deployment Rule Set feature is available for enterprises that manage their Java desktop environment directly, and provides a way for enterprises to continue using legacy business applications in an environment of ever-tightening Java applet and Java Web Start application security policies. Option to disable the Java version is out of date warning For businesses that manage the update process centrally, a new deployment property can be used to disable the Java version is out of date warning. For more information, see Deployment Configuration File and Properties. Java Expiration Date The expiration date for 7u40 is December 10, Certificate Revocation Before signed Java applets and Java Web Start applications are run, the signing certificate is checked to ensure that it has not expired or been revoked. Advanced options in the Java Control Panel can be set to manage the checking process. New JAR Manifest File Attributes 7u25 release introduces the permissions and codebase attributes in the JAR Manifest File. Application developers can use these attributes to verify that the application is requesting the correct permissions level and is accessed from the correct location. LiveConnect Blocked under Some Conditions LiveConnect calls from JavaScript to Java API are blocked when the Java Control Panel security slider is set to Very High level, or when the slider is at the default High level and the JRE has either expired or is below the security baseline. Java Expiration Date The expiration date for 7u25 is November 15, Java Expiration Date The expiration date for 7u21 is July 18, This mode can be set in the Java Control Panel or on Microsoft Windows platform only using a command-line install argument. The ability to select the desired level of security for unsigned applets, Java Web Start applications, and embedded JavaFX applications that run in a browser. Four levels of security are supported. This feature can be set in the Java Control Panel or on Microsoft Windows platform only using a command-line install argument. New dialogs to warn you when the Java Runtime Environment JRE is insecure either expired or below the security baseline and needs to be updated. Java Expiration Date Starting with 7u10, all JREs will contain a hard-coded expiration date. Java 7 and Java 8 Releases by Date Java 8 release changes.
https://gist.github.com/4a388489d988758c285221af816d38d4
https://gist.github.com/a1175ec523642675fb70df85bbe9d841
https://gist.github.com/3f0161b83599c0df6188e91eeaa4e087