Discussion in 'LnS English Forum' started by Jacko2, Dec 4, 2010.
Time for any updates in Look'n'Stop 2.07 ?
So, what is your favourite wish to be implemented in the next update of LnS?
This is a very strong rules based firewall so little if any updating is needed unlike application based firewalls like ZA or Private Firewall etc...
Yup and its rock solid. Really there is nothing more I could possibly want in this firewall. More features = more bloat. I havent seen any bugs so I am happy . I do kind of wonder about the development of look'n'stop though, hope it doesnt turn into abandon-ware the absence of Fredric makes me worried. From what I hear though support is still actively answering questions.
Still no need for an update??
i need :
1.option to disable windows firewall while installation..( or automatically disables)
2. more secure ruleset ( like phan0m's )
3. when password protected ,ability to authorise or block applications..
Some sort of gaming mode.
Change the internet filtering such that when an internet filtering rule is applied to a specific application, it becomes active when that application launches but ONLY for that application and not all allowed applications.
Add a more user-friendly GUI for RAW rule creation.
Keep it lean and mean.
prevent uninstall when password protected LnS.
I can uninstall LnS even if i locked using password
also maybe fix the installation problem of "unable to load the lnsfw driver (Error 0)." that plagues many of us if the slightest of things goes wrong with lns.
lnsfw driver errors relates to Internet Filtering layer
lnsfw1 driver errors relates to Application Filtering layer
"unable to load the lnsfw driver (Error 0)." represents the driver for Internet Filtering was not installed properly, back in the day, before Frederic started to digitally sign the Look ‘n’ Stop drivers, sometimes meant that that the unsigned drivers are automatically forbidden on the persons system. However, wouldn’t be your case though.
I remember helping users over this type of error before, but I don’t re-call what steps was involved. But I do know I’m willing to take it from grounds up, requires both sides to be patient, and follow instructions.
If someone runs into this, and wants to troubleshoot, just say my name!
How about adding "Application name" tab feature in TCP connection states window?
I am the latest victim of the error .Certainly need a fix
If your interested Gobbler, please try what is said over on https://www.wilderssecurity.com/showpost.php?p=1813820&postcount=15
So, can the Windows Firewall be the culprit?Is it necessary to manually turn off the Windows Firewall before the installation?
Look ‘n’ Stop works well with Windows built-in firewall, the only thing is, if packet-filtering is enabled on the Windows firewall, you may have to maintain both packet filters.
the need to fix this?
I know that's not critical , but...
1) In regards to server rules, .. only one application can listen on a specific port at a time.
2) I don’t see how one could make the Raw rule creation / editing any easier, this is a feature meant to be used by experts with insight on packet workings.
3) Agreed, Frederic shares our same views on keeping it lean and mean, and not bloating it up .. like being seen elsewhere.
I think uninstalling Look ‘n’ Stop would be a noticeable end result that the owner of the PC would see and deal with. The goal probably is to prevent tampering that would likely go unseen by the owner. Enforcing password at uninstall stage could be problematic for both parties, I think any administrator should be-able to uninstall anyways regardless of it password protected.
I’ve done the research, I don’t see this being anything even remotely to a outbreak, or fatal as you had implied. First of all, "unable to load the ? driver (Error 0)." shows when the driver was not loaded properly by Windows (for several different reasons) at startup, almost every case that I had read was either shown to be, or pointing to something being messed up prior to the installation of Look 'n’ Stop. The other cases cames abouts sometime after having installed Look ‘n’ Stop and it had been working for a little while, but the use of Total Uninstall product, and installing or uninstalling of different security systems that toys with the Network environments that messes things up for Look 'n’ Stop, and this error message then experienced.
I asked about that LNS support about week ago, on the next business day I've received answer from Frederic.
This is a part of his reply:
So, in other words... don't worry, layered protection should easily protect your computer from that.
thx for the answer
good news lies on the reply
Separate names with a comma.