All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: Advise request on adding a new SSH variant
Date: Mon, 26 Apr 2021 11:08:21 -0400	[thread overview]
Message-ID: <043101d73aae$026409b0$072c1d10$@nexbridge.com> (raw)

Hi Team,

I am getting a bunch of requests from my team (and customers) to make SSH
configuration easier on the NonStop platform. We are currently using a
wrapper script to drive the variant of SSH on the platform but that is not
convenient for many people. I would like to add an ssh.Variant called
"nonstopssh", or something like that, which takes a few extra parameters.
-Q (quiet), -Z (don't display the banner), -p port (obvious but typically
required), -S (a system process name). The code in connect.c looks pretty
straight forward, but I'm wondering about the best way to pass in a process
name (it would be something like "$ZSSHX" - usually an environment variable
"SSH2_PROCESS_NAME"). The program name for SSH, I assume, could come from
GIT_SSH_COMMAND (typically "/G/system/zssh/sshoss", or I could force it if
not supplied). I'm also wondering about controls for the -Q and -Z
parameters. Should I just use the environment for this and build up args or
is there a more appropriate way of managing these values?

Thanks in advance,
Randall

-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.



             reply	other threads:[~2021-04-26 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 15:08 Randall S. Becker [this message]
2021-05-04 14:45 ` Advise request on adding a new SSH variant Philip Oakley
2021-05-04 15:25   ` Randall S. Becker
2021-05-05  0:49   ` Junio C Hamano
2021-05-05  2:04     ` Randall S. Becker
2021-05-05 10:49     ` Philip Oakley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='043101d73aae$026409b0$072c1d10$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.