Bug 1948588

Summary:	Ksh allows exiting restricted mode, besides documented as not allowing
Product:	Red Hat Enterprise Linux 8	Reporter:	Paulo Andrade <pandrade>
Component:	ksh	Assignee:	Lukáš Zaoral <lzaoral>
Status:	CLOSED MIGRATED	QA Contact:	Karel Volný <kvolny>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	kvolny, lzaoral, vmihalko
Target Milestone:	beta	Keywords:	MigratedToJIRA, Patch, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ksh-20120801-260.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1948586	Environment:
Last Closed:	2023-11-29 12:07:51 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:	1948586
Bug Blocks:

Description Paulo Andrade 2021-04-12 14:22:32 UTC

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

From manual page:

              -r      Enables  the  restricted  shell.   This option cannot be
                      unset once set.

  But one can exit it with:

$ set +r

  One can work an a restricted shell with:

+ Create a ~/.profile that sets PATH to, for example, /rbin
+ Add symbolic links to /rbin, e.g.
  # ln -sf /bin/ls /rbin
+ Remove any unwanted environment variable or function from
  ~/.profile with unset.

  Above works with bash, on basic tests using .bash_profile:

export PATH=/rbin
unset command_not_found_handle

and user shell set to /bin/rbash

  Restricted shells overall are somewhat of a fragile solution,
but if the environment is really very small, it is a somewhat
safe option.

Comment 2 Lukáš Zaoral 2023-08-23 14:46:46 UTC

Upstream commit with fix: https://github.com/ksh93/ksh/commit/74b4162178c8a2347491b9fd3a22d8e6e1b7e831

Comment 3 Lukáš Zaoral 2023-09-18 10:59:39 UTC

C8S PR: https://gitlab.com/redhat/centos-stream/rpms/ksh/-/merge_requests/9

Comment 4 RHEL Program Management 2023-11-29 12:07:35 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-11-29 12:07:51 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.