1/*2 * Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved.3 * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.4 *5 * This code is free software; you can redistribute it and/or modify it6 * under the terms of the GNU General Public License version 2 only, as7 * published by the Free Software Foundation. Oracle designates this8 * particular file as subject to the "Classpath" exception as provided9 * by Oracle in the LICENSE file that accompanied this code.10 *11 * This code is distributed in the hope that it will be useful, but WITHOUT12 * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or13 * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License14 * version 2 for more details (a copy is included in the LICENSE file that15 * accompanied this code).16 *17 * You should have received a copy of the GNU General Public License version18 * 2 along with this work; if not, write to the Free Software Foundation,19 * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.20 *21 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA22 * or visit www.oracle.com if you need additional information or have any23 * questions.24 */2526package java.net;
2728import java.security.*;
29import java.util.Enumeration;
30import java.util.Hashtable;
31import java.util.StringTokenizer;
3233/**34 * This class is for various network permissions.35 * A NetPermission contains a name (also referred to as a "target name") but36 * no actions list; you either have the named permission37 * or you don't.38 * <P>39 * The target name is the name of the network permission (see below). The naming40 * convention follows the hierarchical property naming convention.41 * Also, an asterisk42 * may appear at the end of the name, following a ".", or by itself, to43 * signify a wildcard match. For example: "foo.*" and "*" signify a wildcard44 * match, while "*foo" and "a*b" do not.45 * <P>46 * The following table lists all the possible NetPermission target names,47 * and for each provides a description of what the permission allows48 * and a discussion of the risks of granting code the permission.49 *50 * <table border=1 cellpadding=5 summary="Permission target name, what the permission allows, and associated risks">51 * <tr>52 * <th>Permission Target Name</th>53 * <th>What the Permission Allows</th>54 * <th>Risks of Allowing this Permission</th>55 * </tr>56 * <tr>57 * <td>allowHttpTrace</td>58 * <td>The ability to use the HTTP TRACE method in HttpURLConnection.</td>59 * <td>Malicious code using HTTP TRACE could get access to security sensitive60 * information in the HTTP headers (such as cookies) that it might not61 * otherwise have access to.</td>62 * </tr>63 *64 * <tr>65 * <td>getCookieHandler</td>66 * <td>The ability to get the cookie handler that processes highly67 * security sensitive cookie information for an Http session.</td>68 * <td>Malicious code can get a cookie handler to obtain access to69 * highly security sensitive cookie information. Some web servers70 * use cookies to save user private information such as access71 * control information, or to track user browsing habit.</td>72 * </tr>73 *74 * <tr>75 * <td>getNetworkInformation</td>76 * <td>The ability to retrieve all information about local network interfaces.</td>77 * <td>Malicious code can read information about network hardware such as78 * MAC addresses, which could be used to construct local IPv6 addresses.</td>79 * </tr>80 *81 * <tr>82 * <td>getProxySelector</td>83 * <td>The ability to get the proxy selector used to make decisions84 * on which proxies to use when making network connections.</td>85 * <td>Malicious code can get a ProxySelector to discover proxy86 * hosts and ports on internal networks, which could then become87 * targets for attack.</td>88 * </tr>89 *90 * <tr>91 * <td>getResponseCache</td>92 * <td>The ability to get the response cache that provides93 * access to a local response cache.</td>94 * <td>Malicious code getting access to the local response cache95 * could access security sensitive information.</td>96 * </tr>97 *98 * <tr>99 * <td>requestPasswordAuthentication</td>100 * <td>The ability101 * to ask the authenticator registered with the system for102 * a password</td>103 * <td>Malicious code may steal this password.</td>104 * </tr>105 *106 * <tr>107 * <td>setCookieHandler</td>108 * <td>The ability to set the cookie handler that processes highly109 * security sensitive cookie information for an Http session.</td>110 * <td>Malicious code can set a cookie handler to obtain access to111 * highly security sensitive cookie information. Some web servers112 * use cookies to save user private information such as access113 * control information, or to track user browsing habit.</td>114 * </tr>115 *116 * <tr>117 * <td>setDefaultAuthenticator</td>118 * <td>The ability to set the119 * way authentication information is retrieved when120 * a proxy or HTTP server asks for authentication</td>121 * <td>Malicious122 * code can set an authenticator that monitors and steals user123 * authentication input as it retrieves the input from the user.</td>124 * </tr>125 *126 * <tr>127 * <td>setProxySelector</td>128 * <td>The ability to set the proxy selector used to make decisions129 * on which proxies to use when making network connections.</td>130 * <td>Malicious code can set a ProxySelector that directs network131 * traffic to an arbitrary network host.</td>132 * </tr>133 *134 * <tr>135 * <td>setResponseCache</td>136 * <td>The ability to set the response cache that provides access to137 * a local response cache.</td>138 * <td>Malicious code getting access to the local response cache139 * could access security sensitive information, or create false140 * entries in the response cache.</td>141 * </tr>142 *143 * <tr>144 * <td>specifyStreamHandler</td>145 * <td>The ability146 * to specify a stream handler when constructing a URL</td>147 * <td>Malicious code may create a URL with resources that it would148normally not have access to (like file:/foo/fum/), specifying a149stream handler that gets the actual bytes from someplace it does150have access to. Thus it might be able to trick the system into151creating a ProtectionDomain/CodeSource for a class even though152that class really didn't come from that location.</td>153 * </tr>154 * </table>155 *156 * @see java.security.BasicPermission157 * @see java.security.Permission158 * @see java.security.Permissions159 * @see java.security.PermissionCollection160 * @see java.lang.SecurityManager161 *162 *163 * @author Marianne Mueller164 * @author Roland Schemers165 */166167publicfinalclassNetPermissionextendsBasicPermission {
168privatestaticfinallong serialVersionUID = -8343910153355041693L;
169170/**171 * Creates a new NetPermission with the specified name.172 * The name is the symbolic name of the NetPermission, such as173 * "setDefaultAuthenticator", etc. An asterisk174 * may appear at the end of the name, following a ".", or by itself, to175 * signify a wildcard match.176 *177 * @param name the name of the NetPermission.178 *179 * @throws NullPointerException if {@code name} is {@code null}.180 * @throws IllegalArgumentException if {@code name} is empty.181 */182183publicNetPermission(String name)
184 {
185super(name);
186 }
187188/**189 * Creates a new NetPermission object with the specified name.190 * The name is the symbolic name of the NetPermission, and the191 * actions String is currently unused and should be null.192 *193 * @param name the name of the NetPermission.194 * @param actions should be null.195 *196 * @throws NullPointerException if {@code name} is {@code null}.197 * @throws IllegalArgumentException if {@code name} is empty.198 */199200publicNetPermission(String name, String actions)
201 {
202super(name, actions);
203 }
204 }