security-dev
Thread
Date
Earlier messages
Messages by Thread
RFR: 8337713: RISC-V: fix typos in macroAssembler_riscv.cpp
SendaoYan
RFR: 8298387: Implementing ML-DSA signature algorithm
Ben Perez
RFR: 8305406: Add @spec tags in java.base/java.* (part 2)
Hannes Wallnöfer
RFR: 8249831: Test sun/security/mscapi/nonUniqueAliases/NonUniqueAliases.java is marked with @ignore
Fernando Guallini
Several question about JEP 486
Lim
Re: Minor OpenJDK 11 update changed ObjectIdentifer constructor to private
Alan Bateman
JEP 486: Question about CodeSource
Thiago Henrique Hupner
Re: JEP 486: Question about CodeSource
Sean Mullan
RFR: 8340116: test/jdk/sun/security/tools/jarsigner/PreserveRawManifestEntryAndDigest.java can fail due to regex
Fernando Guallini
RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base
Eirik Bjørsnøs
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base
Stuart Marks
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]
Eirik Bjørsnøs
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base
Stuart Marks
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base
Eirik Bjørsnøs
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base
Stuart Marks
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]
Eirik Bjørsnøs
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]
Jaikiran Pai
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]
Stuart Marks
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]
Eirik Bjørsnøs
Re: RFR: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base [v2]
Jaikiran Pai
Integrated: 8341243: Use ArraySupport.SOFT_MAX_ARRAY_LENGTH for max array size in java.base
Eirik Bjørsnøs
RFR: 8341059: Change Entrust TLS distrust date to November 12, 2024
Rajan Halade
Re: RFR: 8341059: Change Entrust TLS distrust date to November 12, 2024
Sean Mullan
Integrated: 8341059: Change Entrust TLS distrust date to November 12, 2024
Rajan Halade
RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status
Jamil Nimeh
Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status
Valerie Peng
Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status
Valerie Peng
Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status
Jamil Nimeh
Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status [v2]
Jamil Nimeh
Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status [v2]
Valerie Peng
Integrated: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status
Jamil Nimeh
RFR: 8341057: Add 2 SSL.com TLS roots
Rajan Halade
Integrated: 8341057: Add 2 SSL.com TLS roots
Rajan Halade
Re: RFR: 8341057: Add 2 SSL.com TLS roots
Sean Mullan
New candidate JEP: 486: Permanently Disable the Security Manager
Mark Reinhold
Re: New candidate JEP: 486: Permanently Disable the Security Manager
Lothar Kimmeringer
Re: New candidate JEP: 486: Permanently Disable the Security Manager
Alan Bateman
New candidate JEP: 486: Permanently Disable the Security Manager
Mark Reinhold
Re: New candidate JEP: 486: Permanently Disable the Security Manager
Peter Firmstone
Re: New candidate JEP: 486: Permanently Disable the Security Manager
Sean Mullan
Re: New candidate JEP: 486: Permanently Disable the Security Manager & Java Serialization.
Peter Firmstone
RFR: 8340327: A Common Framework to Support Public Key Algorithms with Standard Parameter Sets
Weijun Wang
Re: RFR: 8340327: A Common Framework to Support Public Key Algorithms with Standard Parameter Sets
Sean Mullan
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v2]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v3]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v4]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v5]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Sean Mullan
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Sean Mullan
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Sean Mullan
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Sean Mullan
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v6]
Kevin Driver
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v7]
Weijun Wang
Re: RFR: 8340327: A common framework to support public key algorithms with standard parameter sets [v8]
Weijun Wang
RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Artur Barashev
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Sean Mullan
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Artur Barashev
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Artur Barashev
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Sean Mullan
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Sean Mullan
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true [v2]
Artur Barashev
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true [v2]
Artur Barashev
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true [v2]
Sean Mullan
Re: RFR: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true [v2]
duke
Integrated: 8340670: Policy.UNSUPPORTED_EMPTY_COLLECTION.isReadOnly does not return true
Artur Barashev
Integrated: 8319332: Security properties files inclusion
Francisco Ferrari Bihurriet
RFR: 8340537: Typo in javadoc of java.util.jar.JarFile
Jaikiran Pai
Re: RFR: 8340537: Typo in javadoc of java.util.jar.JarFile
Sean Mullan
Re: RFR: 8340537: Typo in javadoc of java.util.jar.JarFile
Lance Andersen
Re: RFR: 8340537: Typo in javadoc of java.util.jar.JarFile
Iris Clark
Re: RFR: 8340537: Typo in javadoc of java.util.jar.JarFile
Jaikiran Pai
Integrated: 8340537: Typo in javadoc of java.util.jar.JarFile
Jaikiran Pai
8179502: Enhance OCSP, CRL and Certificate Fetch Timeouts.
Hempushpa Sahu
Re: 8179502: Enhance OCSP, CRL and Certificate Fetch Timeouts.
Sean Mullan
RFR: 8331391: Enhance the keytool code by invoking the buildTrustedCerts method for essential options
Prasadrao Koppula
Re: RFR: 8331391: Enhance the keytool code by invoking the buildTrustedCerts method for essential options
Sean Coffey
Re: RFR: 8331391: Enhance the keytool code by invoking the buildTrustedCerts method for essential options
Sean Mullan
Re: RFR: 8331391: Enhance the keytool code by invoking the buildTrustedCerts method for essential options
duke
Integrated: 8331391: Enhance the keytool code by invoking the buildTrustedCerts method for essential options
Prasadrao Koppula
RFR: 8339735: Remove references to Applet in core-libs/security APIs
Justin Lu
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs
Naoto Sato
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs
Sean Coffey
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs
Alan Bateman
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Justin Lu
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs
Alan Bateman
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Justin Lu
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs
Sean Mullan
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Justin Lu
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Sean Coffey
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Naoto Sato
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Iris Clark
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Roger Riggs
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Lance Andersen
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Sean Mullan
Re: RFR: 8339735: Remove references to Applet in core-libs/security APIs [v2]
Justin Lu
Integrated: 8339735: Remove references to Applet in core-libs/security APIs
Justin Lu
RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v2]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v2]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Hai-May Chao
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Hai-May Chao
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Jamil Nimeh
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Hai-May Chao
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Hai-May Chao
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Bernd
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Bernd
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Bernd
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v3]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v4]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v4]
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v4]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v5]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v6]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v7]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v7]
Bernd
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v7]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v8]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Daniel Jeliński
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v9]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v10]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v11]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v12]
Artur Barashev
Re: RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v13]
Artur Barashev
Re: RFR: 8313367: SunMSCAPI cannot read Local Computer certs w/o Windows elevation [v6]
rebarbora-mckvak
RFR: 8340082: Use inline return tag in java.base
Joe Darcy
Re: RFR: 8340082: Use inline return tag in java.base
Iris Clark
Re: RFR: 8340082: Use inline return tag in java.base
ExE Boss
Re: RFR: 8340082: Use inline return tag in java.base
Pavel Rappo
Re: RFR: 8340082: Use inline return tag in java.base
Pavel Rappo
Re: RFR: 8340082: Use inline return tag in java.base
Lance Andersen
Re: RFR: 8340082: Use inline return tag in java.base
Chen Liang
Re: RFR: 8340082: Use inline return tag in java.base
Pavel Rappo
Re: RFR: 8340082: Use inline return tag in java.base
Joe Darcy
Re: RFR: 8340082: Use inline return tag in java.base
Daniel Jeliński
Re: RFR: 8340082: Use inline return tag in java.base
Naoto Sato
Re: RFR: 8340082: Use inline return tag in java.base
Chen Liang
Integrated: 8340082: Use inline return tag in java.base
Joe Darcy
RFR: 8309841: Jarsigner should print a warning if an entry is removed
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed
Kevin Driver
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed
Kevin Driver
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed
Kevin Driver
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Kevin Driver
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Hai-May Chao
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Nibedita Jena
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Nibedita Jena
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Hai-May Chao
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v2]
Hai-May Chao
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v3]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v4]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v4]
Hai-May Chao
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v5]
Weijun Wang
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v5]
Sean Mullan
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v5]
Sean Mullan
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v5]
Sean Mullan
Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v5]
Weijun Wang
Earlier messages