This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1948588 - Ksh allows exiting restricted mode, besides documented as not allowing
Summary: Ksh allows exiting restricted mode, besides documented as not allowing
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ksh
Version: 8.4
Hardware: All
OS: Linux
unspecified
low
Target Milestone: beta
: ---
Assignee: Lukáš Zaoral
QA Contact: Karel Volný
URL:
Whiteboard:
Depends On: 1948586
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-12 14:22 UTC by Paulo Andrade
Modified: 2023-11-29 12:07 UTC (History)
3 users (show)

Fixed In Version: ksh-20120801-260.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1948586
Environment:
Last Closed: 2023-11-29 12:07:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ksh93/ksh/commit/74b4162178c8a2347491b9fd3a22d8e6e1b7e831 0 None None None 2023-09-15 10:35:43 UTC
Gitlab redhat/centos-stream/rpms ksh merge_requests 9 0 None opened Fix set +r so that it cannot unset the restricted option 2023-09-18 10:59:39 UTC
Red Hat Issue Tracker   RHEL-17627 0 None Migrated None 2023-11-29 12:07:47 UTC

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 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.


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