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

Setting up SSH (config) #171

Open
Kyslik opened this issue Oct 16, 2017 · 7 comments
Open

Setting up SSH (config) #171

Kyslik opened this issue Oct 16, 2017 · 7 comments

Comments

@Kyslik
Copy link
Collaborator

Kyslik commented Oct 16, 2017

Setting up SSH config is maybe a bit out of scope, but sure is helpful.

Something similar to this https://serversforhackers.com/s/ssh-usage-tips-and-tricks but in text.

@simeg
Copy link
Collaborator

simeg commented Oct 17, 2017

I agree, this would be helpful.

Some topics that I'd like to be covered:

  • What SSH keys are and why they exist
  • Creating SSH keys
  • The SSH-agent
  • Executing a command on a remote server using SSH
  • SCP maybe? Since it's based on SSH, and it's very useful

@Kyslik
Copy link
Collaborator Author

Kyslik commented Oct 19, 2017

Good info to have is also how to copy ssh key to my server and troubleshooting "why my ssh key does not work":

  • home folder (on remote) needs to have 755 permissions (or .ssh folder, not really sure)
  • authorized_keys file needs to be set to 600

@sb2nov
Copy link
Owner

sb2nov commented Oct 21, 2017

+1 to these points.

@sb2nov sb2nov added need-help and removed need-help labels Nov 7, 2017
@Kyslik Kyslik self-assigned this Dec 22, 2017
@Kyslik
Copy link
Collaborator Author

Kyslik commented Jan 4, 2018

I think we need to tackle this from more than just one context, from top of my head:

  1. communicating with git server GitHub / GitLab (obviously using ssh-key)
  2. ssh to a box
  3. explanation of .ssh/config file

3rd one is not a context but can be applied to first and second context I mention above.


Besides that, shall we create new section something like "secure shell SSH" or shall we put it within iTerm2 setup.


Where do we draw the line? Should we as well explain how to configure sshd to accept ssh-key login attempts only on a box? - I think we should put as much info as possible.

@simeg
Copy link
Collaborator

simeg commented Jan 6, 2018

I like your enthusiasm @Kyslik! What if we start with the basic stuff and then we could take it from there? See how it feels :) I definitely think it should be in a separate section called something like "Secure Shell (SSH)".

@sb2nov
Copy link
Owner

sb2nov commented Jan 7, 2018

Sounds like a great idea. I agree we could start with the basics and slowly build this over time.

@simeg
Copy link
Collaborator

simeg commented Feb 4, 2018

Some of the topics were covered in PR #192

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

3 participants