Bug 119365 - cannot change file attributes (=delete read only files) via kio smb
Summary: cannot change file attributes (=delete read only files) via kio smb
Status: RESOLVED UPSTREAM
Alias: None
Product: kio-extras
Classification: Frameworks and Libraries
Component: Samba (show other bugs)
Version: 18.04.2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-02 10:27 UTC by Jens
Modified: 2020-02-17 15:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens 2006-01-02 10:27:49 UTC
Version:           3.4.2 (using KDE 3.4.2 Level "b" , SUSE 10.0)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.7-default

Situation: share via smb://user@host/foo/.

I want to delete a directory there (called "bar"). It contains read-only files. Konqueror complains "File 'bar/LICENSE' does not exist." (it does, though!).

IMHO: Konq should check for read-only files/dirs before starting to delete and ask if these should be removed as well.

To change permissions, I select properties, and change the properties of all selected files to "Allow show/read and change/write". Now Konq complains about "Changing file permissions on SMB protocol is not possible".

However, if I mount the directory with smbmount / CIFS I can change the file permissions both with chmod and with Konqueror. This is a missing feature, IMHO.

Please investigate if you can fix this. This might also be related to Bug 6796 (ACL support).


Thank you!

Jens
Comment 1 Jens 2006-01-02 10:29:46 UTC
Sorry, that was Bug #6976.
Comment 2 Thiago Macieira 2006-01-02 12:51:12 UTC
changing to wishlist: chmod support in kio_smb
Comment 3 Harald Sitter 2020-02-17 15:27:12 UTC
Upstream libsmbclient doesn't support chmodding since that wouldn't be portable to windows hosts. Until that changes we cannot support that. The reason it works when mount is because samba (the server) has the ability to add unix specific extensions which would then allow chmodding in so far as a client (e.g. samba) implements those extensions as well. The kernel-side cifs which is used when mounting uses the extensions, libsmbclient does not. Ultimately that needs taking up with the samba authors. Until they add extension support to smblclient there's simply no way for us to support chmod over smb.

All that said, if the linux system supports and uses ACLs then bug #40892 comes into play as supporting NT ACLs will be a portable way to control file permissions regardless of server (samba server-side translates POSIX ACLs to NT ACLs for the purpose of SMB).