Garrett D'Amore wrote: > Freeman Liu wrote: >> Gary Winiger wrote: >>>> Yes. Visibility and stability of /dev/dsp will be promoted in the >>>> following phases. >>>> >>>> >>>>> When you say that only the root user can access /dev/dsp, do you mean >>>>> to say that the underlying device file is owned by root and has >>>>> permission 600? Or does the device's driver make explicit permission >>>>> checks? >>>>> >>>>> >>>>> >>>> It is owned by root and has permission 600. >>>> >>> >>> What suid 0 programs are required that are not present in S10? >>> >> I am not sure if I understand you correct. I guess you think that >> since the 600 permission, there must >> be some suid 0 applications to use it. Actually, there is no such >> applications, this file will only be >> used by sadasupport. We make the permission 600 to avoid normal users >> to open it. >> Correct me if I misunderstand you. > > If its only used internally, there was a way (IIRC) to create a > "ddi-internal-pathname" so that only in-kernel components could see > the node. I forgot the actual call, but IIRC the keyboard/mouse code > on SPARC does this. > > That might be a preferable solution, or at least worth investigation. Actually, we have thought about that solution. The main reason that we take the current approach is that /dev/dsp will be promoted to public interface in the following phases and this approach will make the migration smooth with only trivial change.
Best regards Freeman > > -- Garrett >> >> Best regards >> Freeman >>> Gary.. >>> >> >
