[
https://issues.apache.org/jira/browse/DRILL-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957892#comment-15957892
]
ASF GitHub Bot commented on DRILL-4335:
---------------------------------------
Github user sudheeshkatkam commented on a diff in the pull request:
https://github.com/apache/drill/pull/773#discussion_r110036482
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/server/rest/DrillRoot.java
---
@@ -61,6 +63,10 @@ public ClusterInfo getClusterInfoJSON() {
final DrillbitEndpoint currentDrillbit =
work.getContext().getEndpoint();
final String currentVersion = currentDrillbit.getVersion();
+ final DrillConfig config = work.getContext().getConfig();
+ final boolean clientEncryptionEnabled =
config.getBoolean(ExecConstants.USER_SASL_ENCRYPTION_ENABLED);
--- End diff --
For consistency, use `userEncryptionEnabled` and `bitEncryptionEnabled`
> Apache Drill should support network encryption
> ----------------------------------------------
>
> Key: DRILL-4335
> URL: https://issues.apache.org/jira/browse/DRILL-4335
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Keys Botzum
> Assignee: Sorabh Hamirwasia
> Labels: security
> Attachments: ApacheDrillEncryptionUsingSASLDesign.pdf
>
>
> This is clearly related to Drill-291 but wanted to make explicit that this
> needs to include network level encryption and not just authentication. This
> is particularly important for the client connection to Drill which will often
> be sending passwords in the clear until there is encryption.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
