View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000540 | 1003.1(2008)/Issue 7 | System Interfaces | public | 2012-02-01 19:05 | 2012-02-10 12:07 |
| Reporter | EdSchouten | Assigned To | ajosey | ||
| Priority | normal | Severity | Editorial | Type | Enhancement Request |
| Status | Closed | Resolution | Rejected | ||
| Name | Ed Schouten | ||||
| Organization | Kumina bv | ||||
| User Reference | |||||
| Section | endutxent() | ||||
| Page Number | 806 | ||||
| Line Number | n/a | ||||
| Interp Status | --- | ||||
| Final Accepted Text | |||||
| Summary | 0000540: Add API for adding entries to user accounting database by passing a pseudo-terminal master file descriptor | ||||
| Description | There are libraries out there, such as `libutempter' that can be used to update utmp(x) entries without any root-like privileges, by passing the file descriptor to a pseudo-terminal master device. These libraries typically spawn a setuid binary to perform the update to the database. It would be nice if POSIX were to integrate such a feature. Currently there is quite some inconsistency in current implementations whether or not they work without any additional privileges. In (almost) all cases, these unprivileged applications are only interested in managing entries for pseudo-terminals. | ||||
| Desired Action | This could be solved by adding a function like: struct utmpx *fpututxline(int fd, const struct utmpx *utmpx); The function would work the same as pututxline(), with the exception that ut_line, ut_id and ut_user are ignored, because they are derived from `fd' and the credentials of the running application. This function shall only work on pseudo-terminal master devices -- not regular TTYs or other character devices. | ||||
| Tags | No tags attached. | ||||
|
|
Also, ut_pid and ut_tv should also be filled in automatically. |
|
|
This item is rejected as out of scope since it proposes a new API. The Austin Group has a specific process which needs to be followed for proposals for new APIs to bring them into scope. See Austin/112r3 and Austin/164 for details. See the text starting : New Work Items : in http://www.opengroup.org/austin/docs/austin_112r3.txt Also see the diagram in: http://www.opengroup.org/austin/docs/austin_164.pdf |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-02-01 19:05 | EdSchouten | New Issue | |
| 2012-02-01 19:05 | EdSchouten | Status | New => Under Review |
| 2012-02-01 19:05 | EdSchouten | Assigned To | => ajosey |
| 2012-02-01 19:05 | EdSchouten | Name | => Ed Schouten |
| 2012-02-01 19:05 | EdSchouten | Organization | => Kumina bv |
| 2012-02-01 19:05 | EdSchouten | Section | => endutxent() |
| 2012-02-01 19:05 | EdSchouten | Page Number | => 806 |
| 2012-02-01 19:05 | EdSchouten | Line Number | => n/a |
| 2012-02-01 19:07 | EdSchouten | Note Added: 0001116 | |
| 2012-02-10 12:07 | ajosey | Interp Status | => --- |
| 2012-02-10 12:07 | ajosey | Note Added: 0001121 | |
| 2012-02-10 12:07 | ajosey | Status | Under Review => Closed |
| 2012-02-10 12:07 | ajosey | Resolution | Open => Rejected |
