> >We're not aware of any unrelated applications that pass DLPI descriptors. > >If the need arises, a routine can be added to make it possible to convert > >a file descriptor to a DLPI handle. > > Is there any chance of us being able to implement something as part > of this project rather than wait for a "call" and have to react ? > > I suppose there's the question of what should it look like, if > we don't yet have something to use it, to complicate matters :-/
Yes. As a rule, I don't believe in building APIs without consumers. > First, /etc/security/device_policy does not always match the > list of network interfaces available. My desktop has nge0 > (from SUNWnge) but device_policy does not. This is quite > possibly a bug in packaging and/or driver enforcement. > I suppose this issue has nothing to do with this library. Yes, that's a separate bug that's been around for a while. I've asked Casper and company about it in the past, but haven't heard an answer. > Second, dlpi_open() has three different open modes and > device_policy only appears to cover "raw access". This > tends to suggest that only 1 of the 3 modes of opening > a device with dlpi_open() would be covered here. The open modes have no impact on the access to the device. If they do in the future, it can be documented. > If dlpi_open() isn't the right place to mention that this > (or some other) privilege is requried, where would be? > Do we put it in the device man page or somewhere else? Use getdevpolicy(1M). -- meem _______________________________________________ networking-discuss mailing list [email protected]
