View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000084 | 1003.1(2008)/Issue 7 | Base Definitions and Headers | public | 2009-06-29 10:21 | 2013-04-16 13:06 |
| Reporter | drepper | Assigned To | ajosey | ||
| Priority | normal | Severity | Objection | Type | Omission |
| Status | Closed | Resolution | Accepted As Marked | ||
| Name | Ulrich Drepper | ||||
| Organization | Red Hat | ||||
| User Reference | |||||
| Section | Pathname | ||||
| Page Number | 75 | ||||
| Line Number | 2147 | ||||
| Interp Status | --- | ||||
| Final Accepted Text | 0000084:0000194 | ||||
| Summary | 0000084: PATH and filenames containing colons | ||||
| Description | OBJECTION Enhancement Request Number 9 drepper:xxxxxxxxxx Defect in XBD Pathname (rdvk# 1) {ud-filename-colon} Mon, 8 Jun 2009 07:56:12 +0100 (BST) _____________________________________________________________________________ The location of the bug is actually one place that is effected. And I'm not sure where the final solution will apply. The problem is the definition of PATH and similar environment variables and similar concepts. The definition of PATH says: This variable shall represent the sequence of path prefixes that certain functions and utilities apply in searching for an executable file known only by a filename. The prefixes shall be separated by a <colon> (:). The definition of path prefix refers to pathname which in turn refers to filename for the actual content of the string and the filename definition says: The characters composing the name may be selected from the set of all character values excluding the <slash> character and the null byte. I.e., the path components are not disallowed to contain colons. This makes it impossible to handle the pathname components correctly. The shell, execvp(), etc only see a string and cannot differentiate between colons in pathname components and those between the paths components. We have to restrict filenames used in paths. I think restricting pathname to pathname components and then define pathname components appropriately. This problem spreads far beyond POSIX's use of path. | ||||
| Desired Action | Change page 76, line 2053 to: A filename not containing a colon (':'). Change page 75, line 2147 from: [..] followed by zero or more filenames separated [...] to [..] followed by zero or more pathname components separated [...] | ||||
| Tags | tc1-2008 | ||||
|
|
Insert a New paragraph after XBD section 8.3 Environment variables page 178 line 5687 Since colon is a separator in this context, directory names that might be used in PATH should not include a colon character. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-06-29 10:21 | geoffclare | New Issue | |
| 2009-06-29 10:21 | geoffclare | Status | New => Under Review |
| 2009-06-29 10:21 | geoffclare | Assigned To | => ajosey |
| 2009-06-29 10:21 | geoffclare | Name | => Ulrich Drepper |
| 2009-06-29 10:21 | geoffclare | Organization | => Red Hat |
| 2009-06-29 10:21 | geoffclare | Section | => Pathname |
| 2009-06-29 10:21 | geoffclare | Page Number | => 75 |
| 2009-06-29 10:21 | geoffclare | Line Number | => 2147 |
| 2009-06-29 10:22 | geoffclare | Tag Attached: real bug in aardvark | |
| 2009-06-29 10:23 | geoffclare | Reporter | geoffclare => drepper |
| 2009-08-06 15:55 | ajosey | Tag Detached: real bug in aardvark | |
| 2009-08-13 15:56 | ajosey | Interp Status | => --- |
| 2009-08-13 15:56 | ajosey | Note Added: 0000194 | |
| 2009-08-13 15:56 | ajosey | Status | Under Review => Resolved |
| 2009-08-13 15:56 | ajosey | Resolution | Open => Accepted As Marked |
| 2009-08-13 15:57 | ajosey | Final Accepted Text | => 0000084:0000194 |
| 2010-08-27 13:21 | ajosey | Tag Attached: tc1-2008 | |
| 2013-04-16 13:06 | ajosey | Status | Resolved => Closed |
