Beta-testing TinyWall

Discussion in 'other firewalls' started by ultim, Oct 12, 2011.

  1. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Thx, I'll look into it.

    TW does not install drivers. The problem was in the service, it only checked that it communicates with its own Controller process (so that random apps cannot send commands to it), but not the data types that got deserialized from it. This allowed a shortcoming in .Net's code in the BinaryFormatter class to be exposed (if the Controller was compromised such that it sent unexpected data), where hidden callbacks leading to malicious code sent over the pipe could be executed by the .Net Framework before it even got handed to TinyWall's code. For more details, you can read up on the issue in this research paper. Though TinyWall does not use JSON like in the paper, the problem was the same due to using the BinaryFormatter class.
     
    Last edited: Dec 29, 2019
  2. Bertazzone

    Bertazzone Registered Member

    Joined:
    Apr 13, 2018
    Posts:
    259
    Location:
    Wonderland
    I also had this experience.
     
  3. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Also on Win8/8.1?
     
  4. Bertazzone

    Bertazzone Registered Member

    Joined:
    Apr 13, 2018
    Posts:
    259
    Location:
    Wonderland
    Sorry, Windows 10.
     
  5. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Sorry, neither of you mentioned which version is affected. 2.1 (stable) or 2.99 (beta)?
     
  6. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,660
    Location:
    Mexico
    From now on, well since you released 2.x betas, whenever I post about TW I referring to those betas and they're running on Windows 8.1 x64 two different machines two different hardware configurations, unless I say otherwise. :)

    Edit: In this case, TW 2.99.10 is installed.
     
    Last edited: Dec 30, 2019
  7. Bertazzone

    Bertazzone Registered Member

    Joined:
    Apr 13, 2018
    Posts:
    259
    Location:
    Wonderland
    2.99 Beta. Also had issue where I needed to re-whitelist Brave and Edge Chromium a number of times. I can't give you more details as I've uninstalled the Beta.
     
  8. mood

    mood Updates Team

    Joined:
    Oct 27, 2012
    Posts:
    23,674
    TinyWall v2.1.14 (January 2, 2020)
    Website
    What's New (detailed changelog)
    Download
     
  9. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    When this happens the next time, can you let me know how many TinyWall.exe processes are running on the system (two or just one)? What I want to find out is if the controller does not start/crashes, or does it stay stuck somehow without showing the icon. Thx.
     
  10. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,660
    Location:
    Mexico
    This is going to take some time cause it rarely happens. For example, it hasn't happened since I posted here last time.
     
  11. g17

    g17 Registered Member

    Joined:
    Sep 30, 2017
    Posts:
    13
    Location:
    MI
    I just updated to Win 10 version 1909, OS build 18363.535 and am seeing some strange new rules in my windows firewall list, but no corresponding new entries in the tiny wall logs (v2.1.11) or application exception list. They do reference the svchost service so that may be the reason.

    Wondering if anyone has seen this also? Sorry if off topic, I searched the forum for this but found nothing.

    The rule names are as follows. They revert back to their settings of allowed if I change them.

    Inbound:

    @FirewallAPI.dll, - 80201
    @FirewallAPI.dll, - 80206

    Outbound:

    @FirewallAPI.dll, - 80204

    Thanks, again sorry if off topic but could not find reliable info even in a general Google search.
     
  12. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    I have seen it on lot's of fresh Windows installs. I don't know exactly what it is for, only that it has to do with multimedia (camera?) streaming in some form. It has nothing to do with TinyWall.
     
  13. g17

    g17 Registered Member

    Joined:
    Sep 30, 2017
    Posts:
    13
    Location:
    MI
    I'll do more research, thanks for the info.
     
  14. tyee

    tyee Registered Member

    Joined:
    Nov 15, 2008
    Posts:
    55
    Can someone help with how to map a local folder to a drive letter. I don't mind this workaround at all if I could just do it. Would I use the "subst" command or the "net use" command? I want my local folder accessible to my amazon fire stick. I did make a few folders shareable a few years ago by uninstalling tinywall, then reinstalling, but I don't want to do that again.
     
  15. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    https://www.laptopmag.com/articles/map-network-drive-windows-10
     
  16. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,660
    Location:
    Mexico
    Happened today morning. Event viewer log attache (delete the txt extension)
     

    Attached Files:

  17. tyee

    tyee Registered Member

    Joined:
    Nov 15, 2008
    Posts:
    55
    So, I have to enter the network name of my firestick in the selection window.

    Update- I can't turn on Network Discovery to find the firestick. My router calls the firestick this -- amazon-eXXXXXXXX. X's are numbers. I know the ip address of the firestick. I tried adding \\192.168.x.xx but Windows says cannot find it. If I ping that address I get 4 replies.
     
    Last edited: Jan 9, 2020
  18. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Thanks. It is clear from the logs that something crashed, but I don't see anything there saying anything about which of the two or which part of the code. This weekend I should be ready with a new release, and it also logs error from the GUI, not just from the service as before, so that should help us. Also, much of the initialization code has changed, so maybe - just maybe - the same problem doesn't even occur anymore.
     
  19. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Usually you also need to specify the share name, so it should be something like "\\192.168.x.xx\name-of-the-share". Unfortunately I don't know the firesticks so I cannot help you what the share name is on these devices.

    This weekend I should be ready with a new release of TinyWall, if you are interested to try it, it does not need this workaround anymore (due to not relying on Windows Firewall). Meaning you can use the default Network Browser of Windows without having to mount your network share as a drive.
     
  20. tyee

    tyee Registered Member

    Joined:
    Nov 15, 2008
    Posts:
    55
    Sounds good, I'll be waiting!
     
  21. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    12,397
    Location:
    The Netherlands
    I keep forgetting that TW doesn't use a standalone driver, and that's because I now see it as a true third party firewall. I thought they all needed a driver to function. And thanks for the info, seems like it wasn't an easy exploitable bug.

    I'm getting confused. Is this still the old version which acts like a front-end for the Win Firewall? What happened to the new style TinyWall which doesn't need the Win Firewall to function?
     
  22. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Any version number that start with 2.1 is still the old version (which is just a frontend). The betas of the new version (which can work standalone) are numbered 2.99, and the first official release will be 3.0.
     
  23. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    12,397
    Location:
    The Netherlands
    OK thanks. I honestly thought that you stopped developing the old skool TW. I'm waiting for v3.
     
  24. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    If you look at the detailed changelog for v2.1, it has only seen criticial bugfixes recently. Any larger improvements are going into v3.0 exclusively, and after 3.0 is released, I will indeed stop maintaining 2.1.
     
  25. ultim

    ultim Developer

    Joined:
    Oct 12, 2011
    Posts:
    438
    Location:
    Hungary
    Hello Everyone, I just uploaded 2.99.11, the latest beta. And probably one of the last ones too.

    The big new feature here is the ability to auto-whitelist paths that are child-processes of manually whitelisted executables. This is not automatic, and has to be enabled manually case-by-case in the exception details dialog. Still, I expect this to be a great comfort feature, for example when using online installers and many other cases. The catch here is that this feature might not always work without a driver. It worked well in my tests, but if your testing says it is a hit-and-miss in the real world, I might remove it for 3.0.

    Other than this, there are a ton of changes and improvements all over the whole spectrum, ranging from setup experience, to runtime performance, firewall rules, and the GUI. Upon installing 2.99.11, your firewall settings (such as rules) will remain intact, but your GUI settings (such as window sizes or language) will be reset. This is expected and normal. Needless to say, the uninstall bug from the previous version is fixed too, I'm sorry it happened, but I assure you it is alright now. If you are running 2.99.10 and you have problems uninstalling it (or upgrading), make sure to follow gmw's instructions here. Once the service has been stopped as outlined there, the uninstall will work. Do NOT try to remove the files or registry entries manually without the uninstaller.

    [Download link]

    Release notes for TinyWall 2.99.11:
    - New: Option to apply rules to child processes
    - Fix: Editing a just-added rule by clicking on pop-up fails to apply
    - Fix: CVE-2019-19470
    - Fix: Dangling icon left in tray after uninstallation
    - Fix: Default DNS rules are incorrectly applied
    - Fix: Crash on .Net 3.5 with loopback adapters
    - Fix: Uninstall fails on some systems
    - Many optimizations to startup and runtime performance
    - Show version on installer's Welcome screen
    - Deleted executables are grouped together in Settings window
    - Eliminate flicker from Processes and Services windows during load and scrolling
    - Log crash details for controller GUI
    - Faster install and uninstall
    - Prevent svchost from being learned when using the Autolearn feature
    - Fix possibly breaking connections when Windows Firewall is enabled during firewall reload
    - Add IPSec AH support to VPN rules
    - Make Settings window resizeable
    - Don't accept unencrypted HTTP during update checks
    - Remove TinyWall's firewall rule from configuration

    As announced earlier, I am putting all new features on hold until 3.0 is released, but things are looking very good. I am officially in bugfix-only mode, and the release date of 3.0 depends only on whether you can find any bugs that warrant another test build. Think of this build as an RC if you will, because it's mostly what it is :) Thank you all for helping out and testing! Here's hoping 3.0 will be released in this month.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.