| Anonymous | Login | 2024-11-23 00:59 MST |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0013951 | ClearOS | app-network - Network Settings | public | 2017-03-21 09:57 | 2017-06-05 08:07 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | tweak | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 7.3.1 Updates | Fixed in Version | 7.3.1 Updates | ||||||
| Summary | 0013951: Tweak API to only use sudoers when necessary | ||||||||
| Description | Some network API calls need to be fast and/or are called very frequently, e.g. Ajax webconfig pages, console displaying the current IP, etc. Getting *all* the network information from a particular interface requires sudoers access, notably: - ifcfg-X files can have stored WiFi passwords - upstream_proxy.conf can have stored username/password settings for a proxy However, many API callers don't need _all_ the network information, just some subset (e.g. current IP address). Continue to tweak the API to handle these scenarios. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-03-21 09:57 | user2 | New Issue | |
| 2017-03-21 10:05 | user2 | Relationship added | parent of 0013961 |
| 2017-03-21 10:05 | user2 | Assigned To | => user2 |
| 2017-03-21 10:05 | user2 | Status | new => confirmed |
| 2017-06-05 08:07 | user2 | Target Version | 7.4.0 Beta 1 => 7.3.1 Updates |
| 2017-06-05 08:07 | user2 | Status | confirmed => resolved |
| 2017-06-05 08:07 | user2 | Fixed in Version | => 7.3.1 Updates |
| 2017-06-05 08:07 | user2 | Resolution | open => fixed |
| 2017-06-05 08:07 | user2 | Status | resolved => closed |
|
Issue History |