 |
 |
Articles / TULARC / Security / SSH - Secure Shell / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
6.3. I don't like the commercial aspects of ssh. |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Security / SSH - Secure Shell / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
6.3. I don't like the commercial aspects of ssh. |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the SSH - Secure Shell FAQ, by Thomas Koenig Thomas.Koenig@ciw.uni-karlsruhe.de with numerous contributions by others.
The protocols ssh uses are freely available. There are no
restrictions if anybody wants to write a version that is available
under different conditions and is interoperable with existing ssh
installations.
Ssh is also on the Internet Standards Track. This means that a
second, independent implementation is required.
You will have to be aware of patent (RSA, IDEA) and export control
issues before writing a second implementation.
Continue to:
|
|
|
|
 |
|