Bug 1996803 - Grammatical errors with Insecure help text at Host Registration
Summary: Grammatical errors with Insecure help text at Host Registration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-23 17:45 UTC by Griffin Sullivan
Modified: 2022-12-22 15:14 UTC (History)
4 users (show)

Fixed In Version: foreman-3.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:29:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34250 0 Normal New Grammatical errors with Insecure help text at Host Registration 2022-01-12 11:22:43 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:29:49 UTC

Description Griffin Sullivan 2021-08-23 17:45:42 UTC
Description of problem:
The help text when you click the "?" next to "Insecure" has a grammatical error under Hosts > Register Host.

Version-Release number of selected component (if applicable):
6.10

How reproducible:
Easily

Steps to Reproduce:
1. Go to Hosts > Register Host
2. Click on the "?" next to the "Insecure" check box

Actual results:
"If the target machine does not trust the host SSL certificate, the initial connection could be subject to Man in the middle attack. If you accept the risk and do not require the server authenticity to be verified, you can enable insecure argument for the initial curl. Note that all subsequent communication is then properly secured, because the initial request deploys the SSL certificate for the rest of the registration process."

Expected results:
"If the target machine does not trust the host SSL certificate, the initial connection could be subject to a man-in-the-middle attack. If you accept the risk and do not require the server authenticity to be verified, you can enable insecure argument for the initial curl. Note that all subsequent communication is then properly secured, because the initial request deploys the SSL certificate for the rest of the registration process."

Additional notes:
I just added "a man-in-the-middle attack" to make the text more readable and consistent.

Comment 1 Leos Stejskal 2022-01-12 11:22:43 UTC
Created redmine issue https://projects.theforeman.org/issues/34250 from this bug

Comment 2 Bryan Kearney 2022-01-14 12:04:43 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34250 has been resolved.

Comment 6 errata-xmlrpc 2022-07-05 14:29:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498


Note You need to log in before you can comment on or make changes to this bug.