-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clearance level inheritance for Level 0. #1739
Comments
Might be fixed in #2705. |
Quick fix for now in #2705. Will address inheritance rules and multi object inference in forthcoming issues. |
dekkers
pushed a commit
that referenced
this issue
Apr 1, 2024
Co-authored-by: ammar92 <[email protected]> Co-authored-by: Jan Klopper <[email protected]>
underdarknl
added a commit
that referenced
this issue
Apr 2, 2024
Co-authored-by: originalsouth <[email protected]> Co-authored-by: ammar92 <[email protected]> Co-authored-by: Jan Klopper <[email protected]>
jpbruinsslot
added a commit
that referenced
this issue
Apr 4, 2024
* main: (51 commits) Fix static files for container images/Debian packages when DEBUG is on (#2742) OOI selection at Aggregate report does not remember changed selection (#2619) fix schema errors on empty / missing schemas (#2744) Updated `phonenumbers` and `django-phonenumber-field` (#2757) Remove octopoes coverage workflow (#2755) Bump actions/configure-pages from 4 to 5 (#2745) Add xtdb-cli tool to Octopoes (#2733) Dont report vulnerabilities without version info of the software for snyk (#2730) Feature/boefjes to oci images (#2709) Query non-reference fields and subclass-specific fields through path queries (#2662) Fix in System Specific (#2732) Plugins overview in appendix not showing any plugins (#2694) Feat stepper design v2 (#2704) Undo project-directory in Rocky (#2734) Remove Docker Compose: "version" (#2718) Upgrade `pre-commit` hooks (#2729) Fix #1739 (#2705) Improve generate report (#2633) Fix critical vulnerability counter (#2712) Fix pdf alignment (#2674) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
To find the origin of an object one can use the clearance level inheritance option. However, this option is not available for objects with L0. When an object is created from an object with clearance level inheritance, but got L0, it is still useful to know where the inheritance of 0 came from (just as it is from L2 to L1).
Describe the solution you'd like
Showing the trail/graph path/inheritance for L0 objects.
Describe alternatives you've considered
None
Additional context
Following up on #501
The text was updated successfully, but these errors were encountered: