Home_greyopenFATE - openSUSE feature tracking > #312876
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Deny individual users' access to screen-saver settings

Feature state

openSUSE Distribution
Unconfirmed

Description

This is an extension of Feature #312871, but because it's a little more involved than changing a simple default, I thought it would be better to have a separate feature request.
The screen-saver settings for time-out and "require password" are security settings that really should not be freely available to the individual user. I propose that we
1) set a reasonable default (60sec, 15sec, always require passwd) (see Feature #312871) and
2) only let these settings be modified by someone with root-access.

To a regular user, the timeout and "require password" settings should appear "greyed out", clearly indicating "not available".

User benefit:

This is simply a reasonable security measure, fitting nicely into the overall security-conscious profile of openSUSE. Security measures (firewall, apparmor, encryption etc) are typically accessible only with root-access; it's only sensible that we apply this principle to the screen-saver settings too.

Usecase

Office user - the user is able to select a screen-saver, but the other settings cannot be accessed, accidentally or otherwise. The install or admin person need not change anything to get a sane security setup for the desktop.

SOHO or home users - same as above, but the default screen-saver settings may be changed by switching to root access.

Discussion


icons/user_comment.png T. R. wrote: (2 years ago)

I think this is backwards. If offices or home users think it is that important to prevent users from changing their screensaver settings, then they can use kiosk to prevent it. If they have that serious of security concerns they should be using kiosk to prevent dangerous actions anyway, so this shouldn't be much additional trouble (it took me about ten seconds on google to find the relevant kiosk settings).
However, implementing this makes it extremely difficult in environments where screen locking is not important. For most home users this would add zero security benefit but a ton of hassle. It also makes things very difficult for offices that think users can make their own judgment about whether a screen locker helps or hampers them, and this would wreck security models that prevent users from having root access.
So if we keep things as-is it is fairly easy to add restrictions to prevent changing the settings, so the burden on people who want the feature is small. However, if we go with this suggestion, then it adds a huge burden to people who don't want it.

Things like apparmor, disk settings, and firewall are things that users should never have any need to touch. But desktop customization settings, like screensavers, are things that users very often do change and are often allowed to change to suit their own work habits. You may think that preventing users from changing their locker settings is an important measure for security, but that is up to each office to decide and implement. The tools to do so are already available.

icons/user_comment.png P. J. wrote: (2 years ago)

I wasn't aware of Kiosk, thanks. I disagree with most of the rest you're saying though. To accommodate both sides, perhaps we could simply make this a tickbox at installation-time.

icons/user_comment.png P. J. wrote: (2 years ago)

Todd, could you get in touch by email, please? I've been reading up on Kiosktool, which looks quite promising, but I've spent way more than ten seconds googling :-), so a link to howto or similar would be really cool. The tool kiosk gui itself doesn't seem entirely intuitive, at least I couldn't find any of the settings I needed.

icons/user_comment.png R. M. wrote: (2 years ago)

If a user is keeping it's session open for others then it affects user's security only. IMO it's usually not root's part to protect the user from himself.

Teaching the user to do better would be enough.

icons/user_comment.png P. J. wrote: (2 years ago)

Sorry, but you are wrong - if a user does not lock his screen when he is a way from it, it exposes/endangers everything to which this user has access.
Wrt teaching users - my experience tells me that it isn't possible and also rarely accepted accepted by a security auditor.

icons/user_comment.png R. M. wrote: (2 years ago)

> [...] it exposes/endangers everything to which this user has access.

That's exactly what I've said. It _only_ affects what the user has access too.

icons/user_comment.png P. J. wrote: (2 years ago)

There is surely a reason why we give people passwords (namely to protect their data and privileges). Most users in an office environment will be trusted with data other than their own. Why protect all of that with a password if the user can just (accidentally or otherwise) leave it for everyone to peruse.

icons/user_comment.png M. M. wrote: (2 years ago)

This is something where a system wide (root modifyable) policy setting
woiuld be used to either deny/allow users these changes.

for openSUSE in homeuser setting, a good default but user-modifyable is sufficient in my eyes.

Last change: 2 years ago
Voting
Score: -22
  • Negative: 24
  • Neutral: 0
  • Positive: 2
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint