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

Build script to create miniconfig #524

Open
owendelong opened this issue Jan 28, 2023 · 2 comments
Open

Build script to create miniconfig #524

owendelong opened this issue Jan 28, 2023 · 2 comments
Assignees
Labels
bug Deferred for Next Year Items deferred to the Next SCaLE

Comments

@owendelong
Copy link
Collaborator

Description

Currently miniconfig is static and doesn't track current SSH keys.

Acceptance Criteria

Have a script which builds an appropriate minimal config for flashing containing all current SSH keys.

@owendelong owendelong self-assigned this Sep 13, 2023
@owendelong owendelong added CRITICAL Bugs which must be urgently addressed SCaLE21x labels Sep 13, 2023
@owendelong owendelong added Deferred for Next Year Items deferred to the Next SCaLE and removed CRITICAL Bugs which must be urgently addressed SCaLE21x labels Jan 28, 2024
@owendelong
Copy link
Collaborator Author

Alternatively, manage a private key that works with miniconfig for a "miniadmin" user that is unique to miniconfig and which can be shared with team members. This would allow miniconfig to remain static as well as reducing its size, since it would only need to contain one public key. Given the extremely low attack surface of the time miniconfig is loaded on the switches, it might even be worth considering embedding this private key in the switch_config_loader script and have it auto-add it to the running user's .ssh/ directory and reference it when attaching to the switch to load a config on top of miniconfig.

This approach would require some additional thought and considerations, but I wanted to get it written down first for wider discussion.

@sarcasticadmin
Copy link
Member

This approach seems sensible.

Given the extremely low attack surface of the time miniconfig is loaded on the switches, it might even be worth considering embedding this private key in the switch_config_loader script and have it auto-add it to the running user's .ssh/ directory and reference it when attaching to the switch to load a config on top of miniconfig.

Putting this into a nix devShell we can wrap ssh flags (-i, etc.) so you wouldnt even need to copy the key into your ~/.ssh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Deferred for Next Year Items deferred to the Next SCaLE
Projects
None yet
Development

No branches or pull requests

2 participants