Brian Cameron wrote: > On some Linux systems, the pam_ck_connector is used to ensure that > non-graphical logins (e.g. telnet, ssh, etc.) are registered with > ConsoleKit. Thus ConsoleKit can be used as a utmp/wtmp replacement > since it stores a superset of the information as in the utmp/wtmp > database. However, this is not an appropriate use of PAM and there > are > no plans to support this feature on Solaris since there is no > immediate need to replace utmp/wtmp at this point in time. Instead, > GDM will make use of ConsoleKit to manage its displays.
I don't understand why you think this isn't appropriate use of PAM. It sounds perfectly reasonable use of a PAM session module. The fact that we don't currently update utmpx/wtmpx/lastlog properly from pam_unix_session is a bug (ironically we used to do it in 2.5.1 before PAM became public in 2.6). pam_ck_connector looks like a nicely written and very useful PAM module. I don't think this should replace utmpx/wtmpx on OpenSolaris systems but I have no problem with it augmenting them. I highly recommend that we ship pam_ck_connector. It is quite a different issue of wither or not we choose to have it configured in any of the default PAM stacks we provide in /etc/pam.conf. > ConsoleKit source code contains the programs > /usr/sbin/ck-log-system-start, /usr/sbin/ck-log-system-restart, and > /usr/sbin/ck-log-system-stop. These are intended to be helper tools > to > log system start, restart, and stop events. These are intended to > make > ConsoleKit more like utmp/wtmp which also logs these events. Since > there are no plans to support ConsoleKit as a utmp/wtmp replacement, > these programs are not included with the Solaris ConsoleKit packages. I think they should be delivered. > 4.1.6 Stop/Restart Scripts > > ConsoleKit manages stopping and restarting the system. On Solaris, > when > the display manager informs ConsoleKit that such an action is > requested, > the chkauthattr function is called to see if the calling user has RBAC > permissions for the "solaris.system.shutdown" key. If yes, then the > /usr/lib/ConsoleKit/scripts/ck-system-restart script is run if a > restart > action was requested. If a shutdown action was requested, then the > /usr/lib/ConsoleKit/scripts/ck-system-stop script is run. > > On Solaris, the ck-system-stop script runs "/sbin/init 5" and the > ck-system-restart script runs "/sbin/init 6". Why does it use init rather than shutdown which is uses on Linux and FreeBSD ? > 4.1.9 SMF integration > > ConsoleKit includes SMF integration files to start and stop the > /usr/sbin/console-kit-daemon program as a service. > > 4.2. Interfaces: > > Exported Interfaces Stability Comments > --------------------------------------- ----------- > ------------- > SUNWconsolekit Uncommitted Package > name. > SUNWconsolekit-devel Uncommitted Package > name. > SUNWconsolekit-root Uncommitted Package > name. > /usr/lib/pkgconfig/ck-connector.pc Uncommitted pkg-config > file. > /var/svc/manifest/system/consolekit.xml Uncommitted SMF > integration > file. What is the FMRI that is the important interface not the filesystem location of the manifest file. What is the method_credential section in the manifest for starting consolekit ? > 4.4. Packaging & Delivery: > > SUNWconsolekit, SUNWconsolekit-root, SUNWconsolekit-devel - packages > for ConsoleKit. Does this project intent to integrate before or after the SXCE demise ? If after then I see no reason to have SUNWconsolekit and SUNWconsolekit-root split apart since whey will just get recombined. -- Darren J Moffat
