Hello once more Loxch, I'd

Technical Support
1

Hello once more Loxch,

I’d like to ask if there’s a problem with the latest version of Mudfish, particularly 4.5.3

You see, I tried to install this on another computer running Windows 7 x64 and I got a notification saying Windows requires a digitally signed driver as shown on the screenshot:

https://image.mudfish.net/i/yvBRzb

I have the logs screenshoted as well:

https://image.mudfish.net/i/wM9MLf

It’s quite weird, could you please check up on it?

2

I’d also like to add

https://www.hybrid-analysis.com/sample/25c6b253d400b6733e60f9add957395ea39d29d54d44093282b12bf9a61a2c77/5cefd5110288387f645e5894

For further investigation of a possibility of infiltrated Mudfish installer binaries

3

Also, does Full VPN Mode make use of this windows service?

IKEEXT - IKE and AuthIP IPsec Keying Modules

4

We think that Unsigned Driver issue is caused to a new feature included in Mudfish 4.5.1+.

That feature requires Microsoft Windows 8+.

So that caused showing Unsigned Driver Issue in Windows 7-.

forums.openvpn.net/viewtopic.php?t=26280

mudfish.net/forums/6/topics/53682

5

Thank you very much for the awesome response! Though I’d seriously like to know if mudfish is dependent on the IKEEXT service of Windows, or is it not?

6

At least if you’re talking about IKE and AuthIP IPsec, I can say that Mudfish doesn’t use it because in my coding ability isn’t higher what most of users are expecting. :slight_smile:

7

ooo I see, thank you for your very modest response :smiley:

8

Please let us know if you couldn’t solve the problem with bcdedit.exe /set nointegritychecks on at cmd or curious about a solution for Windows 10.

9

Thank you for this plausible fix and thankfully it apparently worked just fine as it is even without me doing any fixes or disabling driver signature enforcement