Include PowerShell instructions for SSH on Windows / SSH worksheet

tomeshnet / p2p-internet-workshop

Building the Peer-to-Peer Internet workshop series

https://tomeshnet.github.io/p2p-internet-workshop/

Creative Commons Attribution Share Alike 4.0 International

99 stars 17 forks source link

Include PowerShell instructions for SSH on Windows / SSH worksheet #74

Open Shrinks99 opened 5 years ago

Shrinks99 commented 5 years ago

PUTTY is nice and all but Windows PowerShell includes SSH and works out of the box on all Windows 8+ machines. If we change this Windows users will follow the exact same steps as Mac & Linux users and won't have to install anything to access the Pis.

darkdrgn2k commented 5 years ago

Microsoft announced it was bringing an integrated OpenSSH client to Windows in 2015. They’ve finally done it, and an SSH client is hidden in Windows 10’s Fall Creators Update. You can now connect to an Secure Shell server from Windows without installing PuTTY or any other third-party software.

Update: The built-in SSH client is now enabled by default in Windows 10’s April 2018 Update. Here’s how to get the update if you don’t already have it on your PC.

PuTTY may still have more features. According to the project’s bug tracker on GitHub, the integrated SSH client only supports ed25519 keys at the moment.

So updated Windows 10+ not 8

And ciphers seem to be missing missing

Putty on the other hand is a self-contained executable.

Shrinks99 commented 5 years ago

I like the ability to have have as much parity between operating systems as possible for the instructions, the real question here is should we officially deprecate pre-Windows 10 machines here (and leave it up to the instructor to know what to do)?

I think it's decently fair to assume that if you're running Windows 10 it is updated to the point where it has SSH however according to this website 53% of people are running Windows 10 with 36% on Windows 7 globally. The ciphers don't seem to be a problem for this scenario as Ryan was able to log in using PowerShell tonight without any problems.

darkdrgn2k commented 5 years ago

Parity was initially proposed with git but struck down (granted it required additional installation) https://github.com/tomeshnet/p2p-internet-workshop/pull/28#discussion_r179878766
Windows "features" is a finicky beast and you cannot rely on them being installed especially on none-owned machines that do not have admin privileges. Putty is the fastest way to get some one ssh on their computer without the need of "inner workings".
I would "wait and see" how ssh integration with windows develops over time. IE dont mess with something that works when we have so little data.

Last i'm saying on the subject.
Do with it what you will.

Shrinks99 commented 5 years ago

Yeah based on the concerns presented by you(@darkdrgn2k) and @dcwalk in the chat I don't think it should be removed outright. That said, I still think it could be added with PUTTY mentioned below to support older systems in order to streamline the in-class instructional process.

benhylau commented 5 years ago

I think it is reasonable to have PowerShell, then PUTTY instructions below it, because having to instruct someone to install PUTTY is an extra burden on the facilitators. For example, at conferences we are often running this with only 1 or 2 facilitators for a large group, having PowerShell would let most Windows users move on without help.

As mentioned in chat, we can probably move the SSH stuff into its own sheet.

Shrinks99 commented 5 years ago

Along with SSH instructions this sheet also serves as a general jargon document with a section that allows participants to write in their own notes.