Tim Brooks 3344cd21ac Wrap operations requiring SocketPermission with doPrivileged blocks ... Motivation: Currently Netty does not wrap socket connect, bind, or accept operations in doPrivileged blocks. Nor does it wrap cases where a dns lookup might happen. This prevents an application utilizing the SecurityManager from isolating SocketPermissions to Netty. Modifications: I have introduced a class (SocketUtils) that wraps operations requiring SocketPermissions in doPrivileged blocks. Result: A user of Netty can grant SocketPermissions explicitly to the Netty jar, without granting it to the rest of their application.		2017-01-19 21:12:52 +01:00
..
src	Wrap operations requiring SocketPermission with doPrivileged blocks	2017-01-19 21:12:52 +01:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2017-01-12 11:36:51 +01:00