Is anyone else getting expired certificates with jtreg qa tests? This
seems to be the cause for a number of test failures I'm getting in jtreg.
Is someone able to run the jtreg tests and post the result?
Much appreciated,
Peter.
Test 115: TestEndpoint$TestNewRequest: Right server principal
clientSubject: null
constraints: InvocationConstraints[reqs: {ServerAuthentication.YES,
ServerMinPrincipal{CN=serverRSA}}, prefs: {}]
serverSubject: Subject:
Principal: CN=serverRSA
Public Credential:
X.509 Cert Path: length = 1.
[
=========================================================Certificate 1 start.
[
[
Version: V1
Subject: CN=serverRSA
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunPKCS11-Solaris RSA public key, 1024 bits (id 5083376, session object)
modulus:
135056526541564882699769252544765280837203993874955355339176010564140085107700414706050495414366234012907298276038631730746525823123355138115696905562519095445461377828195158628809164132396476513602498014984611606548981531936609310969402430150940256383925514208004870700529530923239737011605213497165057994633
public exponent: 65537
Validity: [From: Wed Jan 17 07:13:33 EST 2001,
To: Sat Jan 15 07:13:33 EST 2011]
Issuer: CN=serverRSA
SerialNumber: [ 3a64b97d]
]
Algorithm: [MD5withRSA]
Signature:
0000: BE 03 A5 45 EF 3F 9B 8E C1 D5 6C 03 B9 EB E1 28 ...E.?....l....(
0010: 5F D2 91 CC B7 8D D8 94 24 4C D7 9D 1E 64 EC 84 _.......$L...d..
0020: 4F 40 05 2C 94 A0 AF FA B6 31 D4 69 51 88 90 D2 O@.,.....1.iQ...
0030: 11 2E FF B6 3E 39 0D 52 8C 37 EC EA 1E CE 12 37 ....>9.R.7.....7
0040: B6 48 E2 78 B6 D9 69 C9 28 6F D9 7E 4B 00 98 A7 .H.x..i.(o..K...
0050: EA E1 6E 8E 6F 5E 64 92 33 4C CA 0A 87 AE EC 87 ..n.o^d.3L......
0060: F7 8B A9 B1 F7 84 76 CF 15 52 E2 3F 11 5E 16 A9 ......v..R.?.^..
0070: E0 D1 E1 03 20 E6 45 C8 3B B5 56 2E D1 15 1E 29 .... .E.;.V....)
]
=========================================================Certificate 1 end.
]
Private Credential:
javax.security.auth.x500.X500PrivateCredential@186df0f
FAIL: Unexpected exception: net.jini.io.UnsupportedConstraintException: Problem
with certificates: CN=serverRSA
java.security.cert.CertificateExpiredException: NotAfter: Sat Jan 15 07:13:33
EST 2011
at
net.jini.jeri.ssl.SslServerEndpointImpl$SslListenEndpoint.checkCredentials(SslServerEndpointImpl.java:726)
at
net.jini.jeri.ssl.SslServerEndpointImpl$SslListenEndpoint.listen(SslServerEndpointImpl.java:658)
at
TestEndpoint$TestNewRequest$25.addListenEndpoint(TestEndpoint.java:1060)
at
net.jini.jeri.ssl.SslServerEndpointImpl.enumerateListenEndpoints(SslServerEndpointImpl.java:568)
at
net.jini.jeri.ssl.SslServerEndpoint.enumerateListenEndpoints(SslServerEndpoint.java:804)
at TestEndpoint$TestNewRequest.run(TestEndpoint.java:1054)
at UnitTestUtilities.test(UnitTestUtilities.java:185)
at UnitTestUtilities.test(UnitTestUtilities.java:130)
at UnitTestUtilities.test(UnitTestUtilities.java:134)
at UnitTestUtilities.test(UnitTestUtilities.java:143)
at UnitTestUtilities.test(UnitTestUtilities.java:99)
at TestEndpoint.main(TestEndpoint.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Sat Jan 15
07:13:33 EST 2011
at
sun.security.x509.CertificateValidity.valid(CertificateValidity.java:256)
at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:570)
at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:543)
at net.jini.jeri.ssl.Utilities.checkValidity(Utilities.java:774)
at
net.jini.jeri.ssl.SslServerEndpointImpl$SslListenEndpoint.checkCredentials(SslServerEndpointImpl.java:698)
... 17 more
Tom Hobbs wrote:
That's great. Could you grab the artifacts and check that the sources
build, that the bin and doc versions contain what we expect them to, verify
the hashes etc.
I think thatthey're fine, but it's always good to get others to check.
having said that, you might want to hold off some because Peter is going to
add some more things in and then I'll have to cut a new release.
Grammar and spelling have been sacrificed on the altar of messaging via
mobile device.
On 14 Jun 2011 21:40, "Patricia Shanahan" <[email protected]> wrote:
I'm available to work on River again. Is there something I can do to
contribute to getting the release out, given zero experience with Apache
release process?
Patricia
