Skip to content

JSON output: no parameters for policy messages #239

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

Open
maria-messerschmidt opened this issue Apr 10, 2025 · 0 comments
Open

JSON output: no parameters for policy messages #239

maria-messerschmidt opened this issue Apr 10, 2025 · 0 comments
Assignees
Labels
fixed Believed to be fixed in current HEAD

Comments

@maria-messerschmidt
Copy link

None of the policy messages have parameters (yet). I would expect the following parameters:

POL-1: entryPath
POL-2: version (at least when sub message is ("Package version: ODF_xx detected. Package does not comply with specification. The file MUST comply with the standard "OASIS Open Document Format for Office Applications (OpenDocument) v1.3".")
POL-3: mimetype
POL-4: mimetype, extension
POL-5: NA
POL-6: NA
POL-7: NA
POL-8: entryPath
POL-9: entryPath

{
"id" : "POL-1",
"severity" : "ERROR",
"message" : "Encryption",
"parameters" : [ ],
"timestamp" : "2025-03-21 07:48 UTC",
"sub_message" : "The package MUST NOT contain any encrypted entries."
},
"path" : "settings.xml"
}

@carlwilson carlwilson added the bug Something isn't working label May 14, 2025
@carlwilson carlwilson self-assigned this May 14, 2025
@carlwilson carlwilson added fixed Believed to be fixed in current HEAD and removed bug Something isn't working labels May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed Believed to be fixed in current HEAD
Projects
None yet
Development

No branches or pull requests

2 participants