WJCarpenter-4 wrote: > > I've just started poking around the session code in > functions/global.php. Though I'm sure I can brute force something in > there with a patch, I'm not too clear on what horrible side-effects I > might trigger. For example, I'm thinking about maybe making the cookie > name unique by some reliable encoding of the login id (user foo encodes > to SQMSESSID_asdfg, user bar encodes to SQMSESSID_qwerty). > > Any thoughts? > Cookieless mode is possible, but you need changes in lots of places. Not just in global.php -- View this message in context: http://old.nabble.com/multiple-SM-sessions%2C-single-browser-tp33871738p33872085.html Sent from the squirrelmail-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
