Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1637236

Summary: Default install has command shell with factory password
Product: [Fedora] Fedora Reporter: Stuart D Gathman <stuart>
Component: openas2Assignee: Stuart D Gathman <stuart>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: stuart
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openas2-2.10.0-1.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-02 02:27:46 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:

Description Stuart D Gathman 2018-10-08 23:39:20 UTC
Description of problem:
A default openas2 install configures a command shell listening on 14321 with a factory password.  On Fedora Workstation, the default firewalld config does not block it by default either.

Version-Release number of selected component (if applicable):
openas2-2.6.2-2.fc28.noarch

How reproducible:
always

Steps to Reproduce:
1. dnf install openas2
2. systemctl start openas2
3.

Actual results:
command shell (openas2 commands, not a general shell) enabled on 14321

Expected results:
admin action should be required to enable the command shell after setting a secure password.

Additional info:

Comment 1 Stuart D Gathman 2018-10-09 02:40:07 UTC
The simplest solution is to comment out the command shell in the default config as recommended by upstream docs.

Comment 2 Ben Cotton 2019-05-02 20:43:07 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

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 28 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 3 Stuart D Gathman 2019-10-23 22:26:18 UTC
Upstream version 2.10.0 disables socket command processor by default.  User will have to explicitly enable it, and then caveat emptor.

Comment 4 Fedora Update System 2019-10-23 22:34:59 UTC
FEDORA-2019-edefdc749c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-edefdc749c

Comment 5 Fedora Update System 2019-10-24 18:54:45 UTC
openas2-2.10.0-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-edefdc749c

Comment 6 Fedora Update System 2019-11-02 02:27:46 UTC
openas2-2.10.0-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.