search

AndyFul / Hard_Configurator

GUI to Manage Software Restriction Policies and harden Windows Home OS
Other
501 stars 41 forks source link

current source code #19

Open YZgitter opened 10 months ago

YZgitter commented 10 months ago

Is there a current, up to date H_C source code available? The one on here seems to be from 2 years ago.

AndyFul commented 10 months ago

Only the 2-year-old code is available for now. But, most of the current functions are already there. It is a good start for anyone who wants to use H_C on Windows 10 with personal modifications (for personal use).

YZgitter commented 10 months ago

I see it doesn't work on Windows 11. That's a bummer.

AndyFul commented 10 months ago

I am not sure what you want to do. If you want to use a personal application based on the source code, you can make H_C work on Windows 11 in 5 minutes, by trivial modification: https://seclists.org/fulldisclosure/2023/Mar/1 Anyway, that is not all - you must send the EXE file after compilation to Microsoft (or another vendor) for whitelisting. If not, then it will be flagged as malicious (false positive), blocked by SAC, blocked by SmartScreen, etc.

If you do not want to change the code, you have the already compiled application which is digitally signed, accepted by SAC, accepted by SmartScreen, and accepted by Microsoft Defender (including ASR rules). You can download it from GitHub or any popular portal, like Softpedia, Major Geeks, Chip, etc.

YZgitter commented 10 months ago

What I want to do is obvious, I think:

  1. inspect the code and/or
  2. make some changes (for personal use)

I wouldn't be asking for the source otherwise.

Anyway, thanks for the tip about that registry setting. With that, the SRP rules work fine with my modified EXE.

But HC 5.x has some issues on W11, even with your binaries. And there are a couple of features I'm missing from 6.x. Having the current source would make everything easier.

AndyFul commented 10 months ago

The binaries of H_C ver 5.1.1.1 compiled by me, work well on Windows 11 (checked today) with the correction noted in my previous post.

There were some changes from ver. 5.1.1.1. , but most can be easily (re)coded because a similar code already exists in the ver. 5.1.1.1. The only problem can be with a 'Block Appinstaller' option because SRP cannot block it in a standard way. Anyway, the ver. 5.1.1.1 is still very good, and it can provide excellent protection.

I keep the source code on GitHub as an example of advanced coding in AutoIt. I do not need to actualize the source code - this is required when other people participate in the project. If you would like to participate, then let me know.

AndyFul commented 10 months ago

There is a kind of conflict between open-source coding and creating digitally signed applications. The first is based on the informal cooperation of several people who sometimes do not know each other. The second requires the formal entity (person, business group, etc.) who formally buy the certificate. So, the H_C up to ver. 5.1.1.1 is fully open-source. It can be further developed on GitHub, but will not be digitally signed by me.