Fix for KCookieJar's Year 2038 (Y2K38) problem...

Dawit A. adawit at kde.org
Sun Dec 13 14:30:30 GMT 2009


Hi all,

The attached patch is a fix for the so called Y2K38 (Year 2038) problem in 
kcookiejar due to the use of a 32-bit time_t variable to store the expiration 
date. Currently, if any site sets a cookie expiration date greater than 
03:14:07 Tuesday, 19 January 2038, then the cookie will simply be deleted by 
kcookiejar because the 32-bit overflow will "wrap-around" its expiration date 
to be set in the past...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20091213/0b3fe80f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kcookiejar_y238k_fix_43branch.patch
Type: text/x-patch
Size: 7320 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20091213/0b3fe80f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kcookiejar_y238k_fix_trunk.patch
Type: text/x-patch
Size: 7318 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20091213/0b3fe80f/attachment-0001.bin>


More information about the kde-core-devel mailing list