Bug 1007013

Summary:	packstack should handle ssh keys in a more friendly fashion
Product:	[Fedora] Fedora	Reporter:	John Dennis <jdennis>
Component:	openstack-packstack	Assignee:	Martin Magr <mmagr>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	derekh, itamar, Jan.van.Eldik, mmagr, p, sandro
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 17:09:01 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:

Description John Dennis 2013-09-11 17:55:24 UTC

When I ran packstack for the first time I was almost immediately prompted to unlock my ssh key using my passphrase.

Problem 1: There is no way I'm typing in my ssh passphrase into a prompt unless I understand what it's being used for. How do I know this isn't some phishing attempt, malware, or who knows what?

I found out via IRC that ssh is being used as part of the setup process in a legitimate fashion to copy components and set up authenticated communication channels to perform operations (or so I believe).

So I concluded it was legitimate request to provide the passphrase to my key and entered it.

Problem 2: But as packstack ran I was prompted for my passphrase countless times. At some point (maybe after 20 times of entering my passphrase) I got so frustrated that I control-c'ed out of packstack. I then ran ssh-agent and added my key.

Then I ran packstack again, although it ran to completion it was in a screwed up state (the subject of another bug report). I'll confess after setting up ssh-agent I didn't realize one had to use the answer file from the previous run. Eventially I did try and use the original answer from the initial run but I never could get packstack to complete without errors (mostly related to using the wrong mysgl admin password). Long story short, I had to nuke the VM and rebuild a new VM and start over completely, this time armed with the knowledge I had better have ssh-agent running with my key loaded before I ran packstack.

Suggestion:

Since access to your ssh key is so vital to the operation of packstack it should verify you have a valid key loaded, if not it should exit or assist you in adding it to ssh-agent or whatever keyring might be in use. If you key is not available it should explain in one or two sentences why you're being prompted for you key and what use it's going to be put to. Maybe it should even allow you to select the key you want to use.

Comment 1 Fedora Admin XMLRPC Client 2013-10-14 09:51:30 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2013-10-14 09:52:11 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-01-09 19:48:22 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 17:09:01 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.