From mattias.ellert at physics.uu.se  Thu Jul 11 11:25:36 2024
From: mattias.ellert at physics.uu.se (Mattias Ellert)
Date: Thu, 11 Jul 2024 11:25:36 +0200
Subject: [Discuss] GSISSH Maintainer?
In-Reply-To: <89e5160f-ed26-4bc9-a8c9-cb8afd0a0e1a@psc.edu>
References: <89e5160f-ed26-4bc9-a8c9-cb8afd0a0e1a@psc.edu>
Message-ID: <3c376417e615112ccf58e3eb944d6e4c517355e0.camel@physics.uu.se>

tor 2024-05-09 klockan 16:47 -0400 skrev Chris Rapier via discuss:
> 
> Hi,
> 
> I was hoping to contact the GSISSH maintainer. I am the developer of
> HPN-SSH which is part of GSISSH and I'd like to ask the maintainer a
> couple of questions. Specifically, I was contacted by a government
> user
> and they seem to be having some performance issues. This issue might
> be
> because of the version of HPN-SSH that's been incorporated. So I
> wanted
> to ask what version is being used and to see if I can do anything to
> help incorporate the latest version.
> 
> Thanks,
> 
> Chris Rapier
> _______________________________________________
> discuss mailing list
> discuss at gridcf.org
> https://mailman.egi.eu/mailman/listinfo/discuss

Hi Chris.

Sorry for not answering in a timely manner.

In the versions of gsi-openssh I maintain in Fedora and EPEL, I have
based them on the versions of openssh that are available in these
distributions applying the same patches, and then put additional
patches on top of that. The reason for this is to try not to introduce
issues that are not present in the default versions in the
distributions.

I have submitted updates to the packages, that are available in fedora-
updates-testing and epel-testing based on the latest tags in the git
repository based on each of the base versions in each distribution.

I am not a fan of the test in the client for the server version and
then changing the name of the scp command sent according to the test.
This seems to be a major source of incompatibility problems between
different versions.

An idea I had, but did not test yet, so it might not be a working
solution: Would it be possible to on the server create a directory e.g.
/usr/libexec/<some-name>/bin that contain a symbolic link scp pointing
the the renamed scp binary in /usr/bin, and then change the configure
options

--with-default-path=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin
--with-superuser-
path=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin\

to include this directory first in the paths. Then the selection of the
scp binary would be handled on the server side, and the client wouldn't
have to guess so much.

Mattias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4513 bytes
Desc: not available
URL: <http://mailman.egi.eu/pipermail/discuss/attachments/20240711/cf046aad/attachment.p7s>