Mailinglist Archive: opensuse (1165 mails)

< Previous Next >
[opensuse] Re: Should openSUSE review it's Security Policies?
  • From: Joachim Schrod <jschrod@xxxxxxx>
  • Date: Tue, 06 Mar 2012 19:19:50 +0100
  • Message-id: <jj5kg7$v2a$>
Rasmus Plewe wrote:
On Tue, Mar 06, 2012 at 08:35:07AM +0100, Per Jessen wrote:
Frans de Boer wrote:

[big snip]
Where are the people who care about normal
end-users who use the computer as a tool only.

Look at this discussion, that shouldn't have been a discussion to begin
with. "A desktop user should be able to do desktoply things." He can
touch the hardware, so, from a technical point of view, what kind of
security is there, anyway?


But that wasn't the discussion, at least not its start.

Linus does *not* want to give his daughter full root access. But he
wants her to be able to do things that the default 12.1 policy

As Marcus wrote, this is actually often not even a policy problem,
but the user interfaces didn't change fast enough to support newer
low-level service facilities, e.g., system vs. user connections in
NetworkManager. He didn't address the issue if those newer
facilities should have been used as default, though.

IMHO, the issue is more how new facilities are introduced in
openSUSE. If a new facility breaks some other software or
introduces a regression, are the other software's maintainers
responsible to care for it, or is it the person/group that
introduces the change. When somebody introduces system network
connections and makes them default, he has to take care and
coordinate changes in GUIs to make them usable again.

Btw, We had plenty arguments for both sides when systemd was
introduced. This ain't a new discussion. For the record, I like the
Linux kernel approach: If your new code breaks something, you have
to fix it, not some other guy.


Joachim Schrod Email: jschrod@xxxxxxx
Roedermark, Germany

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups