Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start shell session with pam #3

Open
paralin opened this issue Sep 23, 2020 · 1 comment
Open

Start shell session with pam #3

paralin opened this issue Sep 23, 2020 · 1 comment
Assignees

Comments

@paralin
Copy link
Collaborator

paralin commented Sep 23, 2020

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).

@paralin paralin self-assigned this Sep 23, 2020
@paralin
Copy link
Collaborator Author

paralin commented Sep 23, 2020

This might be acceptable (with a flag to enable pam in the skiff-core.yaml):

ssh host
Password: [password]
Last login: Tue Sep 22 17:29:09 PDT 2020 on pts/7
reenter password for pam_mount: [password]

Awkward but works and seems to be the native behavior anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant