-
|
Hi, i've built usbipd from sources and was looking on how it works. I've noticed that the binary required admin privileges for accessing the windows registry. Would it suffice if I made a custom interface + implementation that covers the RegistryKey: IRegistryKey + custom implementation that instead of writing / reading to and from the windows registry, would write to, for example, a json file? Note: first time working on Windows since a long while., company doesnt give me full privileges, would like to do some firmware development from a docker container in WSL2 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
That could work, but other stuff may also need admin privileges. Like using You could also simply use a different registry base key, i.e. in "CURRENT_USER" instead of "LOCAL_MACHINE". That's a much quicker hack... However, in any case you will need to run the installer as admin, to install the driver and services. And then your sysadmin may just as well use the feature that is intended for this: https://github.com/dorssel/usbipd-win/wiki/New-design:-policies (see use cases at the bottom). |
Beta Was this translation helpful? Give feedback.
That could work, but other stuff may also need admin privileges. Like using
--forcefor binding. This will require "driver installation" privileges (i.e. admin).You could also simply use a different registry base key, i.e. in "CURRENT_USER" instead of "LOCAL_MACHINE". That's a much quicker hack...
However, in any case you will need to run the installer as admin, to install the driver and services. And then your sysadmin may just as well use the feature that is intended for this: https://github.com/dorssel/usbipd-win/wiki/New-design:-policies (see use cases at the bottom).