[jira] [Updated] (RANGER-1858) ranger-admin start fail when policymgr_http_enabled equal to false.

[ https://issues.apache.org/jira/browse/RANGER-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1858: - Attachment: 0001-RANGER-1858-ranger-admin-start-fail-when-policymgr_h.patch > ranger-admin start

[jira] [Commented] (RANGER-1300) S3 support

[ https://issues.apache.org/jira/browse/RANGER-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221681#comment-16221681 ] alal alal commented on RANGER-1300: --- [~GodenYao] I am looking into ranger plugin for presto as well as

[jira] [Commented] (RANGER-1851) Enhance Ranger Hive Plugin to support authorization for KILL QUERY command

[ https://issues.apache.org/jira/browse/RANGER-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221674#comment-16221674 ] Ramesh Mani commented on RANGER-1851: - [~sershe] sure if you could point me to this documentation in

[jira] [Resolved] (RANGER-1856) Installation and access logic are inconsistent for the pid of kms program. Like security admin, they should be consistent.

[ https://issues.apache.org/jira/browse/RANGER-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-1856. - Resolution: Fixed Fix Version/s: master 1.0.0 > Installation and

[jira] [Comment Edited] (RANGER-1851) Enhance Ranger Hive Plugin to support authorization for KILL QUERY command

[ https://issues.apache.org/jira/browse/RANGER-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221544#comment-16221544 ] Sergey Shelukhin edited comment on RANGER-1851 at 10/27/17 1:01 AM:

[jira] [Resolved] (RANGER-1857) The value of RANGER_KMS_HOME logic is not correct in dba_script.py and db_setup.py, Like db_setup.py in admin, we should optimize them.

[ https://issues.apache.org/jira/browse/RANGER-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-1857. - Resolution: Fixed Fix Version/s: master 1.0.0 > The value of

[jira] [Commented] (RANGER-1851) Enhance Ranger Hive Plugin to support authorization for KILL QUERY command

[ https://issues.apache.org/jira/browse/RANGER-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221544#comment-16221544 ] Sergey Shelukhin commented on RANGER-1851: -- [~rmani] these are service operation commands if I

[jira] [Resolved] (RANGER-1846) This JAVA_VERSION_REQUIRED configuration item is invalid in security admin installer, we should enable it to control the necessary java version.

[ https://issues.apache.org/jira/browse/RANGER-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-1846. - Resolution: Fixed > This JAVA_VERSION_REQUIRED configuration item is invalid in security admin

FW: New Defects reported by Coverity Scan for Apache Ranger

Please review and fix. Thanks Bosco On 10/26/17, 9:11 AM, "scan-ad...@coverity.com" wrote: Hi, Please find the latest report on new defect(s) introduced to Apache Ranger found with Coverity Scan. 1 new defect(s) introduced to Apache Ranger

Re: Review Request 63145: This JAVA_VERSION_REQUIRED configuration item is invalid in security admin installer, we should enable it to control the necessary java version.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63145/#review189299 --- Ship it! Ship It! - Colm O hEigeartaigh On Oct. 24, 2017,

[jira] [Created] (RANGER-1858) ranger-admin start fail when policymgr_http_enabled equal to false.

peng.jianhua created RANGER-1858: Summary: ranger-admin start fail when policymgr_http_enabled equal to false. Key: RANGER-1858 URL: https://issues.apache.org/jira/browse/RANGER-1858 Project: Ranger

Re: Review Request 63209: RANGER-1644 changed crypto algorithm to a strong one

> On Oct. 23, 2017, 4:56 a.m., bhavik patel wrote: > > @Endre Zoltan Kovacs : Have you tested plugins test-connection? If someone > > upgrade from ranger-0.6 to ranger-0.7 or master after then check plugins > > test-connection should not break, can you please confirm that. > > > > note: If

[jira] [Commented] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.

[ https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220258#comment-16220258 ] Endre Kovacs commented on RANGER-1644: -- added additional comments at the review request / recut

[jira] [Updated] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.

[ https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Endre Kovacs updated RANGER-1644: - Attachment: (was: 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch) > Change the

[jira] [Updated] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.

[ https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Endre Kovacs updated RANGER-1644: - Attachment: 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch > Change the default

Re: Review Request 63209: RANGER-1644 changed crypto algorithm to a strong one

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63209/ --- (Updated Oct. 26, 2017, 9:51 a.m.) Review request for ranger. Changes