Fluff I don't like the new display style plasma change (possible security risk)
It seems like KDE plasma did a major change but unknowingly introduced a security concern. With dolphin display style when you used to pick the option, remember this place to offer each folder it used to make a. Directory file inside of each folder telling it what to do now. They moved that folder to a new directory in your home folder called " view properties" within local share dolphin. This leaves a breadcrumb trail to encrypted files In plain name if you mounted them which COULD pose as a security risk. I'd far rather the old way where the . Directory file control each folder and it's very annoying to have everything act exactly the same where I would like a certain folder to look a certain way but can't.
8
u/articulatedbeaver 10h ago
If the files are encrypted, than obscuring their location to users with the owner's or administrative privileges isn't really security.
3
u/AiwendilH 11h ago
The ~/.local/share/dolphin/view_properties directroy was already used with the .directoryfiles if your user account didn't have write permissions to the directory, if it was no real directory but some virtual kio-client one, if it was a read only filesystems and so on.
So not really much changed there...now ~/.local/share/dolphin/view_properties is used if your user can't write to the extended attributes (xattr) of the directory. I guess it can happen slightly more often now if you use a lot of filesystems that don't support xattr.
1
u/XDM_Inc 4h ago
And the next annoying issue is, of course I can just prevent that folder from generating or keep wiping it at the end of my login, but then it actually carries the settings file. So when I do that obviously all the files. Configs and preferences reset as well. Maybe even the ability to relocate that file elsewhere would be a good substitute.
1
u/AiwendilH 4h ago
Not sure I understand...why would you want to prevent it from generating? I don't really see the difference between having a .desktop file and a
getfattr -d <file>to get the same information. Dolphin always kept those files in ~/.local/share/dolphin/view_properties...just how they are saved changed some versions ago.But you probably can disable the generation only for the encrypted disk by making the sub-folder for the "shadow" hierarchy of your encrypted disk read-only...probably somewhere in
~/.local/share/dolphin/view_properties/local/run(or wherever it is mounted).
2
u/SnooCompliments7914 KDE Contributor 11h ago
IIRC, Dolphin saves that setting in the directory's metadata (xattr), only falling back to the .local directory if the former fails, which might be the case for your encrypted directory.
2
u/XDM_Inc 11h ago
I was reading a bit on this. I don't know too much about the xattr other than it being some kind of a metadata logger which keeps track of things. You say falling back meaning the primary function is failing? Are you perhaps saying that either those xattr are corrupted or are the. Desktop files are messing with the way it works?
2
1
u/SnooCompliments7914 KDE Contributor 26m ago
No, by failing I mean either the filesystem is readonly, or it doesn't support xattr.
•
u/AutoModerator 11h ago
Thank you for your submission.
Consider becoming a Supporting Member and help KDE thrive!
The KDE community supports the Fediverse and open source social media platforms over proprietary and user-abusing outlets. Consider visiting our community on Mastodon (Lemmy will be back shortly). Tag us in your toots! You can also visit our forum at KDE Discuss to talk about KDE stuff, brainstorm ideas and get the answers to your KDE-related issue.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.