Bug 820331 - Vim syntax file for sshdconfig is missing newer keyword entries
Vim syntax file for sshdconfig is missing newer keyword entries
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vim (Show other bugs)
All Linux
unspecified Severity low
: rc
: ---
Assigned To: Karsten Hopp
Filip Holec
: EasyFix
Depends On:
Blocks: 947784 1159824 1404257
  Show dependency treegraph
Reported: 2012-05-09 12:19 EDT by Kwan Lowe
Modified: 2016-12-13 08:36 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1404257 (view as bug list)
Last Closed: 2015-07-22 02:27:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kwan Lowe 2012-05-09 12:19:20 EDT
Description of problem:
The vim syntax file does not contain the most recent SSHD configuration keywords, including:


Version-Release number of selected component (if applicable):

How reproducible:

Edit the /etc/ssh/sshd_config file. Keywords such as PermitTunnel should be highlighted but are not.

Steps to Reproduce:
1. Edit sshd_config
Actual results:
PermitTunnel, and other keywords, are not highlighted.

Expected results:
Keywords should be highlighted.

Additional info:
Comment 2 RHEL Product and Program Management 2012-09-07 01:34:06 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 6 Karsten Hopp 2015-03-31 10:02:46 EDT
Syntax file updated
Comment 10 errata-xmlrpc 2015-07-22 02:27:23 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.


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