We'd love to have this merged so that our FIPS checking code can continue to work now that we've updated to Go 1.19.4
Who are the maintainers here?

@maraino @zaichang thanks for creating this PR! Could you take a look at https://stackoverflow.com/questions/75638176/how-can-i-check-whether-my-golang-app-uses-boringcrypto-instead-of-the-native-go?

@linouk23 boring crypto integration changed last year a lot, I can take a look to see if this PR is still valid or if you need something else.

@linouk23, it looks that this PR still works on Go 1.20.1, in this version, the condition strings.HasPrefix(name, "crypto/internal/boring/sig.BoringCrypto") is unnecessary, but I believe it was for Go 1.17 when I created this PR.

But at the same time, as a comment in Stack Overflow says, goversion is not necessary and you can use go tool nm

$ go tool nm main  | grep -E 'sig.FIPSOnly|sig.BoringCrypto|sig.StandardCrypto'
  52ea60 t crypto/internal/boring/sig.StandardCrypto.abi0
$ go tool nm main.fips | grep -E 'sig.FIPSOnly|sig.BoringCrypto|sig.StandardCrypto'
  532860 t crypto/internal/boring/sig.BoringCrypto.abi0
  532880 t crypto/internal/boring/sig.FIPSOnly.abi0

Fixed, thanks.

@rsc, Can you please tag a new release?

PS: I was pleasantly surprised that Go doesn't complain when you run go install rsc.io/goversion@master, the go.mod shows 1.21

+1 on tagging a release. Thanks for merging this patch!