Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDalibor Pospíšil
2022-04-11 19:16:51 UTC
Description of problem:
rule=12 dec=deny_audit perm=open auid=-1 pid=16015 exe=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-2.el8_5.x86_64/jre/bin/java : path=/var/lib/pki/pki-tomcat/work/Catalina/localhost/ROOT/org/apache/jsp/index_jsp.java ftype=text/x-java trust=0
Version-Release number of selected component (if applicable):
100%
How reproducible:
ipa-server-4.9.6-10.module+el8.5.0+13587+92118e57
Steps to Reproduce:
1. start fapolicyd with the default policy
2. install IPA using ipa-server-install
Actual results:
certificate server install failes
Expected results:
IPA is installed
Additional info:
worked with ipa-server-4.9.2-4.module+el8.4.0+11156+94d209c1
The CA installation fails how? Please provide the server installation log plus the spawn and debug logs found in /var/log/pki (and below)
Re-assigning to pki-core component as this is CA-related.
The issue is we have an untrusted java file being accessed by an interpreter. The fapolicyd rule is that scripts need to be trusted. How did the java file get installed to /var/lib/pki/pki-tomcat/work/Catalina/localhost/ROOT/org/apache/jsp/ ? Was it by rpm? Did someone just open an archive?
The work directory contains temporary working directories for the deployed web applications. What happened is that your ROOT webapp tried to compile the index.jsp, and failed for some reason. The java file was being created in that temp directory as a result of that real time JSP compilation, so whatever manages /var/lib/pki/pki-tomcat/webapps/ROOT/index.jsp is the culprit :) After some quick Googling to learn more about fapolicyd, I found https://access.redhat.com/solutions/5567781 which seems to be a solution? Maybe we need to add some additional rules to the default policy to cover this case?
That's what I'm trying to figure out. Do we need to change rules or is something not registering trust correctly. Since it's a temporary copy, trust is not the right solution. I'd change the suggested rules from that kb to include trust=1 on the subject side. But the suggested rule otherwise should solve the problem. I suppose this should get added to the rules that we ship. Reassigning to fapolicyd. Thanks for the discussion.
(In reply to Steve Grubb from comment #10)
> That's what I'm trying to figure out. Do we need to change rules or is
> something not registering trust correctly. Since it's a temporary copy,
> trust is not the right solution. I'd change the suggested rules from that kb
> to include trust=1 on the subject side. But the suggested rule otherwise
> should solve the problem. I suppose this should get added to the rules that
> we ship. Reassigning to fapolicyd. Thanks for the discussion.
I agree that trusting a temporary copy probably isn't a great idea, so maybe the PKI folks want to precompile the JSP beforehand (rather than compiling at runtime) and package that compiled class in the webapp? You still need to add a rule to the policy to trust it, but it would be permanent and in a better controlled location. See more info about precompilation of JSPs within a webapp at https://tomcat.apache.org/tomcat-9.0-doc/jasper-howto.html#Web_Application_Compilation :D
If this were fixed by precompiling the application, then it would be packaged and rpm would have a SHA256 hash for it making it automatically trusted. That would be a better solution than adding rules.
Comment 28RHEL Program Management
2023-09-19 12:50:20 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 29RHEL Program Management
2023-09-19 12:57:26 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 30Red Hat Bugzilla
2024-01-25 04:25:21 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days