Webmin and Squirrelmail use a cookie named user. So if
a user is using Webmin and Squirrelmail who are twice
installed on the same host, login page of squirrelmail
will not work as espected.
Incorrect statement. SquirrelMail itself doesn't use a
cookie named user. The only cookie SquirrelMail itself sets
is one called KEY. Their is a plugin (login_auto I believe)
that sets a cookie named "user". Please verify, and make
sure that this is the case in your setup (ie, you have that
plugin installed). I know of no core code that sets the
cookie "user".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's it. I've the login auto plugin installed and cookies
is setup from it.
I've sent a email to JayGuerette =-at-= pobox and pdontthink
"#at#" angrynerds to notify this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
But still. isn't 'KEY' a bit too generic? Maybe it doesn't
cause any problem in this case, but it'd be better to change
it to SQM_KEY or maybe even better: the configurable
<session_name> with "_KEY" appended?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That might be an idea, but not top priority. I've not seen
any conflicts, or heard of any yet. It's only been with the
PHPSESSID cookies that have had issues, which was why I put
in the session name stuff.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To summarize, the original report is not a bug in
SquirrelMail (but in a specific plugin). However there's a
feature request to change the KEY cookie to something less
generic. Reported feature request as #1091688, moving this
to the Plugins tracker.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=9879
WebCalendar also use a cookie named user. So there is an
incompatbility bitween Webmin, Squirrelmail and Webcalendar.
Logged In: YES
user_id=620333
Incorrect statement. SquirrelMail itself doesn't use a
cookie named user. The only cookie SquirrelMail itself sets
is one called KEY. Their is a plugin (login_auto I believe)
that sets a cookie named "user". Please verify, and make
sure that this is the case in your setup (ie, you have that
plugin installed). I know of no core code that sets the
cookie "user".
Logged In: YES
user_id=9879
That's it. I've the login auto plugin installed and cookies
is setup from it.
I've sent a email to JayGuerette =-at-= pobox and pdontthink
"#at#" angrynerds to notify this.
Logged In: YES
user_id=620333
It could be made configurable.
Re-assigning to Paul if he still manages it.
Logged In: YES
user_id=285765
But still. isn't 'KEY' a bit too generic? Maybe it doesn't
cause any problem in this case, but it'd be better to change
it to SQM_KEY or maybe even better: the configurable
<session_name> with "_KEY" appended?
Logged In: YES
user_id=620333
That might be an idea, but not top priority. I've not seen
any conflicts, or heard of any yet. It's only been with the
PHPSESSID cookies that have had issues, which was why I put
in the session name stuff.
Logged In: YES
user_id=285765
To summarize, the original report is not a bug in
SquirrelMail (but in a specific plugin). However there's a
feature request to change the KEY cookie to something less
generic. Reported feature request as #1091688, moving this
to the Plugins tracker.