Bug 1309828
Summary: | python-rhsm (1.17.1) can not parse/check path for certificates with short content path (like "/test") | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | stas-fomin <stas-fomin> |
Component: | python-rhsm | Assignee: | Kevin Howell <khowell> |
Status: | CLOSED WONTFIX | QA Contact: | John Sefler <jsefler> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | bcourt, jmolet, khowell |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-22 15:21:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
stas-fomin@yandex.ru
2016-02-18 19:06:22 UTC
as a work around always use paths that are more than 1 level deep. Hello! I'm a tester trying to determine the extent of this bug. I was wondering how you created that certificate in the first place? None of the end user tools (satellite mainly) allow me to create custom content with a path depth of 1, its always 3 or more deep when creating custom content. Your reproducer is super helpful, however any pointers on how you got that certificate would help cover our edge cases. I generated client certificates by CandlePin. (sample of such cert on https://github.com/belonesox/certificates-wtf/blob/master/certparse.py ) I spent some time looking into this, and verified that this does appear to be an edge case in the parser for certv3 in python at least. I also tried to load the content list data into one of our candlepin test cases, and it also caused an exception (though I'm not completely convinced I had the test case set up correctly). Given that there are no practical use cases that candlepin devs are aware of, this is a limitation we are probably going to leave as-is. That being said, if there are use cases that are important to you and/or you can provide more context (use case(s) and sample calls/data used to generate the cert in candlepin would be helpful), then please feel free to reopen this bug. More context in case we revisit: I got as far as determining that the huffman code implementation we use in Python does not assign codes when the tree only has two nodes (see https://github.com/candlepin/python-rhsm/blob/c9ea6a870e789018029ac29a90f799ae238f1ea8/src/rhsm/huffman.py#L85), and I suspect this causes issues. |