Anonymous | Login | 2024-11-22 03:58 EST |
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 | |||
0001415 | PacketFence | core | public | 2012-04-05 11:28 | 2012-10-22 15:24 | |||
Reporter | fgaudreault | |||||||
Assigned To | fgaudreault | |||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |||
Status | resolved | Resolution | fixed | |||||
Platform | OS | OS Version | ||||||
Product Version | 3.2.0 | |||||||
Target Version | 3.6.0 | Fixed in Version | 3.6.0 | |||||
Summary | 0001415: Potential issue when reloading violations | |||||||
Description | It appears that when you reload the violations using pfcmd, the old violations are not deleted from the table, it only updates the actual violations that are in the violations.conf. To reproduce: nsert into class (vid,description) values ('31337','h@x0r'); insert into action values (31337,'email'); pfcmd reload violations select * from action where vid=31337; +-------+--------+ | vid | action | +-------+--------+ | 31337 | email | +-------+--------+ I did not try to reproduce it in lab yet. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
Relationships | ||||||
|
Notes | |
(0003222) fgaudreault (viewer) 2012-10-22 15:21 |
Duplicate of 0001555 |
Copyright © 2000 - 2012 MantisBT Group |