You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/05/23 07:01:12 UTC

[jira] [Commented] (AMBARI-16810) Ambari Agent security bypassed in Python=>2.7.9

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

Hadoop QA commented on AMBARI-16810:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12805580/AMBARI-16810.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6930//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6930//console

This message is automatically generated.

> Ambari Agent security bypassed in Python=>2.7.9
> -----------------------------------------------
>
>                 Key: AMBARI-16810
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16810
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16810.patch
>
>
> We hard-coded the Ambari Agents to ignore certification
> verification. But the reason why this was required was Python be un-secure by
> default:  
> <https://access.redhat.com/articles/2039753>  
> <https://www.python.org/dev/peps/pep-0476/>
> That method will cause signed certificates to not serve any purpose & is
> discouraged by RedHat & Python security experts:
> > "It is also possible, though highly discouraged , to globally disable
> verification by monkeypatching the ssl module in versions of Python"
> Instead we should abstract it to a setting (e.g. ssl_verify_cert) in the
> ambari-agent.ini such that users can turn certification verification if they
> provide a signed/trusted certificate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)