"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/FIPS.md" between
tink-1.6.0.tar.gz and tink-1.6.1.tar.gz

About: Tink is a cryptographic library that provides a safe, simple and agile API for common cryptographic tasks, like symmetric encryption, message authentication, digital signatures, and hybrid encryption.

FIPS.md  (tink-1.6.0)	:	FIPS.md  (tink-1.6.1)
skipping to change at line 71		skipping to change at line 71
To use the BoringCrypto module via Bazel, you can uncomment the `local_repositor y`		To use the BoringCrypto module via Bazel, you can uncomment the `local_repositor y`
definition for `boringssl` in the [C++		definition for `boringssl` in the [C++
WORKSPACE](https://github.com/google/tink/blob/master/cc/WORKSPACE).		WORKSPACE](https://github.com/google/tink/blob/master/cc/WORKSPACE).
### Enabling at compile time		### Enabling at compile time
To build Tink in FIPS-only mode, you simply set a flag at compile time:		To build Tink in FIPS-only mode, you simply set a flag at compile time:
```shell		```shell
bazel build ... --//third_party/tink/cc/config:use_only_fips=True		bazel build ... --//config:use_only_fips=True
```		```
If you want to check at runtime whether Tink has been build in FIPS only mode,		If you want to check at runtime whether Tink has been build in FIPS only mode,
you can include the header `internal/fips_utils.h` which provides the constant		you can include the header `internal/fips_utils.h` which provides the constant
`kUseOnlyFips`.		`kUseOnlyFips`.
If you are *not* building Tink in FIPS only mode, it will still utilize		If you are *not* building Tink in FIPS only mode, it will still utilize
validated implementations for *some* algorithms but not restrict the usage of		validated implementations for *some* algorithms but not restrict the usage of
other algorithms.		other algorithms.
End of changes. 1 change blocks.
1 lines changed or deleted		1 lines changed or added

---