Twitter | Pretraživanje | |
Graham Edgecombe
366
Tweetovi
502
Pratim
195
Osobe koje vas prate
Tweetovi
Graham Edgecombe 11. velj
Odgovor korisniku/ci @Ministraitor @siginthq @Netcraft
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.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 16. kol 2018.
Odgovor korisniku/ci @BenBE1987 @__agwa
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.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 16. kol 2018.
Odgovor korisniku/ci @BenBE1987 @FiloSottile i 2 ostali
has search by entry ID (e.g. to see entry 12345 in all logs). But it doesn't monitor Cirrus :(
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 12. srp 2018.
Odgovor korisniku/ci @chaz_6
Thanks! I haven't found its key yet though, so I can't verify STHs.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 3. svi 2018.
Odgovor korisniku/ci @BenBE1987 @Scott_Helme i 3 ostali
I think found them in Google's STH gossip endpoint.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 3. svi 2018.
Odgovor korisniku/ci @BenBE1987 @Scott_Helme i 2 ostali
base64-encoded DER, one cert per line
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 17. sij 2018.
Odgovor korisniku/ci @__agwa @durumcrustulum
at work we thought it might be related to this post: - "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"
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 11. lis 2017.
Odgovor korisniku/ci @__agwa
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
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 18. kol 2017.
@rob_comodo just spotted that Google announced 5 new CT logs (sharded by expiry date & running Trillian):
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 9. lip 2017.
I think the CNNIC, GDCA, SHECA, StartCom & WoSign logs run SuperDuper btw. They expose the metrics endpoint:
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 17. svi 2017.
Odgovor korisniku/ci @BenBE1987
it's happened before!
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 8. svi 2017.
Odgovor korisniku/ci @__agwa
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
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 7. svi 2017.
Google's Pilot CT log now contains over 100 million entries:
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 6. svi 2017.
Odgovor korisniku/ci @lukegb
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.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 1. svi 2017.
Odgovor korisniku/ci @BenBE1987
yep
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 30. tra 2017.
I like the log ID btw :)
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 30. tra 2017.
some of the get-entries requests I make to fail with a deadline exceeded error:
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 22. ožu 2017.
Odgovor korisniku/ci @lukegb
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.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 22. ožu 2017.
Odgovor korisniku/ci @lukegb
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.
Reply Retweet Označi sa "sviđa mi se"
Graham Edgecombe 22. ožu 2017.
Odgovor korisniku/ci @lukegb
figured it out. SHECA claims to support keep-alive but doesn't
Reply Retweet Označi sa "sviđa mi se"