[GitHub] [ozone] elek commented on pull request #2132: HDDS-5075. [SCM HA Security] Remove code of not starting ozone services when Security is enabled on SCM HA cluster

[GitBox <gi...@apache.org>]

elek commented on pull request #2132:
URL: https://github.com/apache/ozone/pull/2132#issuecomment-816398571


   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 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 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.
   
   Or do we have any other motivations?
   
   I have a strange feeling about committing something to the master which makes the branch non-releaseable...


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org