Re: Capabilities for device drivers

tote — Sun, 29 Jan 2006 01:06:11 +0100

Practically, in the MMP file of an EXE, you have to list those capabilities that you'd like your EXE to be able to do. E.g. if you want your EXE to perform HTTP comms (over TCP/IP), then you have to add NetworkServices capability. If you don't add it to the list, then your EXE will not be able to perform network comms.

However, the meaning of asssigned capabilities is a little bit different for executables other than EXE (like a device driver, a special DLL). For these binaries, capabilities indicates the level of trust, what you can do with the library IF the hosting process (i.e. the EXE) holds that capability. That is, you can assign NetworkServices capability to your device driver (strange, though), it won't necessarily work unless the hosting process has NetworkServices capability, too. The more capabilities a library has, the more you can trust it.

Finally, answering your question: the target should be to assign as many capabilities to your device driver as you can (yes, including NetworkServices, too). Nevertheless, you might have some hard moments when you try to sign your device driver and people are asking questions about the capabilities of your module.

tOtE

Re: Capabilities for device drivers

Mr. Buttington F. Phucque Lewis — Fri, 13 Jan 2006 20:07:17 +0100

See if you can get some answers at the security newsgroup

http://www.symbian.com/developer/public/index.html

Capabilities for device drivers

nirp — Thu, 12 Jan 2006 22:23:06 +0100

NewLC - Capabilities for device drivers - Comments

Re: Capabilities for device drivers

Re: Capabilities for device drivers

Capabilities for device drivers