PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001304PacketFencecaptive portalpublic2011-10-11 09:482015-02-13 15:39
Reporterobilodeau 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001304: guest account expiration improvements
DescriptionWith 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
TagsNo tags attached.
Relationships
child of 0001305closed  guest management improvements 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-10-11 09:49obilodeauNew Issue
2011-10-11 09:52obilodeauRelationship addedchild of 0001305
2015-02-13 15:39lmunroNote Added: 0003770
2015-02-13 15:39lmunroStatusnew => closed

Notes
(0003770)
lmunro   
2015-02-13 15:39   
Closing old bugs.
If we haven't fixed them in four years they are either not a bug, no longer relevant or not worth it.