On Tue, 28 Feb 2012, Bryen M Yunashko wrote:
And the time issue isn't just about timezones, but also about changing time itself and/or syncing up to NTP. And from an administrated-machine standpoint, there may be reasons why we don't want our users to fiddle with the clock itself.
Oh, I get the part about the clock. However, I am not suggesting the user shall change time or date, I am focusing on timezone here. If this requires the same set of privileges, the security design may be in need to some love and care. I'm also fine having a more liberal default when the underlying device is detected to be portable (notebook, tablet,...). Just treating Daniela's or "significant other"'s notebook like one of those multi-user UNIX servers in the old days does not make sense. Those could not be hauled around nearly as easy to begin with. :-)
As for printers... I see the issue being installation of drivers. If we're setting up a printer which has a driver already installed on the machine, then no, password should not be required like that.
Great, we agree on that.
But if setting up the printer means downloading the driver... then it should be treated the same way as any other software installation which requires system authentication.
And I can agree on that. Installation of new software, not yet on the systems or authorized somehow (for example, Linus could have put all acceptable drivers somewhere on the machine for the system to pick up in case of need) is a different beast. Let's focus on the simple cases for now: Timezone (not clock) and printers (no new drivers). Gerald -- Dr. Gerald Pfeifer <gp@suse.com> || SUSE || Director Product Management -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-gnome+owner@opensuse.org