> If you tell us exactly what you need to interface directly > with libsmedia for it would help, ie what kind of service or > application are you building on top of it.
libsmedia.so is used as an ugly hack to work around permission problems when sending USCSI commands to a vold controlled SCSI / ATAPI / USB or Firewire device. In old Solaris releases (Solaris 8 and older?) the console user (with UID != 0 !) was allowed to send USCSI commands to a vold controlled "SCSI" device. It was possible to implement the CSS authentication protocol using USCSI commands on /vol/* devices, to allow DVD playback for encrypted media for non-root users. AFAIR, in S9 this hole was fixed, and you must have EUID=0 to be allowed to send USCSI commands to a vold controlled SCSI device (same restriction that applies when vold is not used and the USCSI commands is send directly to "sd"). At the same time libsmedia.so was extended to allow non-root users to send USCSI command through user level process <-> libsmedia.so <-> smserverd. (which basically re-opens the hole, it seems) See BugID 4549011, Synopsis: SunPCi needs SCSI passthru interface in Solaris 9+ http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4549011 Basically, what is needed is an implementation of the (BSD) ioctls DVD_READ_STRUCT, DVD_WRITE_STRUCT, DVD_AUTH in the Solaris "sd" driver to perform CSS authentication, without having to be root (so that a non-root user is able to playback encrypted DVDs, in case the user owns a DVD playback application that has access to the secret DVD CSS authentication keys). This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
