English « Bug tracker «
Logged in status error?
visitors automatically logged in
Bernard,
An issue has come up a couple of times now that I can't quite understand at all.
Last night I asked a friend to visit my site and look around and give me any advice they might have. We were talking over the telephone and he asked me if he was supposed to be logged in as 'xxxxx' (my admin name). Somehow just bringing up the page caused him to not only see the site but also have full administrative access.
Luckily it was a friend, and luckily I don't really have any traffic yet since the site isn't launched.
This happened to me once before that I noticed when I was using a colleagues PC at my day job, and I thought it was just some error on my part, but now I've confirmed that it does happen.
This could be a serious issue for people that use YACS for commercial/business sites.
An issue has come up a couple of times now that I can't quite understand at all.
Last night I asked a friend to visit my site and look around and give me any advice they might have. We were talking over the telephone and he asked me if he was supposed to be logged in as 'xxxxx' (my admin name). Somehow just bringing up the page caused him to not only see the site but also have full administrative access.
Luckily it was a friend, and luckily I don't really have any traffic yet since the site isn't launched.
This happened to me once before that I noticed when I was using a colleagues PC at my day job, and I thought it was just some error on my part, but now I've confirmed that it does happen.
This could be a serious issue for people that use YACS for commercial/business sites.
Bernard Paques | I have not been able to reproduce this symptom on my own servers up to now, therefore the questions... Maybe I will introduce a specific debug version to be used at your site...
|
Bernard Paques | * Cookies and (Apache) caching - Some Plone developers suggests the issue may be related to Apache. I have implemented tonight the Vary: header to protect from this potential bug. * Site Server Users May Be Authenticated Under the Wrong Account - This page, while coming from Microsoft, explains how proxies and cache engines that can unduly save Set-Cookie headers, will corrupt security * Proxy Caching May Cause Multiple Clients to Receive Same GUID - Microsoft suggests to update their servers; I know, your ISP is Unix... * How does Squid deal with Cookies? - Squid seems to have no problem with this * Installing phpBB 2.0.6 - Apache version 2 has some issue with cache directives; but your ISP is using version 1 anayway... The next step is to spread an updated version of YACS, and to wait for your feed-back..
|
Bernard Paques |
|
Bernard Paques | - the session id is changed to stop some cookie attacks (shared/global.php) - session data is killed after one hour of inactivity (shared/global.php) - workstation IP address is recorded and checked to prevent cookie spoofing (shared/surfer.php) - YACS instance is recorded and checked to prevent cross-impersonation (shared/surfer.php) These features have been introduced in February while I was working on adding a demonstration instance of YACS to this server. Because of all these protections, I think that the issue you have described is related to invalid behavior of cache/proxy servers between workstations and the YACS server. A possible explanation of the symptom you have described is that some cache/proxy server unduly cache pages fetched by you, and serve these pages to anonymous surfers afterwards. Therefore, I would recommend you to change the configuration of your server and to disable cache. Performance will be degraded, of course, but at least all requests would be transmitted to the origin server itself, and the issue you have experienced should not happen anymore. Also, while YACS strictly implements HTTP protocol specifications, I suspect that some cache/proxy appliances do not. Let me dig into Google to find if we could find some workaround to benefit from cache speed while preserving security. To summarize on this hot topic: - disable cache NOW to secure your server - let me revert to you ASAP on additional findings
|












