You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2020/02/06 15:19:00 UTC
[jira] [Assigned] (CASSANDRA-15494) Support additional Jar url
scheme
[ https://issues.apache.org/jira/browse/CASSANDRA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams reassigned CASSANDRA-15494:
--------------------------------------------
Assignee: Brandon Williams
> Support additional Jar url scheme
> ---------------------------------
>
> Key: CASSANDRA-15494
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15494
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Gus Heck
> Assignee: Brandon Williams
> Priority: Normal
> Attachments: CASSANDRA-15494.patch
>
>
> This code in ThreadAwareSecurityManager causes issues for embedded cassandra launched from a one-jar or uno-jar.
> {code:java}
> switch (codesource.getLocation().getProtocol())
> {
> case "file":
> // All JARs and class files reside on the file system - we can safely
> // assume that these classes are "good".
> return true;
> }
> {code}
> Attaching patch to support protocol of 'jar' as well. AFAICT this won't introduce any added risk for UDF's discussed in CASSANDRA-9402 since a jar (or one/uno jar) must also be on the filesystem.
> New code would be (in 2 places):
> {code:java}
> switch (codesource.getLocation().getProtocol())
> {
> case "jar":
> case "file":
> // All JARs and class files reside on the file system - we can safely
> // assume that these classes are "good".
> return true;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org