c23e497da7
The Name Constraints extension contains GeneralSubtree values indicating included or excluded subtrees. It is defined as: GeneralSubtree ::= SEQUENCE { base GeneralName, minimum [0] BaseDistance DEFAULT 0, maximum [1] BaseDistance OPTIONAL } RFC 5280 further specifies: Within this profile, the minimum and maximum fields are not used with any name forms, thus, the minimum MUST be zero, and maximum MUST be absent. Because the minimum fields has DEFAULT 0, and certificates should be encoded using DER, the situation where minimum = 0 occurs in a certificate should not arise. Nevertheless, it does arise. For example, I have seen certificates issued by Microsoft programs that contain GeneralSubtree values encoded thus. Enhance the Name Constraints matching routine to handle the case where minimum is specified. If present, it must be zero. The maximum field remains prohibited. Reviewed-by: Paul Yang <yang.yang@baishancloud.com> Reviewed-by: Paul Dale <paul.dale@oracle.com> (Merged from https://github.com/openssl/openssl/pull/7039) |
||
---|---|---|
.. | ||
build.info | ||
ext_dat.h | ||
pcy_cache.c | ||
pcy_data.c | ||
pcy_int.h | ||
pcy_lib.c | ||
pcy_map.c | ||
pcy_node.c | ||
pcy_tree.c | ||
standard_exts.h | ||
v3_addr.c | ||
v3_admis.c | ||
v3_admis.h | ||
v3_akey.c | ||
v3_akeya.c | ||
v3_alt.c | ||
v3_asid.c | ||
v3_bcons.c | ||
v3_bitst.c | ||
v3_conf.c | ||
v3_cpols.c | ||
v3_crld.c | ||
v3_enum.c | ||
v3_extku.c | ||
v3_genn.c | ||
v3_ia5.c | ||
v3_info.c | ||
v3_int.c | ||
v3_lib.c | ||
v3_ncons.c | ||
v3_pci.c | ||
v3_pcia.c | ||
v3_pcons.c | ||
v3_pku.c | ||
v3_pmaps.c | ||
v3_prn.c | ||
v3_purp.c | ||
v3_skey.c | ||
v3_sxnet.c | ||
v3_tlsf.c | ||
v3_utl.c | ||
v3err.c |