Looking at our own use case as well as people running into the same issue [1][2], it seems like users usually don't care about decoding unknown PKCS12Attributes. [1]: https://github.com/golang/go/issues/24325 [2]: https://github.com/SSLMate/go-pkcs12/pull/4 Fixes golang/go#24325 Change-Id: I4f3700d2551af6dac215c49dd179ce46c4b2a9db Reviewed-on: https://go-review.googlesource.com/c/crypto/+/241281 Reviewed-by: Filippo Valsorda <filippo@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> |
||
---|---|---|
.. | ||
internal/rc2 | ||
bmp-string.go | ||
bmp-string_test.go | ||
crypto.go | ||
crypto_test.go | ||
errors.go | ||
mac.go | ||
mac_test.go | ||
pbkdf.go | ||
pbkdf_test.go | ||
pkcs12.go | ||
pkcs12_test.go | ||
safebags.go |