Hi, No, it is also for whitelisting of apps running with admin rights and for showing processes with admin rights. File sharing is different from the functionality you have described. If you check closely, file sharing still works (if enabled in TinyWall), while "homenetgroup" is not yet supported. Wait for february to be able to use it. I recommend adding a mapped network drive to acces your files on the network, that will work perfectly with TinyWall.
I have released the next maintenance release TinyWall v1, bearing the version number 1.0.3. This brings only fixes and small updates to the current stable branch, but it does correct a significant number of crashes and usability issues. No new features were introduced to avoid new problems. Changelog: - Fix: Controller crash when bubble-editing new exception in GUI multiple times in a row - Fix: Controller crash after exception modification in Manage window, when Modify is clicked again - Fix: Possible controller crash when populating list in Connections form - Fix: Firewall rules may overwrite each other - Fix: Some DNS responses are blocked, leading to possibly slower DNS resolution - Fix: Wrong filtering of ICMPv6 traffic - Fix: GUI is not updated when timed rules are removed - Fix: Generalize Steam profile for all Steam games - Tell user that admin rights are missing instead of disabling Uninstall button - New and updated application profiles - Updated FAQ (please read it) As I have mentioned earlier, I'm already working on the new major version v2, which you might get a taste of in february. v2 will be the first version that I will widely recommend for everybody to use, as it will resolve the shortcomings of v1 and include some features that did not make it into v1. It is also strongly driven by the feedback that I've received during the past month. v2 will introduce new security and UI features, some of which have been requested by the community. It should also correct most limitations of the current version (for example, I am aiming to resolve all "Known Issues" listed in the FAQ). A lot of work has already gone into v2 and many things are implemented. But there is still a lot of work left, so I give no guarantees on the ETA. Still one thing is for sure: it's coming.
It is released and is good enough for everyday use, but you should check the FAQ to avoid problems. v2 should make it much easier for the user without having to read the FAQ.
Updated, BTW, I noticed that the first time you open the manage windows, the list will take some time to parse, if you have many rules, not a big deal though, as it only happens on the first open. How about some clues regarding the new features . EDIT: I just remembered that the auto detect does not detect the ingame browser of Steam. It's gameoverlayui.exe.
I read everything on your site about TinyWall. And as you mentioned V2 should make it easier without having to read the FAQ, I agree. After reading I think average/novices may still face probs & reading FAQ is a must. I will wait for V2 & see how it works. Thanxx Naren
I avoided that on purpose . But the fact alone that it avoids interoperability problems with some native Windows services will be a good enough reason for most people to upgrade. Currently, I am working on a "blocked applications" list. I'm done with supporting it in the engine, and the next thing is to add UI support for it. You'll see the full list when v2 becomes beta.
Also waiting!, TinyWall has been the most user friendly firewall I've ever used. Others have very complex settings. I wondered what are you gonna do to make it more simpler.lol
The GUI won't change significantly, except to accomodate for the new functionality. But for example, TinyWall will know about the concept of applications, so it will know and help you with software that need multiple executables unblocked. That will be a great help to users and should get rid of about 90% of all bug reports
Softoxi has made one (http://www.softoxi.com/tinywall.html), but it is not really a tutorial. It is video of a user clicking through some of the options without explanation or context. Still, it will show you what to expect from the GUI. I will probably make a video tutorial for v2, with explanations.
ultim, You mentioned that version 2 will be easy & recommended. I decided to use version 1, but just for GUI for windows firewall & password protection. How can I use it like default windows firewall on win 7 64? Password protection enabled but tinywall tray icon can be exited? What is enable default windows rules?
The tray application is only a GUI, you can exit it but TinyWall's core still keeps running in the form a service. Password protection locks down all changes in the core, so you can set a password, exit the GUI, and you will still need a pasword for modifications in the future (even if someone would write an alternate GUI). I'm not sure what you mean by "like default windows firewall". As long as TinyWall is installed, changes to the windows firewall (including its rules) can only be made using TinyWall on Win7. If you try to modify the rules over the native Windows GUI, it won't work. So I'm not sure how usefull it is to exit TinyWall's GUI. The protection features will still be active but you won't be able to modify/add new rules until you start up the tray application again. It puzzles me even more that you want the GUI of TinyWall but you want to close its tray application.
ultim, I meant was TinyWall can be exited even if password protection is enabled so I thought it was a bug. But thanks for the info that the service is not stopped. I just wanted to know if it was by design or bug. I want to use it like Windows 7 Firewall means, Win FW blocks incoming & allows outgoing by default, right? Rarely it gives popup which is not bad. TinyWall is the controller for Win FW so what should I choose in TinyWall so that it works Win FW way i.e the bold sentence above. I am confused between allow outgoing & the option in General Enable default windows rules. Allow outgoing means all outgoing connections are allowed & incoming are blocked, right? What does enable default windows rules does if selected? Lock/Unlock is not instant & takes app 20-30 secs here. How to change network Home/Work/Public with TinyWall? Thanxx Naren
This is by design. Even if you close the tray, TinyWall still keeps running as a service so there is no security hole here. For that, switch TinyWall's firewall mode into "Allow outgoing". But note that each reboot of the machine sets it back to Normal mode, so you need to set the mode after each boot. Yes. It makes TinyWall not disable the default rules of a factory-reset windows firewall. Not really usefull for probably anyone but me. Wow, I just checked and even though the operations are instant on my computer, I noticed other problems. It only seems to work if you restart the controller after each lock/unlock. This is clearly unintended and they are supposed to work without restarting the GUI. Thanks for reporting. You don't change it from TinyWall. TinyWall will apply different rulesets based on the Home/Work/Public network type of Windows Firewall, but the currently selected type is still managed by Windows Firewall. You can change the network type in the standard Windows Network and Sharing Center.
Been quiet here, any news about anything? I notice the website shows 1.0, It would be to advantage to you to keep the (web page) version updated (1.03).
I know is against the purpose of TinyWall, but could you make a version with popups? please please xD Or at least a place where we can see which programs are being blocked (are trying) to access to Internet so we can easily allow them via right click A multi-select option in the process window...
