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.
Example steps to reproduce:
$ echo 'this is .bashrc' > ~/.bashrc
$ echo 'this is .bash_profile' > ~/.bash_profile
$ ssh test@localhost
...
this is .bash_profile
$ ssh test@localhost whoami
...
this is .bashrc
The manual page says:
Bash attempts to determine when it is being run with its standard
input connected to a network connection, as when executed by the
remote shell daemon, usually rshd, or the secure shell daemon sshd.
If bash determines it is being run in this fashion, it reads and
executes commands from ~/.bashrc, if that file exists and is read‐
able.
The manual page should reflect it is only for non interactive shells.
Maybe should also document that if bash is built with the preprocessor
SSH_SOURCE_BASH then it would also source .bashrc for interactive shells.
From changelog:
* Thu Oct 23 2008 Roman Rakus <rrakus> - 3.2-28
- Removing Requires for mktemp and ncurses, which cause
dependencing loop
- Enabling #define SSH_SOURCE_BASHRC, because ssh changed.
Resolves: #458839
- Catch signals right after calling execve()
Resolves: #455548
it appears the current behavior is contradictory to
https://bugzilla.redhat.com/show_bug.cgi?id=458839#c3
also, it appears the patch bash-3.2-ssh_source_bash.patch is not
making effect; it likely was looking like working because
.bash_profile sources .bashrc, but in the reproducer steps in the
original report it was modified to avoid getting confused with it.
(I did write a typo with SSH_SOURCE_BASH instead of SSH_SOURCE_BASHRC
ealier...)
Comment 8RHEL Program Management
2023-09-20 19:17:36 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 9RHEL Program Management
2023-09-20 19:22:39 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.
Example steps to reproduce: $ echo 'this is .bashrc' > ~/.bashrc $ echo 'this is .bash_profile' > ~/.bash_profile $ ssh test@localhost ... this is .bash_profile $ ssh test@localhost whoami ... this is .bashrc The manual page says: Bash attempts to determine when it is being run with its standard input connected to a network connection, as when executed by the remote shell daemon, usually rshd, or the secure shell daemon sshd. If bash determines it is being run in this fashion, it reads and executes commands from ~/.bashrc, if that file exists and is read‐ able. The manual page should reflect it is only for non interactive shells. Maybe should also document that if bash is built with the preprocessor SSH_SOURCE_BASH then it would also source .bashrc for interactive shells.