David Adrian
David Adrian
We should read through the documentation, and update information about the forks, and write intro `doc.go` pages for everything.
``` Cipher Suites (17 suites) Cipher Suite: Reserved (GREASE) (0x3a3a) Cipher Suite: TLS_AES_128_GCM_SHA256 (0x1301) Cipher Suite: TLS_AES_256_GCM_SHA384 (0x1302) Cipher Suite: TLS_CHACHA20_POLY1305_SHA256 (0x1303) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)...
This sounds correct to me, @zakird can you confirm that logrus is the correct framework, and not go-logging? `zintermediate` is made up and can be easily changed to use Logrus,...
For what it's worth, I expect this would require a major refactor.
@theloglizard What's the output of `go version`?
@theloglizard Try building again using a more recent version of Golang (at least 1.13). It doesn't look like your Go version is respecting the `replace` directive in the `go.mod` file.
I took a crack at this the other day. This is non-trivial. The `zcrypto/ct` code from Google is poorly organized, and tightly coupled to it's use of `zcrypto/ct/x509`, and there's...
I haven't been particularly involved in TLS1.3. If it's in ZCrypto, and someone adds it into ZGrab (is there a PR?), I'd merge it.
I don't quite understand what you mean. What kind of test domain do you want?
Can you post what the record we'd need to set are? Then myself or @zakird can look into how we would set them.