AG

I think this can be closed now Test cases were added but I'm unable to reproduce (or locate) the issue @samJ-bitsight please let me know if you encounter this again...

I vaguely remember having this issue. Manually create that shims directory and run the script again (add an os.mkdir into the script) Or... just manually copy the files

> Using the tls function of zgrab2, it was found that almost all tls requests were unable to verify the certificate chain, with surprisingly consistent error codes of x509: failed...

Can this be closed? I don't see any immediate interest from the maintainers to change the current behavior as I believe it was a very deliberate choice on their part...

A couple of ideas... - Try specifying the with-body-size bool flag. This won't fix the issue but it might be helpful to see if it's reporting short in the output...

> With HTTP1.1, the connection is assumed to be persistent, and t.Body = NoBody is set for the second pass. I'm not sure what you mean by second pass (I'm...

So I spent a 20 minutes today looking at what would be needed to force the golang HTTP package to send HTTP/1.0 (and potentially other values). That's the quickest blunt-instrument...

FYI - one way to do this until it’s added to Gepetto is with a compatibility shim, e.g. [claude2openai](https://github.com/missuo/claude2openai) I haven’t used it myself but it seems like it might...

Note: the [qusal project](https://github.com/ben-grande/qusal) has [this](https://github.com/ben-grande/qusal/tree/main/salt/kicksecure-minimal) which might be a helpful reference as well

A little late for a response but I'm guessing it's an issue with the ciphers offered not being compatible with the default zgrab2 (via zcrypto) ciphers This probably works now,...