|
Title: security update scheduled for 27 May 9:00 GMT Post by: SirEmi on May 26, 2006, 07:35:01 PM The commanders logged in during the security update will need to login again, at that time.
The update will take less than a minute, as usual After this update, any Space Odyssey account will be virtually inpenetrable to any attack, using a custom encryption method, and a combination of cookie, or no cookie security, depending on your browser settings. No cookies will be required, as usual, tough allowing them will increase your security a lot... Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Seither on May 27, 2006, 03:03:15 AM cookies=good, people who don't allow them are paranoid. And glad to hear it Sir Emi, now we won't have any more hackers (hopefully). Btw, any word on council yet? You projected it to be added on this weekend a while back, I'm just wondering how it's coming along, especially since it's the big update that everyone has been waiting for.
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Chronos on May 27, 2006, 03:21:14 PM I got this when I tried to go to another page after my session expired.
Warning: fopen(session/1024269015) [function.fopen]: failed to open stream: No such file or directory in /home/siremi/public_html/my_session.php on line 53 Warning: filesize() [function.filesize]: stat failed for session/1024269015 in /home/siremi/public_html/my_session.php on line 54 Warning: fread(): supplied argument is not a valid stream resource in /home/siremi/public_html/my_session.php on line 54 Warning: fclose(): supplied argument is not a valid stream resource in /home/siremi/public_html/my_session.php on line 55 Incorect username or password! Back Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Seither on May 28, 2006, 11:51:05 PM It'll probably go away. Those come up after updates sometimes, then they never appear again.
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Chronos on May 28, 2006, 11:54:13 PM It's fixed now, but it was happening consistantly. He also changed the color scheme of that page.
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Seither on May 31, 2006, 02:46:16 PM That might be why. But like I said, they pop up from time to time after updates, usually gone in a day.
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Lammalord on May 31, 2006, 06:23:16 PM at one time i got that 2 its gone now
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Seither on June 02, 2006, 07:35:41 AM yea, they pop up on occasion...though they never seem to really do any harm.
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: ars68 on June 02, 2006, 10:41:42 PM sir e, is it by any chance that these cookies are the cause of all these problems recently? that these cookies are somehow messing witht he game, forcing it to go into maintenance constantly?
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Lammalord on June 03, 2006, 03:10:07 AM i cant wait, is it over yet these random crashes on market and mission is real annoying this morning i wasted 500 turns to figure out there was absluty no encounters... (but got it all back when the votes let me go 2x in a row
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Chronos on June 03, 2006, 04:05:46 PM Two mistakes often equals one nonmistake-amajig.
But being hacked would cause a lot more losses than a few bugs, I do believe. Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Lammalord on June 03, 2006, 04:17:16 PM wow i really scwered up what i was typing there :p i cant even understand what i was trying to say sorry
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Chronos on June 03, 2006, 06:24:10 PM I got the gist of it. You wasted 500 turns through a glitch and got them back through a different glitch.
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Lammalord on June 03, 2006, 09:38:45 PM yep thats excally what happened :p
Title: Re: security update scheduled for 27 May 9:00 GMT Post by: Seither on June 06, 2006, 03:04:22 AM Well, it's fixed, so no worries now.
|