Quote from: patrike on January 28, 2019, 10:02:03 AM

Quote from: danielocdh on January 28, 2019, 12:32:15 AM

Quote from: patrike on January 27, 2019, 07:41:14 AM

Quote from: danielocdh on January 25, 2019, 10:14:07 PM

Quote from: patrike on January 24, 2019, 12:46:30 PM

Quote from: danielocdh on January 24, 2019, 06:05:24 AM

Quote from: patrike on January 23, 2019, 10:45:05 AM

Quote from: danielocdh on January 22, 2019, 11:15:59 PM

Block all incoming connections takes precedence over any other rule.

I manually changed the allow rules created by awesome miner for the mining software to block rules. Have been mining since I originally asked about this without any issue or popup (picture of my rules linked). The problem is that when new software is added/updated new rules will be created by awesome miner as allowed rules.
https://imgur.com/a/w7YBXdZ

If you make this an option you could just leave the default as it is now(allowed rules), just in case "blocked" rules might break anything for someone.

Thanks for the update.

I've made a quick implementation to support this case. I've introduced a new setting that you can set directly in the Awesome Miner configuration file as I don't want to expose this in the user interface.

1) Once the next version of Awesome Miner is available, install it, run it once and then exit the application.
2) Open the configuration file (%appdata%\AwesomeMiner\ConfigData.xml) and search for "ConfigureWindowsDefenderAllowedApps".
3) Change the property from true to false and save the file.

Thanks, I tried but it showed a popup the first time a mining software ran.
While testing further I found out 2 possible reasons why:
1 When creating a block rule the rule is created with Profile Private(current profile), while when creating an allow rule the rule is created with Profile All.
2 When creating a block rule the rule is added to the registry a couple of seconds after the miner software is launched, while when creating an allow rule the rule is added to the registry a few milliseconds before the miner software is launched.
I didn't test extensively but I'm guessing #1 has something to do with defaults, for #2 my guess is some firewall api limitation or maybe it is not the cause of the issue.
Hopefully you can take another look at it, otherwise I'll just create a script that runs now and then and modifies the rules as needed.
Even that my lan is relatively secure and have trustworthy people connecting to it, I don't want to leave my mining software open.

Thanks again.

The default behavior of Awesome Miner is to add this Allowed Apps rule. In that case things should just work and you shouldn't see any dialogs from Windows Defender. Is that correct according to your observations as well? I don't have any plans to change how these rules are set at the moment, as what Awesome Miner do works very well in a very large number of mining environments out there.

If you use the new property set to false, Awesome Miner will not do anything with the firewall configuration. I assume it's in only in this case you are getting the warnings from Defender? With the automatic configuration disabled in Awesome Miner, you are basically on your own here and you can manually configure (or not configure) the rules as you want.

I'm feeling that I'm failing to communicate what I want to say a lot, sorry about that and thank you for your patience. Maybe you make me nervous Wink

I meant that when configuring ConfigureWindowsDefenderAllowedApps as true the rules (allow rules) are being created with Profile=All, but when configuring ConfigureWindowsDefenderAllowedApps as false the rules(block rules) are being created with Profile=Private, I believe the difference in profile causes the popups to come up when ConfigureWindowsDefenderAllowedApps is set to false.

Thanks for the update. Your observations when running with ConfigureWindowsDefenderAllowedApps set to false are probably what to expect, as it's totally up to Windows to decide when to block, when to show the dialog and what rule to add in that case. Awesome Miner will do nothing, which is the purpose of setting the property to false.

Although I understand your observations here, I don't fully understand what you want Awesome Miner to do here. It can already do:
1) Add allowed apps automatically. This is the default, has been around for years and works fine for the purpose of mining.
2) The new mode when ConfigureWindowsDefenderAllowedApps set to false will result in Awesome Miner doing nothing. You are on your own to do what you want here. Any dialogs, blocking and so on you see is related to configuration of Windows and not Awesome Miner.

There are no feature in Awesome Miner to configure the allowed apps in any new way - either it's configured in a way that work (#1) or it's not touching anything (#2). Sorry if I missed your point here.

ConfigureWindowsDefenderExclusions defines whether firewall rules are created by awesome miner or not.
ConfigureWindowsDefenderAllowedApps(the one you added recently) defines whether the rules are created by awesome miner as allow rules(true) or block rules(false).
When ConfigureWindowsDefenderAllowedApps is set to true(default) the created rules are being created by awesome miner with Profile=All, when it is set to false the rules are being created by awesome miner with Profile=Private. I'd like the rules to be created with Profile=All regardless of ConfigureWindowsDefenderAllowedApps being true or false. I believe having Profile=All on the block rules(when ConfigureWindowsDefenderAllowedApps is set to false) might prevent popups to come up.

ConfigureWindowsDefenderExclusions is only for addings paths as exclusions to the anti-virus scan and that feature is always on by default. Otherwise Windows Defender will start removing all mining software it considers a thread.

"When ConfigureWindowsDefenderAllowedApps is set to true(default) the created rules are being created by awesome miner with Profile=All"
Correct assumption. In this case Awesome Miner makes a configuration that is proven to work well with mining

"when it is set to false the rules are being created by awesome miner with Profile=Private."
Not correct assumption. Awesome Miner do nothing to the Allowed Apps here. It will not touch the rules at all when this property is set to False. The behavior you experience is what Windows is doing when Awesome Miner no longer takes responsibility for configuring Defender for you. Any rules added at this point is what Windows is doing. This was the point I was trying to make above that when you tell Awesome Miner to not setup the Allowed Apps for you, you will be on your own and you will most likely run into issues with Defender unless you manually find a way to setup everything.

I'm have to admit that I'm not really an expert on all these Defender settings and the exact behaviors of when Windows is adding these rules automatically. If I knew more of the details, I would of course want to help out more with suggestions how to make these configurations. This is the reason why my answers above is based on everything from an Awesome Miner and mining point of view.

You are right, having ConfigureWindowsDefenderExclusions=true and ConfigureWindowsDefenderAllowedApps=false made windows auto create the block rules with Profile=Private. I misunderstood what ConfigureWindowsDefenderAllowedApps=false would do.

Manually changing the allow rules created by awesome miner to block rules worked fine for me (as shown on the picture), so I will just let awesome miner create the default rules and run an extra script every minute or so to change them from allow to block rules.

Thanks.