You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:37:12 UTC

[jira] [Updated] (HDDS-589) SCM CA: Support Certificate with pathLenConstraint in BasicContraints Extension

     [ https://issues.apache.org/jira/browse/HDDS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose updated HDDS-589:
----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> SCM CA: Support Certificate with pathLenConstraint in BasicContraints Extension
> -------------------------------------------------------------------------------
>
>                 Key: HDDS-589
>                 URL: https://issues.apache.org/jira/browse/HDDS-589
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Security
>            Reporter: Xiaoyu Yao
>            Priority: Major
>
> RFC 5280, section 4.2.1.9
> A pathLenConstraint of zero indicates that no non-self-issued intermediate CA certificates may follow in a valid certification path. Where it appears, the pathLenConstraint field MUST be greater than or equal to zero. Where pathLenConstraint does not appear, no limit is imposed.
> This is needed when we support intermediate CA (non-genesis SCMs) issuing certificate based on its certificate signed by genesis SCM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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