getaddrinfo API failed with return value WSANO_DATA

[Rajesh V R]

Hi All,

We are using Layered Service Provider (LSP) into our project to control the inbound and outbound Internet traffic through Chrome Browser. In this LSP, we are calling "getaddrinfo" API to retrieve the Hostname and IP Address of each Web Requests. It was working fine before latest release of Chrome, but with latest Chrome release (69.0.3497.81) "getaddrinfo" API failed with return value 11004 (WSANO_DATA).

WSANO_DATA:  Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.

For "getaddrinfo" API, please refer this link: https://docs.microsoft.com/en-us/windows/desktop/api/ws2tcpip/nf-ws2tcpip-getaddrinfo

Kindly help us to solve this issue as early as possible, because this issue is affecting very badly with our business.

Thanks,

Rajesh VR

[Matthew Menke]

I'm not sure if this is the issue you're running into, but see https://blog.chromium.org/2017/11/reducing-chrome-crashes-caused-by-third.html.  Also note that independently of that, in the not-too-distant future, Chrome's network code will be moved into a separate sandboxed process, where LSP injection won't really work, because of the security sandbox.

[Rajesh V R]

Hi Matthew,

Kindly suggest an alternative mechanism to overcome this issue. Because this issue is affecting very badly with our business.

Thanks,

Rajesh

[Rajesh V R]

And from this link ( https://blog.chromium.org/2017/11/reducing-chrome-crashes-caused-by-third.html ), there are some exceptional cases:

      While most software that injects code into Chrome will be affected by these changes, there are some exceptions. Microsoft-signed code, accessibility software, and IME software will not be affected.

So can you please tell us what is it meant by "Microsoft-signed code".

Thanks.

On Friday, September 7, 2018 at 6:52:14 AM UTC+5:30, Matthew Menke wrote:

[Matthew Menke]

That's Microsoft signing its own code, so isn't an option for you, unfortunately.

I'm not familiar enough with what you're doing or platform APIs to offer much help, but there are other ways to control traffic without being in Chrome's memory space.  A proxy is the most obvious option.