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

Restore stu-home files #432

Merged
merged 3 commits into from
Jan 16, 2021
Merged

Conversation

laurelmay
Copy link
Member

In contrast to departmental guidance in 2018, it seems that it is now supported (and recommended) to access stu via sshfs support.

Technically this isn't sshfs; it's Nemo's sftp support. But it's all basically the same and will largely present the same to students.

This partially reverts commit 190e913.
This reverts commit 8bb2574.

In contrast to departmental guidance in 2018, it seems that it is now
[supported](https://wiki.cs.jmu.edu/student/utilities/sshfs)
(and recommended) to access stu via sshfs support.

This partially reverts commit 190e913.
This partially reverts commit 8bb2574.
@ripleymj
Copy link
Member

This is still probably as bad an idea as it ever was, but I do suppose it puts us in line with other platforms. When I run it, I get a nondescript text document icon on the desktop. Do you think we be possible to get something more network or disk related? Also curious how you'd feel about having the Ansible known_hosts module pre-push the stu key to prevent a nag on first connection?

@laurelmay laurelmay force-pushed the restore-stu-home branch 3 times, most recently from 458f090 to 50041b4 Compare January 16, 2021 22:15
@laurelmay
Copy link
Member Author

Alright @ripleymj I think that's done. The icon is updated to image and I have tried to have it implicitly trust stu.cs but I can't test the whole login flow since my account is dead.

@ripleymj
Copy link
Member

Purely for style, adding hash_host: yes will make the entry look like others.

As an actual problem, the known_hosts file is being created with root ownership and preventing any future keys from being added.

@laurelmay
Copy link
Member Author

Eww. How do we want to fix that? Would a { file: {state: present}} with the right owner before/after be good enough? Assuming they both work, do you have a preference for before or after?

@ripleymj
Copy link
Member

If we go that route, I think after would be safer to make sure we can't leave it in a bad state. Otherwise become/become_user might be the other option

@laurelmay laurelmay force-pushed the restore-stu-home branch 2 times, most recently from f948a1b to 56507b5 Compare January 16, 2021 22:50
@laurelmay
Copy link
Member Author

Rather than touching every user's config, why don't we just rely on setting it globally? Apparently there's already a decent default for GlobalKnownHostsFile per ssh_config(5). At some point we'll want to add some sort of linting/validation that the host key for stu.cs hasn't changed but that also probably happens on a predictable cadence.

@ripleymj
Copy link
Member

That works, and there will be screaming everywhere if that key changes. Do you want to remove creation of the $HOME/.ssh then, since we're not using it?

@laurelmay
Copy link
Member Author

Done 👍

@ripleymj ripleymj merged commit 9a58f28 into jmunixusers:main Jan 16, 2021
@laurelmay laurelmay deleted the restore-stu-home branch January 17, 2021 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants