New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.security.AccessControlException: access denied ("java.io.FilePermission" "/etc/os-release" "read") #10017
Milestone
Comments
normanmaurer
added a commit
that referenced
this issue
Feb 11, 2020
…mission" "/etc/os-release" "read") Motivation: Modifications: - Wrap the code and execute with an AccessController - Ignore SecurityException (by just logging it) - Add some more debug logging Result: Fixes #10017
@asalamon74 PTAL #10018 |
normanmaurer
added a commit
that referenced
this issue
Feb 12, 2020
…mission" "/etc/os-release" "read") Motivation: Modifications: - Wrap the code and execute with an AccessController - Ignore SecurityException (by just logging it) - Add some more debug logging Result: Fixes #10017
This was referenced Mar 11, 2020
ihanyong
pushed a commit
to ihanyong/netty
that referenced
this issue
Jul 31, 2020
…mission" "/etc/os-release" "read") (netty#10018) Motivation: Modifications: - Wrap the code and execute with an AccessController - Ignore SecurityException (by just logging it) - Add some more debug logging Result: Fixes netty#10017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
Netty 4.1.39 added #9411 where netty checks for the
/etc/os-release
file. It's not a problem if this file is missing, but netty gives an error if we don't have right to read this file. I think it should be treated the same.Actual behavior
Steps to reproduce
Bump netty version in lucene-solr and run unit tests (e. g. org.apache.solr.core.HdfsDirectoryFactoryTest)
Netty version
4.1.39 - 4.1.45
JVM version (e.g.
java -version
)openjdk version "11.0.2" 2019-01-15
OS version (e.g.
uname -a
)MacOS 10.14 (Darwin Kernel Version 18.0.0)
The text was updated successfully, but these errors were encountered: