PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001171 | PacketFence | captive portal | public | 2011-02-02 16:49 | 2012-10-19 15:15 |
| Reporter | obilodeau | ||||
| Assigned To | fgaudreault | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0001171: authentication::radius should support "encrypted" RADIUS authentication | ||||
| Description | Right now our authentication::radius module seems to be doing only plaintext password checking. RADIUS supports other means which are encrypted*. We rely on Authen::Radius for RADIUS Authentication but we would probably need to find a better client module that supports CHAP. Then again it might be something that is negotiated at the server side then we should try to make it work and document how to do it. It was requested on the mailing list. *: the means are considered insecure but it's better than to see cleartext passwords in freeradius' debug output | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2011-02-02 16:49 | obilodeau | New Issue | |||
| 2011-03-03 15:15 | obilodeau | Target Version | 2.1.0 => +1 | ||
| 2011-03-03 15:18 | obilodeau | Target Version | +1 => +2 | ||
| 2012-10-19 13:03 | fgaudreault | Note Added: 0003167 | |||
| 2012-10-19 13:03 | fgaudreault | Status | new => resolved | ||
| 2012-10-19 13:03 | fgaudreault | Resolution | open => fixed | ||
| 2012-10-19 13:03 | fgaudreault | Assigned To | => fgaudreault | ||
| 2012-10-19 15:15 | fgaudreault | Target Version | long-term => | ||
| Notes | |||||
|
|
|||||
|
|
||||