Revision c40c2bc3f3797db7b6a1346e5057f080821a54a5 authored by juerg on 29 February 2024, 08:38:16 UTC, committed by Copybara-Service on 29 February 2024, 08:39:11 UTC
This makes sure that nothing gets registered if Tink is used in FIPS mode but the FIPS module is not available.

Also, the documentation of registerKeyManagerWithFipsCompatibility says that if it fails, then "the KeyManagerRegistry is in an unspecified state and should be discarded." But since we are calling it on a global instance that can't be discarded, we need to make sure that the call doesn't fail. And if it does fail, we need to throw a runtime exception as this shouldn't happen.

PiperOrigin-RevId: 611373559
1 parent 0340f1f
History
File Mode Size
.github
cc
cmake
docs
go
java_src
kokoro
proto
python
testdata
testing
tools
.bazelversion -rw-r--r-- 6 bytes
.gitignore -rw-r--r-- 165 bytes
BUILD.bazel -rw-r--r-- 442 bytes
CMakeLists.txt -rw-r--r-- 1.6 KB
LICENSE -rw-r--r-- 11.1 KB
README.md -rw-r--r-- 5.9 KB
passing_test.sh -rwxr-xr-x 24 bytes
tinkey.rb -rw-r--r-- 556 bytes

README.md

back to top