Skip to content
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

Channel element in manifests #53

Open
frendguo opened this issue Mar 4, 2024 · 3 comments
Open

Channel element in manifests #53

frendguo opened this issue Mar 4, 2024 · 3 comments

Comments

@frendguo
Copy link

frendguo commented Mar 4, 2024

Why doesn't -> in the manifest file contain a description of the channel type? Please.

@AndrewRathbun
Copy link
Collaborator

What exactly are you referring to? Can you provide a screenshot of what's missing and what exactly you think should be there?

@frendguo
Copy link
Author

frendguo commented Mar 5, 2024

@AndrewRathbun Sorry, I didn't express myself clearly.
image
As shown above, from Microsoft-Windows-Windows defender, for each channel of a provider, a channel type is needed to describe what type of channel it belongs to, Operational or Debug.
But in Channels does not have the type field.

@nasbench
Copy link
Owner

Sorry for the late response @frendguo

The missing field is due to the tool we used to dump those XML manifests. We used WEPExplorer and as you can see here the code doesn't extract the channel type into its own field from the XML. The source code needs to be modified to take that into consideration while taking edge cases (no channel assigned).

Unfortunately for now the only way to get that info so is to extract it from the path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants