Bug 154205 - Dolphin does not honour absence of execute permission of directory in some cases
Summary: Dolphin does not honour absence of execute permission of directory in some cases
Status: RESOLVED DUPLICATE of bug 173733
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.9.2
Platform: Chakra Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: reproducible
Depends on:
Blocks:
 
Reported: 2007-12-17 02:31 UTC by Shriramana Sharma
Modified: 2013-06-15 13:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shriramana Sharma 2007-12-17 02:31:29 UTC
Version:            (using KDE KDE 3.97.0)
Installed from:    Ubuntu Packages
OS:                Linux

Steps to reproduce:

1. In Konsole do: mkdir /tmp/foo
2. Open Konqueror
3. Go to /tmp or to /tmp/foo
4. In Konsole do: chmod -x /tmp/foo
5. Try navigating into /tmp/foo from elsewhere in Konqueror.

Expected result:

I should not be allowed into the /tmp/foo folder.

Actual result:

I am allowed.

Notes:

1) Problem persistent till closing all Konqueror windows:

I have to entirely close all existing windows of Konqueror and then restart Konqueror to make it recognize the no-entry permission on the directory. Simply navigating elsewhere in the same tab, opening a new tab, or trying a new Konqueror window without closing the old one are all ineffective in making Konqueror recognize the new permissions.

2) Problem does not arise until first stat of directory by Konqueror

Also, unless Konqueror at least once reads the permission of the folder, this behaviour is not seen. That is, if I skip step 3 or go anywhere other than /tmp or /tmp/foo in step 3, then after step 4 and step 5 I am denied access, which is the accepted behaviour.

3) Konqueror recognises +x change, only not -x change

That is, if before step 2 I add a chmod -x /tmp/foo and then at step 4 I do chmod +x /tmp/foo and try step 5, then Konqueror sees the new permissions of the folder and allows me inside, where it did not allow me before.
Comment 1 Shriramana Sharma 2007-12-17 02:38:50 UTC
I should note that this exists in KDE 4 also, I checked in the KDE 4 RC 2 Kubuntu Live CD via VirtualBox. So with all this talk about closing KDE 3 bugs, kindly don't close this one too.
Comment 2 Jaime Torres 2008-07-24 20:27:36 UTC
I've been able to reproduce it in konqueror and dolphin svn trunk 831729.
I think both use some kind of cache of the visited directories, therefore until the refresh button is not pressed (or the directory info is gone from the cache), they use the cache and does not notice the directory new rights (this is only a guess).
Comment 3 Shriramana Sharma 2009-04-12 21:03:36 UTC
Hello. I am the reporter of this bug. I confirm that this exists in KDE 4.2.2 but only if I navigate to /tmp/foo in step 3, not if I just go to /tmp. Please fix this. Thanks for all your great work on KDE!
Comment 4 Dawit Alemayehu 2012-01-03 16:33:21 UTC
This is an issue in the Dolphin KPart used by Konqueror for file management.
Comment 5 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:18:41 UTC
Resetting assignee to default as per bug #305719
Comment 6 Frank Reininghaus 2012-10-27 08:25:34 UTC
I confirm, but I believe it's actually an issue in KDirLister. Dolphin itself doesn't check the permissions, it only asks KDirLister to open the URL and list the files.
Comment 7 Dawit Alemayehu 2013-06-15 13:55:13 UTC
Fixed when it bug# 173733 was fixed.

*** This bug has been marked as a duplicate of bug 173733 ***