Anonymous | Login | 2024-08-24 22:21 EDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001417 | PacketFence | core | public | 2012-04-06 08:58 | 2015-02-13 15:42 | |||
Reporter | fgaudreault | |||||||
Assigned To | ||||||||
Priority | low | Severity | feature | Reproducibility | N/A | |||
Status | closed | Resolution | open | |||||
Platform | OS | OS Version | ||||||
Product Version | 3.2.0 | |||||||
Target Version | Fixed in Version | |||||||
Summary | 0001417: Violations whitelist concept should be replaced | |||||||
Description | Using whitelist limits more powerful violations usages. We should be able to select the categories, or even the SSID we want to enable to violation for, not just remove categories using whitelist. Potential use cases: - Enable P2P detection only on the Student and Guests Categories, and on the Open SSID - Enable Malware detection to all categories, and all SSIDs This is currently not possible using whitelist. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
![]() |
|
(0002638) obilodeau (reporter) 2012-04-09 09:26 |
Violation whitelists are not really popular so they could be reworked without too much resistance I guess. |
(0003795) lmunro (administrator) 2015-02-13 15:42 |
These bugs have been sitting untouched since 2012. Closing them and possibly reopening in github tracker where relevant. |
![]() |
|||
Date Modified | Username | Field | Change |
2012-04-06 08:58 | fgaudreault | New Issue | |
2012-04-09 09:26 | obilodeau | Note Added: 0002638 | |
2012-10-19 12:10 | fgaudreault | Target Version | => long-term |
2015-02-13 15:42 | lmunro | Note Added: 0003795 | |
2015-02-13 15:42 | lmunro | Status | new => closed |
Copyright © 2000 - 2012 MantisBT Group |