Hi all, This message only concerns you if you use the mgd_auth_midgard function and the MidgardLogin cookie authentication. The cookies generated by mgd_auth_midgard are set to expire on Dec 31, 1999 because when I wrote the function, the cookie spec only mentioned two-digit years. I wondered about the Y2K-issue then but forgot it soon after. In the midst of all this hype I now remembered the issue and got around to fix it. The problem forces registered users, who use cookie authentication to login again as their cookies will expire. HTTP Basic authentication is not affected. The fix: In midgard-php, file functions/midgard.c, replace the string: " Expires=Friday, 31-Dec-99 12:00:00 GMT;" with " Expires=Friday, 1-Jan-2010 12:00:00 GMT;" This will make new cookies expire in 2010. You can easily change the date yourself. Perhaps there'll someday be some additional code that sets the expiry date based on current time and a configurable expiration period. So yeah, there was a Y2K bug in Midgard after all... ;-) Seriously, Apache, PHP, MySQL and Midgard should all be reasonably Y2K safe. You won't lose any of your data and the server's will most probably stay online. Jukka -- This is The Midgard Project's mailing list. For more information, please visit the project's web site at http://www.midgard-project.org To unsubscribe the list, send an empty email message to address [EMAIL PROTECTED]
