Hello, This again, raises the modulation of openvpn project. *NOBODY* wants/needs to modify the driver, most people lacks the skills and interest. Usually people wants to patch openvpn userspace components.
The driver should come in its own .msi signed (msi + driver). OpenVPN installation should embed the driver msi within it. For signing OpenVPN, this should be optional, as Windows does not force it. I use osslsigncode[1] with patches[2][3] to allow signing using a cross compiler. Alon. [1] http://sourceforge.net/projects/osslsigncode/ [2] http://sourceforge.net/tracker/?func=detail&aid=3018894&group_id=129143&atid=713908 [3] http://sourceforge.net/tracker/?func=detail&aid=3018895&group_id=129143&atid=713908 On Fri, Nov 12, 2010 at 10:18 PM, Gert Doering <g...@greenie.muc.de> wrote: > > Hi, > > On Fri, Nov 12, 2010 at 05:50:19PM +0100, David Sommerseth wrote: > > If I've understood it correctly, this is related to signing the Windows > > TUN/TAP driver. So if you don't have a signing key/tool available, it > > is still possible to build the rest of OpenVPN. You might even manage > > to install the unsigned TUN/TAP driver with some tweaking. > > Isn't the openvpn.exe signed as well? > > gert > -- > USENET is *not* the non-clickable part of WWW! > //www.muc.de/~gert/ > Gert Doering - Munich, Germany g...@greenie.muc.de > fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel >
