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.

Sign up for GitHub

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

Jump to bottom

README: update ssh pitfalls for sk-ssh-* keys and update mine. #163

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

README: update ssh pitfalls for sk-ssh-* keys and update mine. #163

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a9f129
README: update ssh pitfalls for sk-ssh-* keys
Janik-Haag Jul 27, 2023
8b37f4d
keys/janik: update keys
Janik-Haag Jul 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,13 +93,15 @@ First, put this in your `configuration.nix`:
```

**Note:** Make sure the SSH key specified above does *not* have a
password, otherwise `nix-build` will give an error along the lines of:
passphrase, otherwise `nix-build` will give an error along the lines of:

> unable to open SSH connection to
> 'ssh://[email protected]': cannot connect to
> '[email protected]'; trying other available
> machines...

You should also avoid keys generated with u2f-devices (f.e. yubikeys) like a sk-ssh-ed25519 since you have to press the presence button for every single package build on a remote server.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC this isn't an issue if ControlMaster/ControlPersist ssh settings are used?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It didn't work when setting them in my user ssh config, it might work when setting it system wide or for the root user, I can try that if you want me to.


Then run an initial SSH connection as root to setup the trust
fingerprint:

Expand Down
4 changes: 1 addition & 3 deletions keys/janik
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1 @@
[email protected] AAAAGnNrLXNzaC1lZDI1NTE5QG9wZW5zc2guY29tAAAAIJ4yq7oHBO2iPs4xj797a//0ypnBr27sSadKUeL2NsK6AAAABHNzaDo= [email protected]
[email protected] AAAAGnNrLXNzaC1lZDI1NTE5QG9wZW5zc2guY29tAAAAIOYg513QZsVzoyVycXZjg4F3T3+OwtcY3WAhrlfyLgLTAAAABHNzaDo= [email protected]
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBLZxVITpJ8xbiCa/u2gjSSIupeiqOnRh+8tFIoVhCON [email protected]
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHLuKhW4+sDUwT4DJS27VZWFTE0Uq71omTo0q4EMgxzh [email protected]