[Info-vax] Viewing SSH users on VMS

[Arne Vajhøj]

On 7/27/2024 7:13 PM, Chris Townley wrote:
> On 28/07/2024 00:03, Arne Vajhøj wrote:
>> On 7/27/2024 6:36 PM, Lawrence D'Oliveiro wrote:
>>> On Sat, 27 Jul 2024 16:58:34 -0400, Arne Vajhøj wrote:
>>>> VSI obvious can and probably should add it to the VMS port.
>>>
>>> For “port” read “fork”.
>>>
>>> Unless these sorts of changes get accepted upstream, you end up with the
>>> burden of maintaining your own parallel version, and keeping up with
>>> upstream developments.
>>>
>>> Somehow, I don’t think they have the resources for that.
>>
>> For a product that is important security wise it makes
>> sense to keep up.
>>
>> And I don't think it should be that bad. 30 years ago one
>> would create and reapply diffs. Today I believe Git can handle
>> it.
> 
> It does worry me a bit that VSI are making their own versions of these 
> packages, rather than putting them back into the packages as VMS 
> variants, that they will maintain within the package. Surely that would 
> imply commitment to the package, as well as the platform

It makes sense for VSI to provide builds of something like
OpenSSH and ship with VMS. It is expected functionality
and "go get something from the internet" may not work well
for all VMS customers.

Ideally the VMS changes should be sent upstream so that VMS
is an out-of-the-box supported platform.

But there can be many reasons why that may not have happened.
Maybe VSI did not prioritize it. Maybe the upstream
project rejected the VMS changes.

My understanding is that VMS support and upstream projects
are not always easy. Sometimes it requires diplomacy at a
high level.

But VSI should definitely try.

Arne