WNDP Connect Site gets an upgrade!

Last year we setup a small site on connect.microsoft.com in order to let our blog readers, developers and users file bugs, make suggestions and get some conntent like whitepapers and samples early. The downside to the site was that you couldn’t easily deep link and it required a Windows Live (aka Passport) login. Well the folks…


Winsock and the new SDK Headers

As you may have noticed in the recent Vista CTP SDK, the Winsock headers have undergone some changes. First, instead of a couple monolithic files (winsock2.h and mswsock.h), they have been split into a number of smaller files for ease of maintenance as well as for use by other components that don’t necessarily load Winsock…


Introduction to Winsock Kernel (WSK)

Overview of WSK   In Windows Vista a new transport-independent kernel mode Network Programming Interface (NPI) called Winsock Kernel (WSK) has been added.  Using WSK, kernel-mode software modules can perform network communication using socket-like programming semantics similar to those supported in user-mode Winsock2.  While the WSK NPI supports most of the same socket programming concepts…

7

Winsock and Vista User Account Control

As you might have heard, Vista introduces User Account Control (UAC) which is a security feature that enables users to perform some tasks as non-Administrators. This has an effect on LSP writers as the Winsock functions to install and remove LSP entries can only be called as an Administrator. On Vista there is a difference…

2

Categorizing LSPs and Applications

In Windows Vista there is a new method for categorizing both Winsock Layered Service Providers (LSP) and applications themselves such that only certain LSPs will be loaded. There are a couple reasons for adding this functionality. One of the main reasons is certain system critical processes such as WinLogon and LSASS create sockets but do…

17

Dual Stack Sockets on Windows Vista

One of the changes in Windows Vista is that the IPv4 and IPv6 stacks are integrated — on older OSes they were completely separate stacks. One benefit of this tighter coupling is the ability to create dual-mode sockets. That is, an application can create a single TCP (or UDP) socket and receive both IPv4 and IPv6…

2

Winsock Connect and TCP SYN Attack Protection

TCP SYN attack protection has been available on Windows platforms since Windows 2000, but by default is turned off. This has changed for the Windows 2003 SP1 release as SP1 enables SYN attack protection by default (which is a good thing). However, once enabled it affects how TCP connections are accepted. Specifically it accepts how Winsock…


Winsock – Microsoft Connect Program

In an earlier blog (http://blogs.msdn.com/wndp/archive/2005/09/27/474679.aspx), Shivakumar introduced the Connect program.  Shiva mentioned WinInet, WinHTTP and HTTP.sys are using Microsoft Connect.  This blog is to announce Winsock  has now joined Connect.  This means you can submit bugs, submit feature requests and (in the future) download additional Winsock-related content such as whitepapers.  Connect Program Homepage: https://connect.microsoft.com. See…

1

Changes in Socket Bind

MSDN finally has the “Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE” doc online. I previously posted it on this blog but the formatting came out a bit funky. Here’s the link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/using_so_reuseaddr_and_so_exclusiveaddruse.asp We’ve received some feedback on the article saying it doesn’t explicitly spell out all the changes in socket bind behavior. The tables in the doc do…


Socket Security: Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE

Developing secure applications is a priority for most developers today; however, socket security is often overlooked but is especially critical. Socket security deals with other processes binding to the same port that an existing application already has a socket bound to. In the past, any process could steal the port that another socket was using…

4