Windows 10 with LooknStop

Discussion in 'LnS English Forum' started by alisultan, Aug 31, 2015.

  1. alisultan

    alisultan Registered Member

    Joined:
    Aug 31, 2015
    Posts:
    1
    I'm a loyal fan of LooKStop but unfortunately after upgrading to windows 10 i cant use this beautiful fire wall any more, the question is how to use it with windows 10 or is their any alternative for it.
     
  2. Boblvf

    Boblvf Registered Member

    Joined:
    Aug 10, 2014
    Posts:
    103
  3. Nebulus

    Nebulus Registered Member

    Joined:
    Jan 20, 2007
    Posts:
    1,582
    Location:
    European Union
    The difference between Look'n'Stop and a firewall controller for Windows Firewall is huge...
     
  4. Boblvf

    Boblvf Registered Member

    Joined:
    Aug 10, 2014
    Posts:
    103
    No difference, Look n' stop, W10FC, Outpost, Comodo, just a GUI in a 64 bits system.

    « WFP is designed to replace previous packet filtering technologies such as Transport Driver Interface (TDI) filters, Network Driver Interface Specification (NDIS) filters, and Winsock Layered Service Providers (LSP). Starting in Windows Server 2008 and Windows Vista, the firewall hook and the filter hook drivers are not available; applications that were using these drivers should use WFP instead


    With the WFP API, developers can implement firewalls, intrusion detection systems, antivirus programs, network monitoring tools, and parental controls »
     
  5. Phant0m

    Phant0m Registered Member

    Joined:
    Jun 7, 2003
    Posts:
    3,684
    Location:
    Canada
    Both TDI & NDIS Intermediate (or NDIS IM) features are deprecated. The both filtering technologies is currently used by Look 'n' Stop. Yes, the WFP (Windows Filtering Platform) is suppose to replace the both TDI and NDIS deprecated filtering technologies.

    ... WFP was a poor replacement; now with Windows 8, and 10 not so much. WFP is still a poor replacement on Windows 7 and older.


    Before Microsoft Windows 8, WFP didn't support Link-layer (Layer 2) inspection. Which means no coverage over non-IP based protocols (like for quick instance; ARP.)


    I've skimmed through 'Windows 10 Firewall Control' official site, so I could be missing some details. However this firewall seems like a very poor example in comparison to other firewalls.

    Does this firewall even support yet other non-IP protocols?



    I have to agree with Nebulus, there's big difference between Look 'n' Stop and WFP firewalls like 'Windows 10 Firewall Control' running under Windows 7 and older. WFP-based firewalls running under Windows 7 and older is no substitute for Look 'n' Stop awesomeness. :D
     
  6. Boblvf

    Boblvf Registered Member

    Joined:
    Aug 10, 2014
    Posts:
    103
    « WFP-based firewalls running under Windows 7 and older is no substitute for Look 'n' Stop awesomeness »

    Especially for you, your money, and your « phantom « rules ...
     
  7. Infected

    Infected Registered Member

    Joined:
    Feb 9, 2015
    Posts:
    665
    I strongly disagree, Comodo it much more than a GUI. In which is has hips and a sandbox....
     
  8. Boblvf

    Boblvf Registered Member

    Joined:
    Aug 10, 2014
    Posts:
    103
    HIPS are for marketing victims, no hooks in kernel in a 64 bits system with patchguard.


    Read and understand, if possible ...

    « Windows Filtering Platform

    Purpose
    Windows Filtering Platform (WFP) is a set of API and system services that provide a platform for creating network filtering applications. The WFP API allows developers to write code that interacts with the packet processing that takes place at several layers in the networking stack of the operating system. Network data can be filtered and also modified before it reaches its destination.

    By providing a simpler development platform, WFP is designed to replace previous packet filtering technologies such as Transport Driver Interface (TDI) filters, Network Driver Interface Specification (NDIS) filters, and Winsock Layered Service Providers (LSP). Starting in Windows Server 2008 and Windows Vista, the firewall hook and the filter hook drivers are not available; applications that were using these drivers should use WFP instead.

    With the WFP API, developers can implement firewalls, intrusion detection systems, antivirus programs, network monitoring tools, and parental controls. WFP integrates with and provides support for firewall features such as authenticated communication and dynamic firewall configuration based on applications' use of sockets API (application-based policy). WFP also provides infrastructure for IPsec policy management, change notifications, network diagnostics, and stateful filtering.

    Windows Filtering Platform is a development platform and not a firewall itself. The firewall application that is built into Windows Vista, Windows Server 2008, and later operating systems – Windows Firewall with Advanced Security (WFAS) – is implemented using WFP. Therefore, applications developed with the WFP API or the WFAS API use the common filtering arbitration logic that is built into WFP.

    The WFP API consists of a user-mode API and a kernel-mode API. This section provides an overview of the entire WFP and describes in detail only the user-mode portion of the WFP API. For a detailed description of the kernel-mode WFP API, see the Windows Driver Kit online help. »