Bug 1146161

Summary:	korn shell installation does not include symlink for the restricted shell
Product:	Red Hat Enterprise Linux 7	Reporter:	Henk Langeveld <henk>
Component:	ksh	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED ERRATA	QA Contact:	Martin Frodl <mfrodl>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	kdudka, mfrodl, ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ksh-20120801-22.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1162687 (view as bug list)		Environment:
Last Closed:	2015-03-05 13:41:52 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:
Bug Depends On:
Bug Blocks:	1162687

Description Henk Langeveld 2014-09-24 15:43:34 UTC

Description of problem:


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


How reproducible:
Consistently

Steps to Reproduce:
1. yum install ksh
2. type ksh rksh

Actual results:
ksh is /bin/ksh
-bash: type: rksh: not found


Expected results:
I would expect a link for rksh to exist.  The actually functionality is builtin
to the shell.

Additional info:

The synopsis for the ksh man page lists 'ksh', 'rksh', and 'pfksh'.
The 'rksh' functionality is built in, and only requires the symlink.
The 'pfksh' functionality is platform dependent (depends on solaris/illumos pfexec(1)) and could be removed from the man page.

AT&T ksh is my preferred shell for scripting, and does not share the same vulnerabilities as Bash. (Cf. CVE-2014-6271)

Comment 2 Henk Langeveld 2014-09-24 15:48:53 UTC

It's a drudge to keep adding the symlink during deployment, when a couple of lines in the rpm definition could do the trick.

Comment 8 errata-xmlrpc 2015-03-05 13:41:52 UTC

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/RHBA-2015-0300.html