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

tsh for Windows #2128

Merged
merged 10 commits into from
Aug 3, 2018
Merged

tsh for Windows #2128

merged 10 commits into from
Aug 3, 2018

Conversation

russjones
Copy link
Contributor

@russjones russjones commented Jul 31, 2018

Purpose

This PR builds upon #1996 submitted by @spectrumjade to add support for building tsh on Windows.

Implementation

  • tsh on Windows always has a nil caching policy.
  • Connections to ssh-agent are established over a Unix socket for Linux and macOS and a named pipe for Windows.
  • On Windows only a certificate (with an embedded private key) is loaded into ssh-agent. On Linux and macOS both certificate (with an embedded private key) and private key are loaded.
  • When tsh is in debug mode, logs no longer go to syslog, instead go to stderr.
  • The ssh, join, play, scp, and bench subcommands are hidden on Windows.
  • Updated the Makefile to build tsh for Windows with make release OS=windows.

Related Issues

Fixes #2114
Fixes #1996

@russjones russjones changed the title Rjones/tsh windows tsh for Windows Jul 31, 2018
@russjones russjones requested a review from klizhentas July 31, 2018 00:38
@russjones russjones force-pushed the rjones/tsh-windows branch 4 times, most recently from 30c1675 to 7e83e6e Compare August 1, 2018 19:39
@russjones russjones force-pushed the rjones/tsh-windows branch from 149f9e3 to ec13acd Compare August 3, 2018 17:58
@russjones russjones merged commit 7964641 into master Aug 3, 2018
@russjones russjones deleted the rjones/tsh-windows branch August 3, 2018 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants