Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #1270925 +++

Description of problem:

I have just updated our options test and found out that there are still some options/directives not dumped by sshd -T, namely:
allowgroups
allowusers
authorizedkeyscommand
authorizedkeyscommandrunas
authorizedprincipalsfile
chrootdirectory
denygroups
denyusers
forcecommand
hostcertificate
kerberosgetafstoken
match
requiredauthentications
revokedkeys
trustedusercakeys

("match" is probably not a problem)

Version-Release number of selected component (if applicable):
openssh-5.3p1-111.el6

How reproducible:
always

Steps to Reproduce:
1. install clean machine with openssh-server
2. sshd -T |grep DESIRED_OPTION

Actual results:
nothing

Expected results:
DESIRED_OPTION default_value

(In reply to Stanislav Zidek from comment #0)
> allowgroups
> allowusers
> denygroups
> denyusers
This would work, since it doesn't require any argument, if I am right

> authorizedkeyscommand
> authorizedkeyscommandrunas
> authorizedprincipalsfile
> chrootdirectory
> forcecommand
> hostcertificate
> kerberosgetafstoken
> requiredauthentications
> revokedkeys
> trustedusercakeys
These should have default "none" written out. For most of them, there are filled upstream bugs, but I belive, this is really low priority, since we can get usable config now (note, that we will also get these, if they are in the source config).

> match
this doesn't make sense, since it is not standalone option.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.