Changes between Version 4 and Version 5 of OpenSSH


Ignore:
Timestamp:
May 23, 2008, 12:28:26 AM (9 years ago)
Author:
jrollins
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenSSH

    v4 v5  
    5555== using OpenSSH as a system component ==
    5656
    57 The OpenSSH developers do not want to be library developers.  This is understandable, given the headaches involved with library maintenance.  They've been very careful to make sure that their toolset behaves in stable, standardized ways.  So if you want to use OpenSSH tools in a system you're creating, you'll have the better luck if you think about the OpenSSH portion of the system as its own individual processes, and consider how you can connect the other components of your system to stdin, stdout, and other sockets created by those processes.
     57The OpenSSH developers do not want to be library developers.  This is understandable, given the headaches involved with library maintenance.  They've been very careful to make sure that their toolset behaves in stable, standardized ways.  So if you want to use OpenSSH tools in a system you're creating, you'll have better luck if you think about the OpenSSH portion of the system as its own individual processes, and consider how you can connect the other components of your system to stdin, stdout, and other sockets created by those processes.
    5858
    5959This "please treat OpenSSH as an independent binary, not a library" model also has benefits when attempting to use the tool with other tools with different licenses.  Many licenses (such as the GPL) restrict what sorts of libraries you can link with and retain your rights under the license.  By using OpenSSH tools as separate programs, there is no linkages, and the consequences of the license do not trigger.