[
https://issues.apache.org/jira/browse/KUDU-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224692#comment-17224692
]
ASF subversion and git services commented on KUDU-3210:
-------------------------------------------------------
Commit 6d2c79a4f266932b644f1cf7165ad3b6ccc49404 in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=6d2c79a ]
KUDU-3210 Add option to enforce FIPS approved mode
If KUDU_REQUIRE_FIPS_MODE is set to "1", "true" or "yes", Kudu checks if
FIPS mode is enabled and crashes when initializing OpenSSL if not. This
is also true for Kudu C++ client applications.
On initializing OpenSSL, Kudu now also verbose logs (level 2) if FIPS
mode is enabled regardless of whether it's required or not.
Change-Id: I98a6a8b3330ea0b372b188690fadd4d312d8bf93
Reviewed-on: http://gerrit.cloudera.org:8080/16657
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-by: Kudu Jenkins
> Support FIPS approved mode
> --------------------------
>
> Key: KUDU-3210
> URL: https://issues.apache.org/jira/browse/KUDU-3210
> Project: Kudu
> Issue Type: Improvement
> Reporter: Attila Bukor
> Assignee: Attila Bukor
> Priority: Major
>
> FIPS 140-2 is a standard used to approve cryptographic modules. Some versions
> of OpenSSL support a "FIPS mode" where only approved algorithms and key sizes
> are enabled. Kudu should be able to run when FIPS mode is enabled and should
> provide a way for admins to require that FIPS mode is enabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
