Delegate privileged authentication to sudo PAM
This commit is contained in:
parent
7872991e0b
commit
026bbc4eff
8 changed files with 266 additions and 236 deletions
|
|
@ -46,7 +46,8 @@ before entering Privileged Mode if you sorted only for inspection.
|
|||
## Enter Privileged Mode
|
||||
|
||||
Press `Ctrl+E`. The application first checks for existing sudo authorization.
|
||||
If authorization is not already available, it asks for your password. Before
|
||||
If authorization is not already available, it temporarily returns control of
|
||||
the terminal to `sudo` and its configured PAM authentication method. Before
|
||||
enabling mutations it verifies write access and creates a Pre-edit Backup.
|
||||
|
||||
If authorization, permission validation, or backup creation fails, the
|
||||
|
|
@ -192,10 +193,12 @@ reachable through the TUI. Editing them manually is not a supported workflow.
|
|||
|
||||
## Troubleshooting
|
||||
|
||||
### Privileged Mode asks for a password
|
||||
### Privileged Mode needs authentication
|
||||
|
||||
This is expected when no cached sudo authorization is available. Canceling the
|
||||
password prompt leaves the application in Read-only Mode.
|
||||
This is expected when no cached sudo authorization is available. `hosts` never
|
||||
collects credentials; `sudo` and PAM present any configured authentication
|
||||
method, such as Touch ID or a password prompt. Canceling authentication leaves
|
||||
the application in Read-only Mode.
|
||||
|
||||
### Privileged Mode cannot be enabled
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue