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

Reduce severity classes #1285

Merged
merged 5 commits into from
Sep 2, 2020

Conversation

janowagner
Copy link
Member

@janowagner janowagner commented Sep 1, 2020

The list of supported severity classes is reduced by removing last remains
of "classic" (deprecated since v8.0) and by removing "bsi" which is actually the same as "nist".

This cleans code and UI, without removing functionality.

The XML element "severity_class" will be empty in case
security class is "bsi".
The class "classic" was remove with gvmd version 8.0 and
the migrator replaced all occurances by class "nist".
Copy link
Contributor

@mattmundell mattmundell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be confusing to users who have BSI as their "Severity Class" setting. But I guess you're going to remove that in subsequent PRs.

@mattmundell mattmundell merged commit 606b2e7 into greenbone:master Sep 2, 2020
@janowagner
Copy link
Member Author

This could be confusing to users who have BSI as their "Severity Class" setting. But I guess you're going to remove that in subsequent PRs.

The only confusion can happen in "My Settings", which is addressed by greenbone/gsa#2434 .
The actual classification is identical.

@mattmundell
Copy link
Contributor

The only confusion can happen in "My Settings", which is addressed by greenbone/gsa#2434 .

Nice. So they will still appear in GMP GET_SETTINGS. How about removing the BSI settings from the db?

@janowagner
Copy link
Member Author

Nice. So they will still appear in GMP GET_SETTINGS. How about removing the BSI settings from the db?

on my agenda, but related to another aspect.

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

Successfully merging this pull request may close these issues.

2 participants