On 01/19/2013 03:48 AM, Randy McMurchy wrote: > Hi all, > > My apologies right here at the beginning if this subject has been discussed > and I missed the discussion. I am curious about BLFS' view on the obsolete > and deprecated package ConsoleKit. ConsoleKit is listed as a dependency for > several BLFS packages, and recommended for at least one package. The issue > is the package is unmaintained. > > We (BLFS) list ConsoleKit in the "Security" section of the book. It would > seem to me that packages in the "Security" section would have a solid base > behind it, and the package would be looked at closely. However, because > ConsoleKit is now abandoned, deprecated, and apparently has been replaced > by the systemd package (which BLFS doesn't support), it seems that this > would be a security hole. > > I am not saying that the current BLFS situation with ConsoleKit is a security > hole, I am just saying that it could turn in to one. I would like a discussion > about the future of our direction toward the ConsoleKit deprecation, and the > apparent move by most other distribution's move toward systemd. > > If anyone is interested in discussion, I encourage your participation. >
Well, ConsoleKit is required for every desktop. It is used by D-Bus and PolicyKit to identify local sessions and grant privileges. If your session is not registered with ConsoleKit, you will likely get "Permission denied" in lot of Desktop stuff like device mounting, network manager management, etc ... In short, it is used to track sessions and help D-Bus and PolicyKit to work correctly. But, it has been obsoleted by systemd-logind. I've raised a thread or two about this but every time systemd was rejected. From what I know, Ubuntu won't be switching to systemd and I think that Canonical's Martin Pitt wwas about to maintain ConsoleKit. Only maintain - not improve or such ... -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
