Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1237129 - sshd -T does not output authenticationmethods with default value
sshd -T does not output authenticationmethods with default value
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssh (Show other bugs)
7.2
All Linux
low Severity low
: rc
: ---
Assigned To: Jakub Jelen
Stanislav Zidek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-06-30 08:47 EDT by Stanislav Zidek
Modified: 2016-11-03 16:18 EDT (History)
2 users (show)

See Also:
Fixed In Version: openssh-6.6.1p1-28.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 16:18:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2588 normal SHIPPED_LIVE Moderate: openssh security, bug fix, and enhancement update 2016-11-03 08:09:45 EDT

  None (edit)
Description Stanislav Zidek 2015-06-30 08:47:53 EDT
Description of problem:
Since AuthenticationMethods default value is an empty list, current logic of openssh does not dump it (using "sshd -T"). This is inconsistent with other options, which are dumped, even with default values.

Version-Release number of selected component (if applicable):
openssh-6.6.1p1-14.el7

How reproducible:
always

Steps to Reproduce:
1. make sure AuthenticationMethods is not in sshd_config
2. sshd -T |grep -i AuthenticationMethods

Actual results:
<empty output>

Expected results:
authenticationmethods

Additional info:
Considering low priority, we should probably wait until upstrem fixes this. See https://bugzilla.mindrot.org/show_bug.cgi?id=2398
Comment 6 errata-xmlrpc 2016-11-03 16:18:37 EDT
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://rhn.redhat.com/errata/RHSA-2016-2588.html

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