| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001364 | PacketFence | core | public | 2012-01-11 09:49 | 2015-02-18 10:55 |
|
| Reporter | obilodeau | |
| Assigned To | | |
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001364: our Config::IniFiles usage is not bullet proof |
| Description | See 0000960: "Using ->ReWriteConfig instead of ->WriteConfig in pfcmd could've fixed it however I just read that both don't perform locking or transaction control so it would be worse if we read an incompletely written file then modify it and write it back."
See https://metacpan.org/module/Config::IniFiles#BUGS [^]
Because Config::IniFiles performs no locking, the following would be possible: someone makes a change between the time pfcmd reads and write another change. The original change would be lost.
Because pfcmd reads, performs the change then writes. Chances are probably very low that someone ever got bitten by this. |
| Tags | No tags attached. |
|
| fixed in git revision | |
| fixed in mtn revision | |
|
| Attached Files | |
|
Relationships 
Relationships 