6 Commits (6c5a4a14ef415e4635f7e0dc7fcb345f0c617a98)

Author	SHA1	Message	Date
Dreamcat4	6c5a4a14ef	fix: win10 - Add exception handling for 'Profiles:' textual output key name mismatch. ... In win10 (and pribably win8x also): The output of 'show rule' key includes the line "Profiles:<TAB>Public,Private". Yet your script expects the key name printed out to be "Profile:<TAB>value". This commit added the necessary exception handling to avoid flagging 'different=true' under the false circumstance. The key name to SET a firewall rule is still "profile=" and not "profiles=". There is coming up another commit to fix the value handling for win10/win8. Which is another (different) error with the profile: key.	9 years ago
Dreamcat4	2654789af7	fix: fw rule names must always be quoted, to permit spaces ' ' and brackets '()' ... Without this fix, the 'netsh' command gets name=Firewall Rule Name instead of name="Firewall Rule Name". Thus causing all sorts of havoc. Basic shell quoting rules seems to apply to Windows Powershell too. This is very much needed as many of windows 10's default firewall rules contain spaces and brackets () characters.	9 years ago
TimothyVandenbrande	2d6303b368	upon request, added the license	9 years ago
Timothy Vandenbrande	d87da2ba2d	renamed profile var	10 years ago
Timothy Vandenbrande	97d8273558	windows default to current instead of all	10 years ago
Timothy Vandenbrande	2a0df8ec04	renamed the module	10 years ago