--
You received this message because you are subscribed to the Google Groups "certificate-transparency" group.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/da316b03-75db-4c00-a741-68181cde2d41%40googlegroups.com.
Hi SriRamji,could you provide a little more detail on exactly what you're seeing?It might help folks figure out what the problem might be.Kind regards,Al.
On Mon, Jun 1, 2020 at 5:24 PM SriRamji Kathiravan <sriramji....@pearson.com> wrote:
Certificate transparency stopped working for s3.amasonaws.com while debugging it was working fine with version 2 log_list but not working on version 1 log_list--We are ready get rid of old version but it does affecting our production userPlease revert if any changes made recently in version 1 log_list(this was working fine in recent days, today it stopped working)Thank you understanding
You received this message because you are subscribed to the Google Groups "certificate-transparency" group.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transparency+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/da316b03-75db-4c00-a741-68181cde2d41%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "certificate-transparency" group.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/80b37171-6ecf-4370-9850-54383892f833%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transparency+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/da316b03-75db-4c00-a741-68181cde2d41%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "certificate-transparency" group.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transparency+unsub...@googlegroups.com.
We are using https://github.com/babylonhealth/certificate-transparency-android version 1.4, this(seconds/milliseconds variation) was not handled in the libraryTo avoid confusion/maintain consistency between timestamp, Is this possible to update the log_list timestamp value in milliseconds?
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/da316b03-75db-4c00-a741-68181cde2d41%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "certificate-transparency" group.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/80b37171-6ecf-4370-9850-54383892f833%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "certificate-transparency" group.
To unsubscribe from this group and stop receiving emails from it, send an email to certificate-transp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/certificate-transparency/670d2d87-1dcb-4b18-a2f2-478bd230a939%40googlegroups.com.
The documentation on the format of the v1 schema was somewhat lacking, and indeed the original schema just has it down as a number, so we clearly made a mistake in the interpretation.
The library no longer supports the v1 schema, as Al mentions the v2 schema is much better defined, so please upgrade to the latest version of the library, v0.2.0 which should fix your issue.
From: 'Al Cutter' via certificate-transparency <certificate-...@googlegroups.com>
Reply to: "certificate-...@googlegroups.com" <certificate-...@googlegroups.com>
Date: Tuesday, 2 June 2020 at 12:27
To: "certificate-...@googlegroups.com" <certificate-...@googlegroups.com>
Subject: Re: https://www.gstatic.com/ct/log_list/log_list.json stopped working
On Tue, Jun 2, 2020 at 6:53 AM SriRamji Kathiravan <sriramji....@pearson.com> wrote:
We are using https://github.com/babylonhealth/certificate-transparency-android version 1.4, this(seconds/milliseconds variation) was not handled in the library
To avoid confusion/maintain consistency between timestamp, Is this possible to update the log_list timestamp value in milliseconds?
Changing the unit of a field definition in a config file which has been around for a while seems like it might more generally make things worse.
However, the new log_list v2 schema, which I believe folks should be moving to, seems quite clear that temporal periods etc. are all defined as JSON date-time types - hopefully this will help avoid confusion in the future.
I see that you've opened an issue on Babylon Health's CT repo (https://github.com/babylonhealth/certificate-transparency-android/issues/40 for anyone else following along), let us know if there's anything else we can do to help.
To view this discussion on the web visit
https://groups.google.com/d/msgid/certificate-transparency/CACM%3D_OfT9XbRDcHz7zVC86zbFXtXA-mhihfDAfptw5x6syqJig%40mail.gmail.com.