[Openvpn-devel] OpenVPN Licensing Issues

2004-09-14 Thread James Yonan
Open Letter to OpenVPN developers and users
---

This message is primarily directed at individuals who have submitted or plan
to submit source code patches to the OpenVPN project.

I've been considering various ways that the OpenVPN project might become
financially self-sustaining.  While this has been discussed in the past, the
discussion usually centered around donations.  I'd like to propose and invite
discussion on another potential fundraising method.

Hans Reiser (ReiserFS developer) and separately the MySQL project have
pioneered a dual-licensing scheme where the source code remains under the GPL
license, but can be alternatively licensed under a standard commercial license
that allows customers to modify the code or link with non-open-source code,
without being required to publish their changes.  Funding is generated by
selling commercial licenses to the same codebase which is available to the
general public under the GPL.  As Hans Reiser bemuses, the commercial license
amounts to "taxing money from those who can't convince their investors they
should share their code with us."

Being able to sell commercial licenses would bring badly needed funding into
the OpenVPN project to help with the increasing workload of maintainance,
support, etc., and ensure that OpenVPN continues to evolve in the direction of
becoming a universal open source VPN solution.  While most OpenVPN users would
continue to use the GPL license, an example of the type of user who might want
a commercial license would be someone who wants to sell a network appliance
which uses a modified version of OpenVPN as the security layer, and who wants
to keep their modifications proprietary.

Of course, if software is licensed under the GPL, only the copyright holder
for the software is legally entitled to dual-license under a different,
non-GPL license agreement.

Therefore, in order for a dual licensing scheme to work, anyone who has ever
submitted code to the OpenVPN source code would need to agree to the dual
licensing scheme, since their code might now be potentially licensed under a
commercial license (in addition to the GPL).

There are different forms in which this agreement can be legally stated:

Here is Hans Reiser's version:

http://namesys.com/legalese.html

I'd like to invite some discussion on this idea, and I'd especially like
feedback from past OpenVPN contributors as to whether this is something they
could agree to.

Best Regards,
James





[Openvpn-devel] Microsoft digital signature warning pop up windows

2004-09-14 Thread Russell Sutherland
When one installs the current OpenVPN .exe NSIS install
bundle on a WindowsXP or 2000 machine, a window pops
up during the installation process saying something
to the effect:

"Warning: this driver has not been signed/approved
 by Microsoft quality control blah blah blah"

I believe that a similar pop up messages occurs when
one trys to "run" the NSIS .exe file from a URL directly
rather than downloading it first.

Is there any intention from the OpenVPN developers to
"do the right thing" in order to remove these pops from
the installation procedure?

-- 
Russell P. Sutherland   Email: russ @ madhaus.cns.utoronto.ca
4 Bancroft Ave., Rm. 102Voice: +1.416.978.0470
University of Toronto   Fax:   +1.416.978.6620
Toronto, ON  M5S 1C1WWW:   http://madhaus.cns.utoronto.ca/~russ
CANADA



Re: [Openvpn-devel] Microsoft digital signature warning pop up windows

2004-09-14 Thread James Yonan
On Tue, 14 Sep 2004, Russell Sutherland wrote:

> When one installs the current OpenVPN .exe NSIS install
> bundle on a WindowsXP or 2000 machine, a window pops
> up during the installation process saying something
> to the effect:
> 
> "Warning: this driver has not been signed/approved
>  by Microsoft quality control blah blah blah"
> 
> I believe that a similar pop up messages occurs when
> one trys to "run" the NSIS .exe file from a URL directly
> rather than downloading it first.
> 
> Is there any intention from the OpenVPN developers to
> "do the right thing" in order to remove these pops from
> the installation procedure?

I think this warning dialog is new.  I've only seen it once, after 
installing XP SP2.  Does this mean that the warning dialog will always 
accompany software installs unless the code has been signed by MS?

James



Re: [Openvpn-devel] OpenVPN Licensing Issues

2004-09-14 Thread Thomas Glanzmann
Hello James,

> I'd like to invite some discussion on this idea, and I'd especially
> like feedback from past OpenVPN contributors as to whether this is
> something they could agree to.

I didn't submit that much code, but of course I would aggree to dual
licensing.

Honestly,
Thomas