Is LnS project death??

i excuse myself if i'm too much radical, but:
what is making the Soft4Ever in order to contrast the competition that in these last times seems to be truly pressing?
Agnitum, for exemple, is working on new Outpost4 that shortly will enter in beta testing phase (see http://www.outpostfirewall.com/forum/showthread.php?t=17160), the same one for jetico that is developing version 2 (http://www.fluxgfx.com/ssc/showpost.php?p=1294&postcount=2)....
Moreover new player are showing themself on the market with their new intresting products (Comodo2...)

...and so on....

Well, and the Soft4Ever?

Regards....

 

Hi, alfa1

You should not put yourself down, your not Radical.

You are just A Lurker with not much to say.

Oh yes, I am being Sarcastic

When an update is ready from LnS it will be posted.

Many other venders say what they are Going to do but untill they post their update it is all blow.

Take Care,
TheQuest

 

Fly down when you speak of someone else.
Your reply is only a trivial remark.
So, stay on topic if you have something to say.

Again, "what is making the Soft4Ever in order to contrast the competition that in these last times seems to be truly pressing?".
Frederic, could you give us an idea about future plans of development?
Are you working on the observations moved from the customers?
(for exemple, UDP/ICMP Pseudo Stateful Packet Inspection seen that packet-filtering strength is critical (see also https://www.wilderssecurity.com/showpost.php?p=286363&postcount=41 and focus on Phant0m reply "a lot of developers who built some very strong packet-filtering systems don’t agree…" or https://www.wilderssecurity.com/showpost.php?p=288001&postcount=52), control over ECE/CWR flags, detection of various port scan tecnology (LnS with built in IDS...) http://www.mntolympus.org/phpbb2/viewtopic.php?t=2032 https://www.wilderssecurity.com/showpost.php?p=286513&postcount=47 https://www.wilderssecurity.com/showpost.php?p=287138&postcount=50, a better implementation of TCP SPI mechanism still anchored to 256 simultaneous connections open/half open....and so on....

To sum up, I LOVE LnS but i'm afraid of his development is too slow especially in the light of the pressures that arrive from the outside....

 

….

It’s impressive how few of the other players are persistently staying on their toes to impress their customers, lot of dedication (and time) there to their customers and to their work.

And there are some new players coming into the woodworks and with impressive work too. Take Comodo Personal Firewall a fresh firewall and with TCP Stateful Packet Inspection. UDP isn’t stateful (a connectionless protocol much like ICMP) it can be designed stateful-like and some ICMP is stateful (despite what some may say), Comodo Personal Firewall already developed both technologies.

Regarding LooknStop TCP SPI Implementation; I class myself as an average user with average habits and I still forced to leave the current TCP stateful inspection feature disabled, so it is obvious this needs some work ‘still’.

Also, I personally see a major incompleteness with TCP SPI implementation ‘still’ after all this time, I believe SPI implementations should be informative on various occurrences, 1. "Out of connection", 2. "Invalid Flags",3. "Invalid Sequence Number", 4. "Invalid Acknowledge Number", 5. "Incoming connection limit reached", 6. "Outgoing connection limit reached", 7. "Half-open connection limit reached".

alfa1, Look ‘n’ Stop with use of a Plug-In (PluginEditRawRule.dll) and a rule can detect and block packets containing ECE/CWR TCP flags, but I believe it should be feature directly implemented into Look ‘n’ Stop.

 

Txs for your reply, Phant0m.
If i know something about LnS, it is due to you!.
Txs for all!


Anyway it would be interesting to know the point of view of Frederic on my question: "an idea about your plans of development"....

In which direction do you move your research?


Txs in advance.