6470164c19
Changelog: New Features security-libs/javax.net.ssl ➜ Support for Customization of Default Enabled Cipher Suites via System Properties The system property jdk.tls.client.cipherSuites can be used to customize the default enabled cipher suites for the client side of SSL/TLS connections. In a similar way, the system property jdk.tls.server.cipherSuites can be used for customization on the server side. The system properties contain a comma-separated list of supported cipher suite names that specify the default enabled cipher suites. All other supported cipher suites are disabled for this default setting. Unrecognized or unsupported cipher suite names specified in properties are ignored. Explicit setting of enabled cipher suites will override the system properties. Please refer to the "Java Cryptography Architecture Standard Algorithm Name Documentation" for the standard JSSE cipher suite names, and the "Java Cryptography Architecture Oracle Providers Documentation" for the cipher suite names supported by the SunJSSE provider. Note that the actual use of enabled cipher suites is restricted by algorithm constraints. Note also that these system properties are currently supported by the JDK Reference Implementation. They are not guaranteed to be supported by other implementations. Warning: These system properties can be used to configure weak cipher suites, or the configured cipher suites may become more weak over time. We do not recommend using the system properties unless you understand the security implications. Use them at your own risk. See JDK-8162362 Bug Fixes This release contains fixes for security vulnerabilities described in the Oracle Critical Patch Update. For a more complete list of the bug fixes included in this release, see the JDK 8u192 Bug Fixes page. Security bugs: CVE-2018-3183 CVE-2018-3209 CVE-2018-3169 CVE-2018-3149 CVE-2018-3211 CVE-2018-3180 CVE-2018-3214 CVE-2018-3157 CVE-2018-3150 CVE-2018-13785 CVE-2018-3136 CVE-2018-3139
19 lines
778 B
Text
19 lines
778 B
Text
$NetBSD: patch-common_autoconf_boot-jdk.m4,v 1.3 2018/12/12 14:22:11 ryoon Exp $
|
|
|
|
--- common/autoconf/boot-jdk.m4.orig 2018-12-09 09:50:43.000000000 +0000
|
|
+++ common/autoconf/boot-jdk.m4
|
|
@@ -334,14 +334,12 @@ AC_DEFUN_ONCE([BOOTJDK_SETUP_BOOT_JDK_AR
|
|
# Maximum amount of heap memory.
|
|
# Maximum stack size.
|
|
if test "x$BOOT_JDK_BITS" = x32; then
|
|
- JVM_MAX_HEAP=768M
|
|
STACK_SIZE=768
|
|
else
|
|
# Running Javac on a JVM on a 64-bit machine, takes more space since 64-bit
|
|
# pointers are used. Apparently, we need to increase the heap and stack
|
|
# space for the jvm. More specifically, when running javac to build huge
|
|
# jdk batch
|
|
- JVM_MAX_HEAP=1600M
|
|
STACK_SIZE=1536
|
|
fi
|
|
ADD_JVM_ARG_IF_OK([-Xmx$JVM_MAX_HEAP],boot_jdk_jvmargs_big,[$JAVA])
|