| Summary: | Do no permission checking if filesystem is mounted with noperm | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | mike |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdelibs-bugs-null, mike |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
mike
2017-03-12 09:02:27 UTC
checking the source code I think in this case kfileitem is wrong in this case: the methods isReadable and isWritable return false only if it is absolutely sure it is not readable or writeable (the exception remote file is explicitly written in the method documentation, so this one is not a wishlist but a bug) The kmountpoint class would give all required information (the noperm mount option), how expensive it would be to request that information I am not able to tell. Maybe the KMountPoint should add one or two FileSystemFlags: isRemote and supportsAcl. Until kio supports nfs4 acls I would also not consider acl checking locally if fs is mounted with nfs4 and sec=krb5 (=return true for isReadable and isWritable) Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |