Bug 1671862

Summary: Geo-rep setup creates an incorrectly formatted authorized_keys file
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Andrew Robinson <anrobins>
Component: geo-replicationAssignee: Sunny Kumar <sunkumar>
Status: CLOSED ERRATA QA Contact: Rahul Hinduja <rhinduja>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: amukherj, avishwan, bkunal, csaba, pasik, rhs-bugs, sheggodu, storage-qa-internal, sunkumar
Target Milestone: ---   
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1679401 (view as bug list) Environment:
Last Closed: 2019-10-30 12:20:20 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:    
Bug Blocks: 1679401, 1696806    

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