Ready to share source code – seeking signing assistance

[Nalik27]

Hello everyone,

I’ve developed a filter driver for mouse and keyboard that fully replicates the functionality and API of this Interception project. It’s been thoroughly tested and is ready for distribution.

Unfortunately, I’m unable to sign the driver myself. I’m looking for someone with Windows kernel code-signing capabilities to help me publish it. I’m happy to share the complete source code privately with anyone who can assist.

If you can help (or know someone who can), please reach out to me on Telegram: @Nalik27

Thanks in advance!

[liaguedes]

I hope someone helps you with that, this driver would be very helpful for me to use extra keyboards for video editing macros

Will it also have the 10 driver limit? I hope not

[Nalik27]

I hope someone helps you with that, this driver would be very helpful for me to use extra keyboards for video editing macros

Will it also have the 10 driver limit? I hope not

and what problems do you have with this project? It still works :)

[liaguedes]

I hope someone helps you with that, this driver would be very helpful for me to use extra keyboards for video editing macros
Will it also have the 10 driver limit? I hope not

and what problems do you have with this project? It still works :)

The fact that the dev disappeared and the 10 device driver limit scares me a lot

[Nalik27]

The fact that the dev disappeared and the 10 device driver limit scares me a lot

Got it. No, my driver doesn't have a device limit.

[jasonm23]

@Nalik27 regardless of signing, please open the source and reference your project here.

[svenkreis]

Did you change it fundamentally? The conflicts with Easy Anti Cheat are really annoying. I am using Macropads that only can take Keyboard Keys as mapping to send this device to vJoy, which is afaik impossible otherwise without affecting other "real" keyboards. I had to redo my whole hardware setup just because of iRacing and EAC.

[IgelRM]

Perhaps get in touch with @nefarius of ViGEm fame

[nefarius]

I've been summoned? Sure, let's talk, sounds interesting 😎

[liaguedes]

@nefarius Please talk to him on his Telegram! I'm very interested in this project since Interception will never be updated again

[nefarius]

@nefarius Please talk to him on his Telegram! I'm very interested in this project since Interception will never be updated again

We've connected 👍

[jamespatriot]

Very much looking forward to it, is there any progress now?

[Nalik27]

Yes, the driver filter has been written. It's not perfect, but it works. Unfortunately, I don't have the ability to constantly sign and test it, so development is complicated by this. I'm trying to register with Microsoft as a developer, but this bureaucratic process has become significantly more complicated lately. Also, I'm currently working on another project, which I might return to next year.

[petoncle]

@Nalik27 I'm not entirely clear on your goals or the current state of your project. Can I ask a few questions to better understand?

1. You mentioned that code signing is slowing down development. Have you considered using the test signing methods documented here?
2. You do not want to open source this project and it will remain closed source. Is that correct?
3. Under what license do you plan to distribute it? Are you intending to commercialize it?
4. You mentioned "working on another project", which you might "return to next year". Do you mean you currently don't have enough time to make progress on this driver project?
5. Is this GitHub issue thread the only place where public discussion about your project takes place? Where else can people follow your progress?

[Nalik27]

@petoncle Actually, I found a person who was able to sign the driver (with a regular signature, without HLK tests) for a certain fee. However, the result wasn’t quite what I expected.

First, a few bugs were discovered — not critical, but still present. To release an update with fixes, I’d have to pay again for signing, and I’m not ready to do that at the moment.

Second, most games that use EAC (and possibly some others) refuse to start when the driver is loaded. This isn’t a major issue, but I’d like the driver to be 100% system-compatible to avoid negative feedback from users. To properly investigate and fix this, I need the ability to test signed builds more frequently, which isn’t possible right now. Windows Test Mode doesn’t allow full-scale testing.

To answer your questions point by point:

1. I’m currently testing the driver in Windows Test Mode (bcdedit /set testsigning on), but this kind of testing is limited and not suitable for a wider group of users.
2. I haven’t decided yet what to do with the source code. I don’t want to publish something unfinished or of poor quality.
3. I don’t plan to make any commercial profit from this project. If I eventually open the source, it will be freely available for anyone to use, modify, and distribute.
4. I meant that I have a full-time job and a tight schedule, so I had to temporarily pause work on this driver. I expect to have more time next year to continue development.
5. Yes, this GitHub issue is the only place where public discussion about the project takes place.

[Nalik27]

And of course, special thanks to @nefarius for offering to help with the signing process if I need such assistance in the future!
P.S. @nefarius — I haven’t forgotten 🙂 I’m just very busy at the moment and not actively working on the project right now. I’ll definitely reach out to you once I resume development.