[ 
https://issues.apache.org/jira/browse/IGNITE-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723029#comment-16723029
 ] 

Ignite TC Bot commented on IGNITE-10324:
----------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=2573768]]

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2537371&buildTypeId=IgniteTests24Java8_RunAll]

> 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
>            Assignee: Alexand Polyakov
>            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)

Reply via email to