Posts Tagged ‘Winsock API’

Winsock LSP Calls

Tuesday, June 15th, 2010

How does the call from the Winsock LSP travel through the interfaces?  How is communication handled within the application?  This is a very brief synopsis.

LSP is the quick way to say Layered Service Provider.  A Winsock LSP is used for a number of reasons.  This technology is not simple, though it may seem that way to the casual computer user.

When a call is sent on a Winsock API, it travels through a succession of gates or interfaces before it reaches the kernels.  The gates, or layers, as they are also called, are where code is inserted in order to monitor, reroute or change the original call.  This is what happens when you utilize adult content controls or block spam or emails.


Windows Sockets

Monday, June 7th, 2010

Winsock is simply the shortened form of Windows Sockets and it is the top dog in every network (Windows).  Layered Service Provider is shortened down to LSP and the Winsock LSP is merely a code that allows your application to maneuver itself into the communication stack for the Winsock API.  Winsock LSP can read, intercept, and modify network traffic.

Winsock APIs are simply the application program interfaces.  These facilitate communication for the application network calls and the Windows OS kernel.  Therefore, any message sent through this network gets turned into an application call.  This application call is then fed to the WinSock API. At this point Winsock routes this message through the kernel and to the recipient port.

Since the Winsock LSP is a simply a code, it can be placed anywhere between the applications and the API.  This results in the possibility of any network call/message from the application can be scanned and intercepted.  There are various actions that can be taken based on the data gained and the benefits to the user are immense.