[
https://issues.apache.org/jira/browse/IGNITE-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719921#comment-16719921
]
ASF GitHub Bot commented on IGNITE-10324:
-----------------------------------------
GitHub user a-polyakov opened a pull request:
https://github.com/apache/ignite/pull/5660
IGNITE-10324 Disallow fallback to Scanner in control.sh when asking password
Signed-off-by: a-polyakov <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/a-polyakov/ignite ignite-10324
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5660.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5660
----
commit a9db73c244a567956b4cec5770896a7db881af7e
Author: a-polyakov <polyakov.alexandr.alexandrovich@...>
Date: 2018-12-13T08:38:21Z
IGNITE-10324 Disallow fallback to Scanner in control.sh when asking password
Signed-off-by: a-polyakov <[email protected]>
----
> Disallow fallback to Scanner in control.sh when asking password
> ---------------------------------------------------------------
>
> Key: IGNITE-10324
> URL: https://issues.apache.org/jira/browse/IGNITE-10324
> Project: Ignite
> Issue Type: Bug
> Reporter: Pavel Voronkin
> Priority: Major
>
> After implementing IGNITE-9990 we still can fallback to Scanner in case of
> Console is not allowed, user can easily fallback to non-secure mode by using
> some java agent. We should not allow this, cause otherwise all efforts in
> IGNITE-9990 are useless.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
