commoncriteria / commoncriteria/transforms

Sel-based triggers from functional packages not working

Open
#136 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
XSLT
Stars
1
Forks
4
PR merge metrics
No merged PRs in 30d

Description

There is an issue with sel-based triggers from functional packages that are causing the dependency box to populate with unnecessary text. To the best of my recollection this was not previously an issue so it may have been introduced in a relatively recent transforms update and not noticed until now.

In the example below, FCS_COP.1/SKC is trying to say that its inclusion is dependent on claiming any of the numerous AES-CBC ciphersuites in the TLS package. The expected behavior is that this all gets consolidated into a single reference rather than duplicating for each individual dependency. The "work-dir of external doc =../../output" string is also obviously extraneous and shouldn't be included.

This behavior was observed across multiple updated PPs (MDM, MDF, virtualization) which makes sense because they're using the same syntax to reference the FP and are presumably all on the same build of the transforms.

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the dependency-box output for the FCS_COP.1/SKC example described in the issue and trace the transform handling of sel-based triggers from functional packages. Done means consolidating the AES-CBC dependency into one reference and omitting the extraneous "work-dir of external doc =../../output" text.

Written by the indexing model from the issue text.

Assessment

Tech stack
xml
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.