[Pidgin] #15586: Use 64-bit value to represent times (was: Issue in parsing CA certificate)

[Pidgin]

#15586: Use 64-bit value to represent times
--------------------+---------------------------
 Reporter:  params  |       Owner:  rekkanoryo
     Type:  defect  |      Status:  new
Milestone:  3.0.0   |   Component:  unclassified
  Version:  2.10.7  |  Resolution:
 Keywords:          |
--------------------+---------------------------
Changes (by datallah):

 * milestone:   => 3.0.0


Comment:

 It's really a terrible thing to MITM all SSL traffic via a proxy, but
 that's relatively unrelated to the problem.

 The reason it's *relatively* unrelated and not completely unrelated is
 that you probably won't find real certificates in the wild that expire
 after 2038-01-19 (the 32-bit unix timestamp barrier), but your certificate
 expires in 2063 (which is not really not a sane timeframe for a current
 certificate to expire).

 It isn't actually an issue with NSS, but rather a libpurple issue and is a
 real bug.

 The libpurple API uses `time_t` to store the effective and expiration
 dates and time_t is a 32-bit number on Windows with the default C runtime.
 It's also a 32-bit number on 32-bit Linux systems as far as I can tell.

 This isn't something that can be corrected without an API change (which
 can't happen until the 3.0.0 release of Pidgin).  Part of changing this
 behavior will likely mean that we need to use the glib date/time functions
 instead of the system functions (https://developer.gnome.org/glib/2.30
 /glib-Date-and-Time-Functions.html).

-- 
Ticket URL: <https://developer.pidgin.im/ticket/15586#comment:3>
Pidgin <http://pidgin.im>
Pidgin