You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The session is not started using PAM currently, instead using "docker exec." Using PAM will correctly mount any libpam_mount volumes on connect, for example.
The problem is that this will require SSH forwarding the raw password through to the session libpam. Probably, something will need to hook libpam in skiff root, and forward the data to the container libpam if it exists. (Non-trivial).
The text was updated successfully, but these errors were encountered:
The session is not started using PAM currently, instead using "docker exec." Using PAM will correctly mount any libpam_mount volumes on connect, for example.
The problem is that this will require SSH forwarding the raw password through to the session libpam. Probably, something will need to hook libpam in skiff root, and forward the data to the container libpam if it exists. (Non-trivial).
The text was updated successfully, but these errors were encountered: