| Tweetovi |
|
Graham Edgecombe
@grahamedgecombe
|
11. velj |
|
Max score is the highest score observed by the master node during the event - it's there so you can see which teams were doing well until they had all their coins stolen.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
16. kol 2018. |
|
If you're including extra_data they seem to have longer chains too. Mean chain length in Cirrus (excluding the leaf) is ~2.9, in Argon 2017 it's ~2.3.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
16. kol 2018. |
|
crt.sh has search by entry ID (e.g. crt.sh/?ctid=12345 to see entry 12345 in all logs). But it doesn't monitor Cirrus :(
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
12. srp 2018. |
|
Thanks! ct.grahamedgecombe.com/logs/76 I haven't found its key yet though, so I can't verify STHs.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
3. svi 2018. |
|
I think @__agwa found them in Google's STH gossip endpoint.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
3. svi 2018. |
|
gist.github.com/grahamedgecomb… base64-encoded DER, one cert per line
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
17. sij 2018. |
|
at work we thought it might be related to this post: cabforum.org/pipermail/publ… - "from China CA related government authority [...] China will have a central CT log server in China that all issued certificates for China subscriber must post to this log server"
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
11. lis 2017. |
|
They me emailed asking me to monitor them & changed the key after a few days - I think they forgot to replace the test key with the real one
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
18. kol 2017. |
|
@__agwa @rob_comodo just spotted that Google announced 5 new CT logs (sharded by expiry date & running Trillian): bugs.chromium.org/p/chromium/iss…
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
9. lip 2017. |
|
@__agwa I think the CNNIC, GDCA, SHECA, StartCom & WoSign logs run SuperDuper btw. They expose the metrics endpoint: ctlog.wosign.com/metrics
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
17. svi 2017. |
|
it's happened before! groups.google.com/a/chromium.org…
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
8. svi 2017. |
|
thanks, was worried it was a bug on my end at first! Wasn't looking forward to re-downloading all the entries to diagnose it :p
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
7. svi 2017. |
|
Google's Pilot CT log now contains over 100 million entries: ct.grahamedgecombe.com/logs/1
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
6. svi 2017. |
|
I only check if the timestamp is older than the MMD if the STH was served directly from the log, as gossip clients could submit an old STH.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
1. svi 2017. |
|
yep
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
30. tra 2017. |
|
@FiloSottile I like the log ID btw :)
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
30. tra 2017. |
|
@FiloSottile some of the get-entries requests I make to @_behindthesofa fail with a deadline exceeded error: pastebin.com/raw/mdf7JzBH
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
22. ožu 2017. |
|
I hope so! Chrome log policy says logs have to obey RFC6962, hopefully the intent is that they have to obey specs it depends on too.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
22. ožu 2017. |
|
The first req works, socket kept open. Second req fails, I close the socket on my end. Third req opens a new socket and works, etc.
|
||
|
|
||
|
Graham Edgecombe
@grahamedgecombe
|
22. ožu 2017. |
|
figured it out. SHECA claims to support keep-alive but doesn't
|
||
|
|
||