It would be great if stirling were able to decode TLS flows from the 'boringcrypto' versions of Golang.
Stirling would need to be modified to have uprobes for this version of Golang: https://go.googlesource.com/go/+/dev.boringcrypto
This version of Golang is used in order to have FIPS compliant Go programs. We at VMware use it extensively.
Alternatives:
Don't use the boringcrypto version of Golang. This is not an option in cases where one wants to claim FIPS compliance for their Go program.
It would be great if stirling were able to decode TLS flows from the 'boringcrypto' versions of Golang.
Stirling would need to be modified to have uprobes for this version of Golang: https://go.googlesource.com/go/+/dev.boringcrypto
This version of Golang is used in order to have FIPS compliant Go programs. We at VMware use it extensively.
Alternatives:
Don't use the boringcrypto version of Golang. This is not an option in cases where one wants to claim FIPS compliance for their Go program.