Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

We're going to sell our product, based on slackware linux.
It runs several daemons, also OPENSSH.

We would like to know, if it is possible to change the OPENSSH version
in the source to 'ourproduct ssh daemon 1.0' for example, and sell it.
We can name it as ourproduct-sshd-1.0 for example. Is that allowed?

What should we do more? I would like to have some answers on this. I'm
not good in English, i hope the anyone can help us.

We hope for a fast feedback.

Thanks for support!

Kind regards,


Re: Commercialisation

Quoted text here. Click to load it

Short answer: probably yes, read the LICENSE file and ask your lawyer.

What you're describing is pretty much what Sun did when they forked
OpenSSH into SunSSH, see:

Quoted text here. Click to load it

It would probably be a good idea to acknowledge that it's based on

Darren Tucker (dtucker at
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Re: Commercialisation

Darren Tucker wrote:
Quoted text here. Click to load it

As an aside, I would really recommend you keep the "OpenSSH ..." at the
front, like what Debian does.  A number of other SSH clients and server
enable/disable features and bug fixes based on what SSH peer they are
talking to.  Debian sends:

   SSH-1.99-OpenSSH_3.6.1p2 Debian 1:3.6.1p2-11

for it's identity string.   After the OpenSSH_<ver> part of the string,
I think you can put pretty much anything you want.  But removing the
OpenSSH part of this may cause interopability problems.

Pete Flugstad
Icon Labs

Quoted text here. Click to load it

Re: Commercialisation

Quoted text here. Click to load it

Don't if you don't have to. Pete Flugstad is right about adding some extra
*suffix* information being OK, but changing the primary versions and names
of things makes it very difficult for your own users to assess if they have
the appropriate versions of the software, especially for key handling and
configuring newer features like PrivSep.

Site Timeline