Video tutorial

[kn0t3k]

Hey m8 @0xflux , thank you for the excellent video on how to setup Sanctum, finally made it work!

I also figured out why it might not have worked out for me before:

1. there are 2 DLLs called sanctum.dll! one in Sanctum\driver\target\debug, the other in Sanctum\target\release. You should make it clear which one to copy in the installation instructions (as you showed in the video, though I'm not sure you were fully aware of the 2 different DLLs)
2. elam_installer has to be run on every startup - was not said in the instructions
3. path to service executable is hardcoded to C:\Users\flux\AppData\Roaming\Sanctum\sanctum_ppl_runner.exe. It is difficult to change the service settings once it is created on the system, most likely due to it being under Local System account. There is actually a TODO in your code:

   Sanctum/elam_installer/src/main.rs

   Line 150 in c126e17

   // todo not hardcode

All in all it seems to work, driver is loaded, the App works (at least it is producing some outputs) and I can start messing aroung with alternate syscalls! Cheers

[0xflux]

Thanks for leaving the feedback, I'll take a look at fixing this tonight!

I had a thought over the weekend if my project uses alt syscalls going forward, the PPL service and DLL technically aren't required. I may look at deprecating the service as a runtime requirement, same for the DLL. 😀

Anyway, I appreciate your perseverance with this it's helped me get the project in a better state for it being used!

[kn0t3k]

no problem

the startup procedure is a little bit jerky, i.e. I run elam_installer.exe which tells me to run the service... can elam_installer.exe run the service directly? I mean it is executed under admin rights as well...

The same idea comes to um_engine.exe, it is executed in the same set of steps, so elam_installer could teoretically run it as well. Or maybe some other runner, which would run elam_installer, run the service and finally run the um_engine. Could also run the App afterall...
This way it would all be a part of one executable, which could drive the whole starup procedure and it would be less error-prone

[kn0t3k]

Also, as I'm playing around with the driver, is there a way to make cargo make (executed from driver) also run the sign.bat script? Again would make the developer's life easier

[0xflux]

Re the service - yep you're right it would make it easier, however as I will deprecate the PPL for now, I wont look at this.

It's possible to interfere with the signing process; but tbh I haven’t looked that deeply into the make process for the driver - it was a little more complicated due to needing the ELAM cert hash etc, but I cant see no reason why it cant be done after you make those edits after a first signing. I wont be looking at that with any priority right now