Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Access to RAW sockets requires admin rights on Windows 2000 and later, and that is described on MSDN:</p> <p><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms740548.aspx" rel="nofollow">TCP/IP Raw Sockets</a></p> <blockquote> <p>Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later. </p> <p>...</p> <p><strong>Note</strong> To use a socket of type SOCK_RAW requires administrative privileges. Users running Winsock applications that use raw sockets must be a member of the Administrators group on the local computer, otherwise raw socket calls will fail with an error code of WSAEACCES. On Windows Vista and later, access for raw sockets is enforced at socket creation. In earlier versions of Windows, access for raw sockets is enforced during other socket operations. </p> </blockquote> <p>There is no way to get around that restriction. On the other hand, if your intention is just to initialize Winsock in general, then you do not need to create a RAW socket to do that. Create a TCP (<code>SocketType.Stream</code> and <code>ProtocolType.TCP</code>) or UDP (<code>SocketType.DGram</code> and <code>ProtocolType.UDP</code>) socket instead, which are not restricted, and most likely what OOo is actually going to use internally anyway. Or, you could use PInvoke to call Winsock's <code>WSAStartup()</code> function directly.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload