Bug 1883312
Summary: | java.txt file contains both security properties and system properties | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Andrew John Hughes <ahughes> |
Component: | crypto-policies | Assignee: | Alexander Sosedkin <asosedki> |
Status: | CLOSED MIGRATED | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.3 | CC: | mmillson, ssorce, szidek |
Target Milestone: | rc | Keywords: | MigratedToJIRA, Reopened, Triaged |
Target Release: | 8.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-19 20:30:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1882178 | ||
Bug Blocks: | 1882168, 1882185 |
Description
Andrew John Hughes
2020-09-28 18:08:37 UTC
Seems 1882178 already covers the 1023 issue. What would ideally be the format of the system properties configuration file? (In reply to Tomas Mraz from comment #2) > What would ideally be the format of the system properties configuration file? The current format is fine. What we need is two files instead of one, so they can act as input to different parts of the JDK. That's the most efficient way of handling this, as then the security properties code can completely ignore the system properties file (and vice versa). I'd rather fix this in 9-onwards-only (bz1974274), feel free to reopen if you strongly feel otherwise. 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. 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. |