PacketFence - BTS - PacketFence | ||||||||||
View Issue Details | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||
0001304 | PacketFence | captive portal | public | 2011-10-11 09:48 | 2015-02-13 15:39 | |||||
Reporter | obilodeau | |||||||||
Assigned To | ||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |||||
Status | closed | Resolution | open | |||||||
Platform | OS | OS Version | ||||||||
Product Version | ||||||||||
Target Version | Fixed in Version | |||||||||
fixed in git revision | ||||||||||
fixed in mtn revision | ||||||||||
Summary | 0001304: guest account expiration improvements | |||||||||
Description | With current temporary_password schema, we can't see if a code was used, codes can be used more than once (within expiration limit), etc. This can cause problems especially if you want to ban a guest within his allowed period. For example: - evil guest uses code - evil guest's associated node is unregistered by an admin - evil guest can still re-authenticate Should we add an expired status to the node table? Or implement the same status in temp_pass as in activation_code? | |||||||||
Steps To Reproduce | ||||||||||
Additional Information | ||||||||||
Tags | No tags attached. | |||||||||
Relationships |
| |||||||||
Attached Files | ||||||||||
Issue History | ||||||||||
Date Modified | Username | Field | Change | |||||||
2011-10-11 09:49 | obilodeau | New Issue | ||||||||
2011-10-11 09:52 | obilodeau | Relationship added | child of 0001305 | |||||||
2015-02-13 15:39 | lmunro | Note Added: 0003770 | ||||||||
2015-02-13 15:39 | lmunro | Status | new => closed |
Notes | |||||
|
|||||
|
|