bharatviswa504 edited a comment on pull request #2132: URL: https://github.com/apache/ozone/pull/2132#issuecomment-816436854
> Thanks the answer @bharatviswa504 > > > Yes, planned phase-1 development tasks are almost completed. We have one in-progress HDDS-5060. > > Based on my understanding without [HDDS-5060](https://issues.apache.org/jira/browse/HDDS-5060) it can not be secure in production. We shouldn't release the current code it without this safety check (or we need to issue a cve... ;-) ) Is there any release planned from master, before next release we will make sure we shall have this fix. I belive we don't need to issue a cve for this, as we shall take care of this issue before the next release from apache master branch. > > Is there any specific reason to remove this check before having full security? I mean: if it's required for acceptance tests, we can directly configure this value in docker-config files. Currently, in docker-tests we have that way. If you see this PR, this PR is removing the config in docker tests. > > Or do we have any other motivations? > > I have a strange feeling about committing something to the master which makes the branch non-releaseable... The motivation for this is in Cloudera CM integration we don't need this additional config for CM integration of SCM HA. SCM HA work is merged to master, so SCM HA security tasks are being worked on in master directly, and as said above this will be addressed before the next release. But if you feel strongly this cannot be committed until we have HDDS-5060 I am fine with it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
