Discussion in 'LnS English Forum' started by jodu, Oct 11, 2006.
Is LnS still being developed??
Is there any plans for a new version ??
I would like to know that too !
Yes, me too.
I'd be glad to see the current version come out of Beta...
Hi jodu and all,
Yes, there will be a new version.
Supporting Vista (and possibly IPV6) will be the main features for this new version.
Unfortunately, experimental features of the 2.05p3 (+ potentially "Watch Thread injection" and "Watch DNS call") won't be kept, since they are not compatible with DEP and Vista.
thats good news Frederic. any rough ETA?
So the only feature of a new version would be that LNS would support vista? Would any of the current features,settings,etc be updated somehow?
Nevermind.Made the change to Comodo.Not bad at all.
I stick to Look 'n' Stop since I uninstalled Jetico/Comodo.
Look 'n' Stop should remain a pure firewall other than a complicated HIPS. Running light is its incomparable advantage.
I agree its lightness is one of the reasons i use it. I hope it remains a pure firewall thats light and stable.
I installed LnS probably 4 years ago. It has been an install and forget program, using the enhanced rule set.
I hope there are no major changes.
I hope for the following changes:
1) Higher number of app and internet filtering rules (128 doesn't cut it anymore)
2) More user friendly activation system, which enables those of us who re-install often, to use LnS without having to always ask for a new
3) Solving issue: DEP + Thread Injection = BSOD issue
4) UI fixes: use radio buttons with XOR selections, not check boxes (check boxes are for AND or basic OR selections, not XOR)
Which one's in particular ?
lns should definitely improve its SPI feature, as now the SPI quite trouble for p2p applications, while use the free WIPFW packet filter cause no trouble to system & it can change spi slot number, dynamic rule time, maybe lns future ver should have these too.
- Yea different limits will be increased, the key question is, when and which one to be first?
- The use of checkboxes in Look ‘n’ Stop is all appropriate from what I see, correct me if I’m wrong but I just see stand-alone checkboxes which is to activate or deactivate a single features
Momentarily I do believe the Look ‘n’ Stop SPI + p2p problems are direct end result of the LooknStop TCP SPI simultaneous connections limit (max-allowed, 256). And this is supposed to be fixed with v2.06 release … and sadly to say, it is unknown to date when a release date will be for that…
I do wish though, that the Look ‘n’ Stop SPI implementation will begin taking form of shared SPI characteristics, LooknStop SPI should really be informational when logging. … "Out of connection", "Invalid Flags", "Invalid Acknowledge Number", "Invalid Sequence Number", "Incoming connection limit reached", "Outgoing connection limit reached", "Half-open connection limit reached"
So far, all we know when we all ever see the Look ‘n’ Stop SPI loggings; this could be only just direct result of "Half-open connection limit reached", and can we actually be sure the lns SPI implementation is even proper (No offence to Fred )….
Network interfaces selection screen.
At least on my system, I have two options and if I click one, the other one is automatically deselected.
So, it functions like a radio button (XOR), so it should look like a radio button, not a checkbox.
This is actually a listview control with the LVS_EX_CHECKBOXES attribute.
There is no LVS_EX_RADIOBUTTON attribute...
Internet-filtering rules edit bug
When activating or deactivating the logging flag for a rule that is set for application, the rule becomes active (though still shown with deactivated attribute) even though there no application even launched…
I was not able to reproduce that.
Are you really talking about the Application filtering page ?
If I understand well, if an application doesn't have the green checkbox on the left side, and you press the ! attribute, then, when you start the application there is no alert ? the application is allowed or blocked (and logged) ?
Thanks for responding.
No, I’m talking about Applications being set on a rules on 'Internet Filtering' screen
On the Internet filtering screen, the application feature available through the ‘Rule Editing’ dialog, to associates an application or applications with rule…
When activating or de-activating the logging flag on a rule that is set with application or applications, the rule becomes activate (even though the rule still shown with a deactivated attribute), and the associated application or applications NOT even running.
Also, when rule that’s associated with an application, and becomes active by the execution / connecting of that associated application, making changes to just the logging state causes the rule to stay activated after the application disconnects and even closes out…
Here is a couple anyways….
Hi, will this include Vista64 ?
Hope the new version will really come out.
Separate names with a comma.