2012-02-21 - [GRASE-Hotspot] #61: When clock goes backwards, things break

Header Data

From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: 55b0a2581d85d08fe26b9e6d28bd52e041c42179ab20a44ae0ed3a1c9b27cb03
Message ID: <039.c9f42a82ca3dc50f3172ecb700805b7d@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2012-02-21 21:27:25 UTC
Raw Date: Wed, 22 Feb 2012 04:27:25 -0000

Raw message 

#61: When clock goes backwards, things break
---------------------------+-----------------
 Reporter:  tim            |      Owner:  tim
     Type:  defect         |     Status:  new
 Priority:  minor          |  Milestone:  3.8
Component:  Other Backend  |    Version:  3.6
 Keywords:                 |
---------------------------+-----------------
 A bit of a corner case, but will cause problems on some devices.
 If the clock goes backwards (i.e. no battery for CMOS clock) and things
 like ntp don't work properly (maybe internet is down when it boots up)
 then we end up with sessions that are just plain wrong due to them being
 as far back as 12 years (Jan 2000).
 We need to detect if time has gone backwards by more than say 2 hours
 (plenty of leeway for daylight savings), prehaps by testing if now() is
 more than 2 hours before the last successful login to the hotspot. If so,
 we deny logins and ask the administrator to set the time manually? So in
 Radius we reject logins with error "time has gone backwards" maybe with a
 link to the admin area, were we again detect time having gone backwards
 and ask the administrator to set the time correctly, with the option to
 override it (i.e. by placing a special login session?)

 Not sure how to make all this happen, as CoovaChilli will also get the
 reject message, as it authenticates for settings.

-- 
Ticket URL: <http://trac.grasehotspot.org/ticket/61>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker

Thread