Bug 1671862 - Geo-rep setup creates an incorrectly formatted authorized_keys file
Summary: Geo-rep setup creates an incorrectly formatted authorized_keys file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHGS 3.5.0
Assignee: Sunny Kumar
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks: 1679401 1696806
TreeView+ depends on / blocked
 
Reported: 2019-02-01 22:19 UTC by Andrew Robinson
Modified: 2022-03-13 16:54 UTC (History)
9 users (show)

Fixed In Version: glusterfs-6.0-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1679401 (view as bug list)
Environment:
Last Closed: 2019-10-30 12:20:20 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:20:42 UTC

Comment 2 Andrew Robinson 2019-02-01 22:43:12 UTC 
Description of problem:


When creating an ssh authorized_keys file prior to executing the push-pem command, the geo-rep setup inserts an extra space before the "ssh-rsa" label. This gets flagged by an enterprise customer's security scan as a security violation. 


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

RHGS 3.4

How reproducible:

Work through the geo-replication setup

Steps to Reproduce:
1.
2.
3.

Actual results:

There are two spaces between 'command="/usr/libexec/glusterfs/gsyncd"' and 'ssh-rsa'

Expected results:

There should only be one space. 


Additional info:
Comment 4 Sunny Kumar 2019-02-21 05:29:37 UTC 
Upstream Patch : https://review.gluster.org/#/c/glusterfs/+/22246
Comment 25 errata-xmlrpc 2019-10-30 12:20:20 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, 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/RHEA-2019:3249
Note You need to log in before you can comment on or make changes to this bug.