Yes, the test pass, but I wonder what will happen when the system has to
sign the deltas (although I guess this is only needed in a federated
configuration).

On Thu, Sep 15, 2011 at 12:44 PM, James Purser <[email protected]>wrote:

> As a follow up, by disabling the CertpathTest it all builds fine.
>
> On Thu, Sep 15, 2011 at 8:35 PM, James Purser <[email protected]
> >wrote:
>
> > I can confirm this error:
> >
> __________________________________________________________________________________________________________________________________________________________
> >
> >
> >
> >
> >   Class org.waveprotocol.wave.crypto.CertpathTest
> >
> >
> >
> >
> >
> >        Name     Tests Errors Failures Time(s)     Time Stamp       Host
> >
> >
> >    CertpathTest 1     1      0        0.054   2011-09-15T10:26:04 hosting
> >
> >
> >
> >
> >
> > Tests
> >
> >
> >
> >
> >
> >    Name Status Type Time(s)
> >
> >
> >    testValidator_canGrokCriticalExtension Error Certificate validation
> > failure
> >
> >    org.waveprotocol.wave.crypto.SignatureException: Certificate
> validation
> > failure
> >
> >    at
> >
> org.waveprotocol.wave.crypto.CachedCertPathValidator.validateNoCache(CachedCertPathValidator.java:103)
> >
> >    at
> >
> org.waveprotocol.wave.crypto.CachedCertPathValidator.validate(CachedCertPathValidator.java:65)
> >
> >    at
> >
> org.waveprotocol.wave.crypto.CertpathTest.testValidator_canGrokCriticalExtension(CertpathTest.java:96)
> >
> >    Caused by: java.security.cert.CertPathValidatorException: timestamp
> > check failed
> >
> >    at
> >
> sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:153)
> >
> >    at
> >
> sun.security.provider.certpath.PKIXCertPathValidator.doValidate(PKIXCertPathValidator.java:325)
> >
> >    at
> >
> sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:187)
> >
> >    at
> > java.security.cert.CertPathValidator.validate(CertPathValidator.java:267)
> >
> >
> >    at
> >
> org.waveprotocol.wave.crypto.CachedCertPathValidator.validateNoCache(CachedCertPathValidator.java:101)
> >
> >    Caused by: java.security.cert.CertificateExpiredException: NotAfter:
> Fri
> > Sep 09 13:28:30 EST 2011
> >
> >    at
> > sun.security.x509.CertificateValidity.valid(CertificateValidity.java:273)
> >
> >
> >    at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:587)
> >
> >
> >    at
> >
> sun.security.provider.certpath.BasicChecker.verifyTimestamp(BasicChecker.java:178)
> >
> >
> >    at
> > sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:130)
> >
> >
> >    at
> >
> sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:131)
> >
> >    0.046
> >
> >
> > On Wed, Sep 14, 2011 at 5:03 PM, Eduardo Garcia Lopez <
> > [email protected]> wrote:
> >
> >> Hi,
> >> I tried to build the project today and got an error during tests phase:
> >> *...*
> >> java.security.cert.CertificateExpiredException: NotAfter: Fri Sep 09
> >> 05:28:30 CEST 2011
> >> ...
> >>
> >> I'm not sure, but it seems it is a certificate issued by Google the one
> >> that
> >> has expired on Sep 09 2011, with Wave critical extension in it. I am
> >> afraid
> >> Google is not going to issue such certificates anymore, so I guess we
> >> should
> >> issue self-signed certificate, with wave critical extension.
> >> Should I file this as an issue in Jira?
> >>
> >> --
> >> Eduardo G.
> >> http://www.stream18.com
> >>
> >
> >
> >
> > --
> > James Purser
> > Collaborynth
> > http://collaborynth.com.au
> > Mob: +61 406 576 553
> > Wave: [email protected]
> >
> >
> >
>
>
> --
> James Purser
> Collaborynth
> http://collaborynth.com.au
> Mob: +61 406 576 553
> Wave: [email protected]
>



-- 
Eduardo G.
http://www.stream18.com

Reply via email to