Red Hat Bugzilla – Bug 173595
os.path.realpath can't handle symlink loops
Last modified: 2013-04-12 13:13:10 EDT
Description of problem:
The problem is described in
Version-Release number of selected component (if applicable):
Steps to Reproduce:
See upstreams report
The problem is fixed in newer releases upstreams. The reason for this bug
report is that we need this fix in the python in RHEL3 and RHEL4, none of which
has the fix. In the case of RHEL4, it would probably be enough to upgrade
python to 2.3.5. For RHEL3, I guess a backport will be necessary.
Created attachment 121334 [details]
Revision 1.67 - (view) (download) (as text) (annotate) - [select for diffs]
Sat Jul 10 22:55:13 2004 UTC (16 months, 1 week ago) by bcannon
Changes since 1.66: +30 -6 lines
Diff to previous 1.66
posixpath.realpath() now detects symlink loops and returns the path just before
the loop starts.
Closes bug #930024. Thanks AM Kuchling.
Revision 1.71 - (view) (download) (as text) (annotate) - [select for diffs]
Sat Aug 14 15:01:53 2004 UTC (15 months, 1 week ago) by jlgijsbers
Changes since 1.70: +9 -7 lines
Diff to previous 1.70
bug #990669: os.path.realpath() will resolve symlinks before normalizing the
path, as normalizing the path may alter the meaning of the path if it contains
Also add tests for infinite symlink loops and parent symlinks that need to be
Revision 1.74 - (view) (download) (as text) (annotate) - [select for diffs]
Fri Jun 3 14:24:43 2005 UTC (5 months, 2 weeks ago) by birkenfeld
Changes since 1.73: +1 -1 lines
Diff to previous 1.73
Bug #1213894: os.path.realpath didn't resolve symlinks that were the first
component of the path.
The client is asking for an update on this issue and has asked why this was not
fixed in the latest update release.
Committed the patch and building as python-2.2.3-6.6
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.