Serious Discussion Fort Firewall

[tnodir]

Fort Firewall 3.16.8

• UI: Options: TrafficGraph: Add "Tick label size" option (#323).
• UI: GraphWindow: Show right y axis (#323).
• UI: Connections: ProgramEdit: Fix Rule's empty name (#464).

 

[ranecogofi]

We're in process of company and employee verification by MS. They're verifying company's domain, email etc and requesting docs.

Has it been more than 5 days? From this Microsoft article, it seems like it should normally take 3-5 days.

 

[tnodir]

it seems like it should normally take 3-5 days.

It already several months.

 

[ranecogofi]

It already several months.

Uh, that's been a while. Have you tried contacting Microsoft's support? Are they responding to you?

 

[tnodir]

Have you tried contacting Microsoft's support? Are they responding to you?

Yes, only a month ago. Support us helpful, but docs are rejected by bot on the site.

 

[ranecogofi]

Support us helpful, but docs are rejected by bot on the site.

Was it because the docs need revision? If it's rejected by mistake maybe try contacting support again?

 

[tnodir]

Was it because the docs need revision?

Yes, the docs need to be corrected and renewed. So it takes time.

 

[ranecogofi]

Yes, the docs need to be corrected and renewed. So it takes time.

I hope it can be resolved soon. Thanks for answering my questions.

 

[tnodir]

I hope it can be resolved soon.

The thread about driver signing by MS.

 

[tnodir]

Fort Firewall 3.16.9

• UI: Rules: Add "ip_version(4, 6)" filter function (#470).
• UI: GraphWindow: Draw ticks outside of grid (#323).

 

[tnodir]

Fort Firewall 3.17.0

• UI: Connections: Fix disabling of auto-scroll (#474).
• UI: Connections: Show port numbers only (#487).
• Driver: Fix Global Rules, After App Rules, for 1-st conn of new app (#484).
• Driver: Order Global Rules by Name (#486).

 

[tnodir]

Fort Firewall 3.17.1

• Driver: Fix Program's Zones handling (v3.17.0 regression) (#488).

 

[tnodir]

Fort Firewall 3.17.2

• UI: Add "-c [command] report" command-line argument (#478).
• UI: Add "-c group on|off|report [group-index]" command-line argument (#478).
• UI: Connections: Copy selected cells by Ctrl+C (#489).
• UI: Tray: Hide context menu for ignored right click (#490).

 

[tnodir]

Fort Firewall 3.17.3

• UI: Options: Add "Snooze Alerts" flag (#494).
• UI: Add "-o [file-path]" command-line argument (#478).
• UI: Services: Open Program's dialog on double-click.

 

[oldschool]

@tnodir thanks for the regular updates. Haven't tried FFW yet but I'll give it a go.

Do you have any idea if it interferes with Windows 11 widgets? I had problems with TinyWall. It blocked them updating real time widget info.

 

[tnodir]

Do you have any idea if it interferes with Windows 11 widgets?

No idea. To troubleshoot the blocking issues see FAQ

 

[ranecogofi]

Hi @tnodir, is Fort system service guarded against random application trying to interact with it? Like changing firewall settings for example.
If so, how does it verify the application that interact with the service is a legit application (Fort UI) and not some random app?
I see that you could set a password to protect against config change, is this password validated by the service or just the UI?

Thanks!

 

[tnodir]

@ranecogofi Yes, you have to set password to validate processes interacting with the service. Password is checked by service.

 

[ranecogofi]

@ranecogofi Yes, you have to set password to validate processes interacting with the service. Password is checked by service.

Can you link me to part of the code where the service validates the password? I tried searching for it but only found reference on UI src. Thanks!

 

[tnodir]

Can you link me to part of the code where the service validates the password?

1. Fort can work without Service, so it uses special *Rpc classes to communicate with service, when the service is installed.

2. ConfManager::checkPassword() is actual place where password is checked.
UI process uses ConfManagerRpc::checkPassword() to call the service function.

3. RPC calls are managed by RpcManager class.

4. The master and *Rpc classes are registered in the FortManager.cpp: setupServices() function.

5. Service's clients (i.e. UI processes) are checked for password validation: see ControlWorker::setIsClientValidated() usages.