[CONJ-156] SecurityManager being used incorrectly Created: 2015-05-22 Updated: 2015-06-23 Resolved: 2015-06-23 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Other |
| Affects Version/s: | 1.1.8 |
| Fix Version/s: | 1.1.9 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Andy Shulman | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
SecurityManager checks were added in the fixed for the two linked bugs. However, you create a new SecurityManager rather than getting the configured SecurityManager via System.getSecurityManager(). In most JVM installations, people are running without SecurityManagers and so will not have policy set up and applications that call abort or setNetworkTimeout will throw SecurityExceptions. |