<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Mischa et al.,<br>
<br>
I think forking Mattias' version into the gridcf organization makes
sense for maintaining version control history.<br>
<br>
- Brian<br>
<br>
<div class="moz-cite-prefix">On 09/07/2018 07:31 AM, Mischa Salle
wrote:<br>
</div>
<blockquote type="cite" cite="mid:20180907123111.GI16229@nikhef.nl">
<pre wrap="">Hi Frank, others,
I think it's probably good to focus on the version maintained by
Mattias, but that's probably for Mattias to answer (-;
What we could do is host that version under <a class="moz-txt-link-freetext" href="https://github.com/gridcf">https://github.com/gridcf</a> or
alternatively adapt the current gridcf/gct version to the one maintained
by Mattias.
Concerning GSI-OpenSSH itself, I think it's use is not really in the
same situations as GridFTP clients are typically used: although you can
run quite some commands over GridFTP, it's not the same as SSH.
When transferring real™ data I would use GridFTP and certainly not
gsis{cp,ftp}. AFAIK (some) of the German supers use gsissh for
kickstarting access.
For the further future (don't remember whether I mentioned this before),
one could probably make a different patch based on the adapted OpenSSH
versions as shipped by RedHat and Debian, which have proper GSSAPI
support (i.e. not just Kerberos, those patches were pushed by the
Moonshot people which also requires a proper GSSAPI, and I think were
based on the GSI-OpenSSH patch). It probably still requires a patched
server, but might be able to use a stock client with just some extra
modules installed (if I'm not mistaken).
Cheers,
Mischa
On Thu, Sep 06, 2018 at 05:56:33PM +0200, Frank Scheiner wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
...and Christmas came in between...
I think we never really finished this discussion.
And recently the question about the status of GSI-OpenSSH came up in PRACE.
The GSI-OpenSSH repo on Github ([1]) is still based on OpenSSH 7.5p1 and no
commit has been made there since September 2017. Consequently the current
GCT still builds a source package for GSI-OpenSSH based on OpenSSH 7.5.p1
where OpenSSH 7.8p1 is already out.
[1]: <a class="moz-txt-link-freetext" href="https://github.com/globus/gsi-openssh">https://github.com/globus/gsi-openssh</a>
I'll try to summarize the points so far - please correct me if I'm wrong
somewhere:
* Trying to get the GSI patch upstream into OpenSSH is a lost cause. Same
for the other patches.
* The current version of GSI-OpenSSH "available from" the Globus Toolkit and
the current GCT is based on OpenSSH 7.5p1 and includes (1) the HPN patches,
(2) the iSSHD patches on top of the HPN patches, (3) the GSI patches on top
of the iSSHD patches and (4) the Fedora OpenSSL 1.1 support patch on top of
it all.
* The EPEL/Fedora versions of GSI-OpenSSH that Mattias maintains are based
on the OpenSSH versions used in the respective EPEL/Fedora release and
contain all of the above minus the HPN and iSSHD patches and minus the parts
of the GSI patch that are already included in the EPEL/Fedora versions of
OpenSSH.
* Jim proposed to focus on the EPEL/Fedora version(s) of Mattias
****
So what are the next steps?
Should we remove GSI-OpenSSH from the GCT? Although I personally consider
gsiscp and gsisftp (even with HPN patches) inferior to GridFTP clients, they
are certainly useful and users are usually already familiar with the non-GSI
versions.
Should we switch to Mattias' version(s)? But how can we include this, as the
development happens in Fedora I assume?
Where should we point users for the GSI-OpenSSH source and for support in
the future?
Cheers,
Frank
--
Frank Scheiner
High Performance Computing Center Stuttgart (HLRS)
Department Project User Management & Accounting
Email: <a class="moz-txt-link-abbreviated" href="mailto:scheiner@hlrs.de">scheiner@hlrs.de</a>
Phone: +49 711 685 68039
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<br>
</body>
</html>