On Thursday, September 10, 2015, Matt Durgavich mattdurgavich@gmail.com wrote:
That’s unfortunate. Where is the caching taking place?
Inside ntdll, from inside ws2_32 follow the get_sock_fd call an you will reach ntdll, I'm replying from mobile phone so I can't give source details.
On Sep 9, 2015, at 8:04 PM, Bruno Jesus <00cpxxx@gmail.com javascript:_e(%7B%7D,'cvml','00cpxxx@gmail.com');> wrote:
On Wednesday, September 9, 2015, Matt Durgavich <mattdurgavich@gmail.com javascript:_e(%7B%7D,'cvml','mattdurgavich@gmail.com');> wrote:
Why are we looking at the dll side again?
Closing the sockets server side does not clear the ntdll cache, the current solution is incomplete then as functions like send and closesocket will fail for the wrong reasons because the socket is still "available".
Best regards, Bruno