Skip to content

About

Sign in to a Windows machine over ssh with the keys already on your GitHub profile.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

Windows SSH Setup

Sign in to a Windows machine over ssh with the keys already on your GitHub profile.

License: MPL-2.0 Sponsor thehale on GitHub Joseph Hale's software engineering blog Follow Joseph Hale on LinkedIn

Quickstart

Run this in PowerShell on the Windows machine:

& ([scriptblock]::Create((irm https://raw.githubusercontent.com/thehale/windows-ssh-setup/main/windows-ssh-setup.ps1)))

It asks for your GitHub username, and for administrator approval when it needs it.

What you get

  • The OpenSSH Server that ships with Windows, switched on to start with Windows. It accepts your GitHub keys, never passwords, and only from your local network.
  • Sessions that open in Git Bash, so commands run as they would on a Mac or Linux machine.

Run it again after adding or revoking a key on GitHub, and the machine follows.

License

Copyright (c) 2026 Joseph Hale, All Rights Reserved

Provided under the terms of the Mozilla Public License, version 2.0

What does the MPL-2.0 license allow/require?

TL;DR

You can use files from this project in both open source and proprietary applications, provided you include the above attribution. However, if you modify any code in this project, or copy blocks of it into your own code, you must publicly share the resulting files (note, not your whole program) under the MPL-2.0. The best way to do this is via a Pull Request back into this project.

If you have any other questions, you may also find Mozilla's official FAQ for the MPL-2.0 license insightful.

If you dislike this license, you can contact me about negotiating a paid contract with different terms.

Disclaimer: This TL;DR is just a summary. All legal questions regarding usage of this project must be handled according to the official terms specified in the LICENSE file.

Why the MPL-2.0 license?

I believe that an open-source software license should ensure that code can be used everywhere.

Strict copyleft licenses, like the GPL family of licenses, fail to fulfill that vision because they only permit code to be used in other GPL-licensed projects. Permissive licenses, like the MIT and Apache licenses, allow code to be used everywhere but fail to prevent proprietary or GPL-licensed projects from limiting access to any improvements they make.

In contrast, the MPL-2.0 license allows code to be used in any software project, while ensuring that any improvements remain available for everyone.

About

Sign in to a Windows machine over ssh with the keys already on your GitHub profile.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages