Correctly disable UDS_ACCESS being set
ClosedPublic

Authored by davidedmundson on Mar 3 2020, 6:17 PM.

Details

Summary

718abcb69b78385123dd7a05a66a656af772d581 tries to disable UDS_ACCESS
being set. See the long comment introduced.

It did this by setting the value to -1 which doesn't achieve that
result.

-1 is a perfectly valid value that gets send to the client.

Having it set breaks anyone calling udsEntry.numberValue(UDS_ACCESS,
aLegitimateDefault) getting their default. Something used by kio-fuse.

Test Plan

Used kio-fuse
Opened a samba file in mplayer
It opened

Opened a text editor in kate (using regular kio)

Diff Detail

Repository
R320 KIO Extras
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
davidedmundson created this revision.Mar 3 2020, 6:17 PM
Restricted Application added projects: Dolphin, Frameworks. · View Herald TranscriptMar 3 2020, 6:17 PM
Restricted Application added subscribers: kfm-devel, kde-frameworks-devel. · View Herald Transcript
davidedmundson requested review of this revision.Mar 3 2020, 6:17 PM
davidedmundson edited the test plan for this revision. (Show Details)Mar 3 2020, 6:21 PM
sitter accepted this revision.Mar 3 2020, 6:44 PM

I am pretty sure I picked that up somewhere, might be worth asking lxr for possible other places we set ACCESS to -1

This revision is now accepted and ready to land.Mar 3 2020, 6:44 PM
This revision was automatically updated to reflect the committed changes.

I am pretty sure I picked that up somewhere, might be worth asking lxr for possible other places we set ACCESS to -1

grep through kio/kio-extras doesn't reveal this being a pattern.

Yeah, can't find anything either, I may be thinking of the numberValue query in CopyJob, so entirely unrelated.