https://bugs.kde.org/show_bug.cgi?id=422554

            Bug ID: 422554
           Summary: permission order in usershare_acl
           Product: frameworks-kio
           Version: 5.70.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kio-bugs-n...@kde.org
          Reporter: yyc1...@gmail.com
                CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY

To be fair, I'm not sure if this should be frameworks/kio or
network/kdenetwork-filesharing .

The permissiong window shows an "everyone" as well as an entry for each samba
users with the "everyone" being the first one. The GUI strongly suggests that
different permissions can be configured for different users with the everyone
as fallback.

However, in the generated usershare_acl, everyone (S-1-1-0) is also the first
one, before any user ones. Even though I haven't been able to find the document
for this configure field yet, from local testing, this field is order sensitive
and samba will use the first match. This essentially means that as long as the
"fallback" is set, it'll be used for everyone...

STEPS TO REPRODUCE
1. Configure samba usershare
2. Share a directory from dolphin properties dialog
3. Change everyone to deny and the user to read/write (note: might need to
workaround
https://invent.kde.org/network/kdenetwork-filesharing/-/commit/447735830b0749f0d896dd9408c3287f66d496e9#note_56261)

OBSERVED RESULT
The user will not be able to access the share.
Moving the `S-1-1-0:d` in usershare_acl in the samba usershare configure file
to the end fixes this.

EXPECTED RESULT
The user should have read/write permission whereas no one else should.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Samba version 4.12.3

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to