Icinga / Icinga/icinga-powershell-framework
Idea: IfW-WindowsFirewallRestricted
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 87
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When IfW-WindowsFirewall is set to 0 during installation (“Open Windows Firewall for incoming Icinga connections”), provide an option to restrict the Windows Firewall rule for the local port so that inbound connections are only allowed from the configured upstream servers: IfW-CAServer, IfW-ParentAddress, and IfW-ParentNodes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the installation handling for IfW-WindowsFirewall and the related IfW-CAServer, IfW-ParentAddress, and IfW-ParentNodes options. Done means an opt-in restriction can create the Windows Firewall rule so inbound local-port connections are limited to the configured upstream servers, while the existing unrestricted behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100