| Summary: | sshd_config Match section - pam functions cannot use stdout? | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Akshay <akshay.moghe> |
| Component: | sshd | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | major | CC: | djm |
| Priority: | P3 | ||
| Version: | 7.6p1 | ||
| Hardware: | amd64 | ||
| OS: | Linux | ||
|
Description
Akshay
2018-09-26 07:58:01 AEST
Bumping up importance (P = priority?) to see if I can get some visibility. stdout isn't attached in any case. The session modules record the output of the PAM conversation functions at the end of the authentication phase and it is replayed later when the user has an actual channel over which to send them. The difference is not stdout, but that the login messages are suppressed when a command is executed so as not to pollute the command's stdout. > The difference is not stdout, but that the login messages are suppressed when a command is executed so as not to pollute the command's stdout.
Gotcha. In that case, is there a way to un-suppress those messages? I'm looking to use a `Match` clause along with a ForceCommand to force a particular login shell. When used this way, the login messages cease to work. (I guess I'm in the need for a `ForceShell` if one exists).
I'm not sure - you *might* be able to use a PAM session session - the messages for these are queued and displayed at login time. workaround provided. Please reopen if it doesn't work close bugs that were resolved in OpenSSH 8.5 release cycle |