New 2.06p3 version

[Frederic]

Hi All,

A new 2.06p3 version is available.

This new version includes updated versions of standard rulesets in order to be compatible with KB951748 (http://support.microsoft.com/kb/951748) Microsoft update affecting Look 'n' Stop under Windows XP and 2003 Server.
These new rulesets are especially for a fresh installation of Look 'n' Stop.
If Look 'n' Stop is already installed, to solve the issue caused by KB951748 you have to apply this item of the FAQ (http://www.looknstop.com/En/faq_problems.htm#KB951748) or this thread (http://www.wilderssecurity.com/showthread.php?t=214468) of the forum (in other words: the 2.06p3 doesn't fix the KB951748 if Look 'n' Stop is already installed, because your current rulesets are not overwritten when Look 'n' Stop is updated).

Some other fixes are included (see below) and if you are not (or no longer) concerned by KB951748 you can anyway update to this 2.06p3.

Here are the links for download (with VC2005 libraries):

32 bits versions:
- English release (http://www.looknstop.com/En/LooknStop_Setup_206p3_VC2005.exe)
- French release (http://www.looknstop.com/Fr/Installation_LooknStop_206p3_VC2005.exe)
- Release with the translation plugin (http://www.looknstop.com/En/LooknStop_Setup_206p3MEn_VC2005.exe) (for other languages)

64 bits version:
- English release (http://www.looknstop.com/En/LooknStop_Setup_206p3_x64_VC2005.exe)
- French release (http://www.looknstop.com/Fr/Installation_LooknStop_206p3_x64_VC2005.exe)
- Release with the translation plugin (http://www.looknstop.com/En/LooknStop_Setup_206p3MEn_x64_VC2005.exe)

If you are already using the 2.06p2 or if VC2005 libariries are already installed, you can use the following links:

32 Bits version:
- English release (http://www.looknstop.com/En/LooknStop_Setup_206p3.exe)
- French release (http://www.looknstop.com/Fr/Installation_LooknStop_206p3.exe)
- Release with the translation plugin (http://www.looknstop.com/En/LooknStop_Setup_206p3MEn.exe)

64 bis version:
- English release (http://www.looknstop.com/En/LooknStop_Setup_206p3_x64.exe)
- French release (http://www.looknstop.com/Fr/Installation_LooknStop_206p3_x64.exe)
- Release with the translation plugin (http://www.looknstop.com/En/LooknStop_Setup_206p3MEn_x64.exe)

If no major issue is detected, this version will replace the 2.06 on our site, and therefore will officialize the content of the 2.06p2.

Here is the history section of the help file:

Changes:
Standard and enhanced rulesets contain an additional DNS rule in order to be compatible with Windows update KB951748.
Standard and enhanced ruleset now contain rules for LLMNR, UPnP and WS-Discovery protocols (which are used under Vista and add a lot of alerts at Windows startup). These protocols are still blocked by default but without adding alerts in the log.

Fixes:
Application Filtering: better compatibility with some Antivirus software (some crashes/BSOD could happen with previous releases).
DLL Filtering: one very rare crash/BSOD has been fixed
Localization (through the translation plugin) was not working properly in the 2.06p2
Rule creation from log: ports values have been fixed for IPV6
Console window: some fixes and improvements regarding driver logs
Language Plugin under Vista: language files (.lng) are now saved into "\Users\[user]\AppData\Local\looknstop".


Any feedback welcome here.

Thanks,

Frederic

[cdr]

Frederic,
For those of us who have installed this new version 2.06p3, but are using Phant0m's Ruleset, do we still have to also import the "UDP-DNS for KB951748.rie?" I'm not clear about this.
Thanks for your help!

[Frederic]

Hi cdr,

If you have already updated Phant0m's Ruleset when using the 2.06p2, then there is nothing else to do if you install the 2.06p3 (the updated ruleset will be still ok).

If you are using the 2.06p2, with the old ruleset and you have the issue with KB951748, then yes, you still need to update the ruleset whatever the version you are using (2.06p3 or 2.06p3).

Hope this clarifies.

Frederic

[octogen]

Thanks, Frederic. Excellent firewall. :thumb:

{QUOTE-> Application Filtering: better compatibility with some Antivirus software (some crashes/BSOD could happen with previous releases). <-QUOTE}

Does this encompass the issue with Kaspersky Antivirus? Thanks in advance.

[Frederic]

{QUOTE->
Does this encompass the issue with Kaspersky Antivirus? Thanks in advance. <-QUOTE}
Yes, exacltly.

Frederic

[shaunwang]

Thanks, Frederic. for updating the firewalll...

{QUOTE->
Application Filtering: better compatibility with some Antivirus software (some crashes/BSOD could happen with previous releases). <-QUOTE}

Does this resolved Avira AntiVir Personal - FREE Antivirus on Vista sp1 ?

[Frederic]

{QUOTE-> Does this resolved Avira AntiVir Personal - FREE Antivirus on Vista sp1 ? <-QUOTE}
No, I have never investigued crash issue with Avira.
What is the problem exactly, and do you have minidump files ?

Frederic

[nuser]

great! Frederic.:D
btw, any update for the rawrule plugin?

[Mongol]

{QUOTE-> great! Frederic.:D
btw, any update for the rawrule plugin? <-QUOTE}

Also the ARP plugin...? :o ;D

[Frederic]

Hi nuser and Mongol,

No there is no update for raw rule edition plugin and ARP plugin, so far.
The existing versions are supposed to work fine with the 2.06p3.

Regards,

Frederic

[Triple Helix]

Working very well here on XP SP3 and Vista SP1.

Thanks,

TH ;)

[Thomas M]

Dear Fredric,

The new 2.06p3 nicely works on my Win-XP SP2 (32bit)!

Thank you,
Thomas :)

[sukarof]

2.06p3 working fine on Vista SP1 64bit.

[ankupan]

Hi,

I installed it on Win XP SP3 and it is working great.

When we need firewall, than LnS is the right one. (only firewall)

[Enig123]

Look'n'Stop causes winS2003 to crash when I set too many ip address restriction to an application @ Application Filtering window.

It pop up a message window to tell me what happened, when I press the OK button, the OS crashed.

[Frederic]

Could you copy/paste the string entry causing the crash ? (I guess it is just an application crash, and not an OS crash)
You can change some digits (in case some privacy is required), but let the size of the string not modified.

For which kind of application do you require many IP address to be allowed ?

Thanks,

Frederic

[Enig123]

{QUOTE-> Could you copy/paste the string entry causing the crash ? (I guess it is just an application crash, and not an OS crash)
You can change some digits (in case some privacy is required), but let the size of the string not modified.

For which kind of application do you require many IP address to be allowed ?

Thanks,

Frederic <-QUOTE}

It's a reproduceable BSOD, and definitely is an OS crashes that caused by LnS.

Why do you think it's allowed ips instead of banned ips? ;)

Better LnS have the function of alias of a group of ips for this kind of usage. Would you consider implementing it?

[Frederic]

{QUOTE-> It's a reproduceable BSOD, and definitely is an OS crashes that caused by LnS.
<-QUOTE}
Ok, in that case, could you send a MiniDump file (from c:\windows\minidump) to lnssupport@soft4ever.com. In case you have many files there, check the date to be sure to send a minidump file corresponding to this issue.
Also if you could give the kind of entry causing the issue, it would help.
{QUOTE->
Why do you think it's allowed ips instead of banned ips? ;)
<-QUOTE}
Because normally for a specific application you would like to give the only IP it is allowed to connect.
If you want to block some IPs, usually it is not specific to one application but to all applications, and it that case, it is better to do that through the Internet Filtering.
Also "restriction" could mean you have limited the IP @ to an allowed list.
{QUOTE->
Better LnS have the function of alias of a group of ips for this kind of usage. Would you consider implementing it? <-QUOTE}
Yes, maybe, but if implemented it will be at the Internet Filtering level.
Are you talking about a large list of IP @ (>100) ?

Thanks,

Frederic

[Frederic]

{QUOTE-> Ok, in that case, could you send a MiniDump file (from c:\windows\minidump) to lnssupport@soft4ever.com. In case you have many files there, check the date to be sure to send a minidump file corresponding to this issue.
Also if you could give the kind of entry causing the issue, it would help.
<-QUOTE}
I've finally reproduced the issue, so my requests are no longer required.
A fix will be included in the next driver update. In the meantime, the maximum number of IP/ports (when set individually, without ranges/mask) is limited to 18.

Frederic

[Enig123]

Thanks a lot. 18 will be more than enough.