MAINT: don't mess with plc ssh key configs, avoid Administrator account #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SSH Keys
While working on pcdshub/twincat-bsd-ansible#14 I realized that having the
publickey
option in the ssh config here means that:Procedurally, doing it like this (after the edit) requires you to have access to the admin password, which seems in line with the procedure we want people to use for other protected systems like the switches etc.
Alternatively, we could do plc auth by having everyone send their public key to every plc, but that feels wrong.
Non-admin user
The other change here is to make it so you log in as a non-admin user by default. This means you need to opt-in as the Administrator user by doing e.g.
ssh Administrator@plc-tst-bsd2
, and if you simplyssh plc-tst-bsd2
you will log in asecs-user
instead.