Rajko M. wrote:
> On Monday 30 March 2009 01:39:45 pm Stef Bon wrote:
>
>> Rajko M. wrote:
>>
>>> It is common practice in Linux to create own account (seat) for each
>>> service that is potentially dangerous. That way you can limit access to
>>> only few files and directories that such service needs.
>>>
>> Read the documentation. ConsoleKit is a tool to track seats,
>> (keyboard/mouse/display combinations) not to track daemons/services.
>>
>
> OK, then let we rename demon to process (which its) and then reread
> Chapter 2. Terminology: Session:
> " ... For example, we don't yet have a way to prevent a process from moving
> between sessions owned by the same user. ..."
>
> I'm really not keen to read all of it.
> I know that I should do it, but not right now.
>
>
I've read it, and again take a close look to the output of ck-list-sessions.
I see that I did mix session and seat. The session for me, as user
logging into KDE is another session
than the one pointed to kwrited, but they belong to the same seat. So
there is no extra seat created for kwrited.
But then again, why is an apart session created only for kwrited?
Stef
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
