sshnet / sshnet/SSH.NET

Support force pseudo-terminal allocation(the ssh -f option)

Open
#988 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
4.4k
Forks
993
Avg merge
9d 21h
Merged PRs (30d)
1

Description

public class SshCommand : IDisposable
{
    ......
    private readonly bool _forcePseudoTerminal;

    internal SshCommand(ISession session, string commandText, Encoding encoding, bool forcePseudoTerminal)
    {
        ......
        _forcePseudoTerminal = forcePseudoTerminal;
    }

    public IAsyncResult BeginExecute(AsyncCallback callback, object state)
    {
        ......
        _channel = CreateChannel();
        _channel.Open();
        if (_forcePseudoTerminal)
            _channel.SendPseudoTerminalRequest(string.Empty, 0, 0, 0, 0, null);
        _channel.SendExecRequest(CommandText);
        return _asyncResult;
    }
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating SshCommand, its constructor, BeginExecute, and CreateChannel, then inspect how SendPseudoTerminalRequest is exposed and tested. The issue's proposed flow indicates that a force-pseudo-terminal option should be carried into execution and trigger the request before SendExecRequest; done means the option is available and behaves accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.