* [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
@ 2009-04-08 0:58 Karl O. Pinc
2009-04-08 3:21 ` dave
` (2 more replies)
0 siblings, 3 replies; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 0:58 UTC (permalink / raw)
To: openvpn-devel
Hello,
What I really want is a Windows binary and whatever
else gets built, _not_ packaged in an installer, so I can build
my own installer. It would be nice if OpenVPN would
release such a binary. Absent that I'm forced to
drag out a Windows machine, torture myself
for hours with it, and pester you. :-)
(I want to make my own installer so I can, e.g., install
real keys and config files that use them. It seems
straightforward enough to script the keymaking
process and have that script also create an
installer. Obtaining the raw materials, a Windows
binary, turns out to involve helpings of the
pain that comes with MS Windows.)
I've followed the instructions in domake-win and am having serious
problems building OpenVPN on XP.
One issue is that cryptoapi.c works around a
problem where CryptAcquireCertificatePrivateKey
is missing from MinGW. However, I've installed
the latest stable MinGW, 5.1.4, and the function
is now in MinGW. So, I tried commenting out the
#ifdef __MINGW32_VERSION hacks in cryptoapi.c.
This seems to have worked. (So far)
But then I got bit by some strange windows problem:
http://forums.logitech.com/logitech/board/message?board.id=quickcam_software&message.id=897&nobounce
(MinGW is a cygwin fork.)
I get this even though I long ago uninstalled the
logitech quickcam software.
Now I get seemingly random segfaults and
very strange behavior, like running domake-win
and having it tell me there's no autoconf directory,
or that at least version 1.4 of m4 is required
even though it's installed, or getting random segfaults
while running the autoconf stuff at the top
of install-win32/makeopenvpn.
In other words XP seems totally borked.
I find that LVPrSrv program has risen from
the dead to haunt me. I may have finally gotten
rid of it.... For the moment the compile is working....
Now I get:
!define "SF_SELECTED" already defined!
Error in script "gen/nsi/openvpn.nsi" on line 264 -- aborting creation
process
This I imagine I can figure out.
If there happen to be recommended versions of all the
tools that are known to work together and avoid
all these problems, or anything else that makes
it "just work", please let me know.
Thank you for your time.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
P.S. If I can't have unpackaged Windows binaries
I would oh-so-love to have a cross-compiler
so I could compile for Windows on Linux. There
seems to be one for OpenSC that compiles OpenVPN.
http://www.opensc-project.org/build/browser/trunk/build
Perhaps OpenVPN could coordinate with them and
support cross-compiling? (Please, please, please.)
P.P.S. It is not clear from the domake-win instructions
that the process is supposed to be undertaken on a
MS Windows machine. A note in the instructions would
be helpful.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 0:58 [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP Karl O. Pinc
@ 2009-04-08 3:21 ` dave
2009-04-08 3:50 ` Karl O. Pinc
2009-04-08 5:03 ` Karl O. Pinc
2009-04-08 15:10 ` Karl O. Pinc
2 siblings, 1 reply; 23+ messages in thread
From: dave @ 2009-04-08 3:21 UTC (permalink / raw)
To: "'Karl O. Pinc'" <kop@
> -----Original Message-----
> From: Karl O. Pinc [mailto:kop@...1206...]
...
> What I really want is a Windows binary and whatever
> else gets built, _not_ packaged in an installer, so I can build
> my own installer. It would be nice if OpenVPN would
> release such a binary. Absent that I'm forced to
> drag out a Windows machine, torture myself
> for hours with it, and pester you. :-)
...
OK, low-tech, but...
When I used to package OpenVPN for Portable Apps, I used to just install
openvpn, and pluck what I wanted out of the Program Files\OpenVPN
directory.
I now have a MingW environment working, so I don't do that anymore (and
so I can patch if I want), but it worked in a pinch and may allow you to
get on with the business of focusing on creating your installer for now,
then one day you can return to the MingW if you want to.
-Dave
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 3:21 ` dave
@ 2009-04-08 3:50 ` Karl O. Pinc
0 siblings, 0 replies; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 3:50 UTC (permalink / raw)
To: dave <dev@; +Cc: openvpn-devel
On 04/07/2009 10:21:36 PM, dave wrote:
> > -----Original Message-----
> > From: Karl O. Pinc [mailto:kop@...1206...]
> ...
> > What I really want is a Windows binary and whatever
> > else gets built, _not_ packaged in an installer, so I can build
> > my own installer.
> OK, low-tech, but...
>
> When I used to package OpenVPN for Portable Apps, I used to just
> install
> openvpn, and pluck what I wanted out of the Program Files\OpenVPN
> directory.
I probably should have gone that route. Alas, I now have
a working build environment. ;-) The good part about this is that
the binaries and whatnot are all in the right place
so that the supplied nsis config works to build the
installer. I've got something to start from.
The bad part is that no matter the approach I'm
stuck having to use a Windows box. I don't trust 'em.
They most likely know it too and that's why
I have a hard time every time I touch one,
no matter how simple the task.
Good suggestion though. The same idea crossed my mind before
I started, but I thought "hey, how hard can it be?"
I guess now I know.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 0:58 [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP Karl O. Pinc
2009-04-08 3:21 ` dave
@ 2009-04-08 5:03 ` Karl O. Pinc
2009-04-08 12:58 ` dave
2009-04-08 15:10 ` Karl O. Pinc
2 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 5:03 UTC (permalink / raw)
To: openvpn-devel
On 04/07/2009 07:58:30 PM, Karl O. Pinc wrote:
> Hello,
>
> What I really want is a Windows binary and whatever
> else gets built, _not_ packaged in an installer, so I can build
> my own installer. It would be nice if OpenVPN would
> release such a binary.
I suspect that what I want is exactly what OpenVPN already has at
http://openvpn.net/prebuilt/. The problem is that it's not
labeled as such and does not seem to have the same "supported"
status as the rest of the downloads. It's something of
an afterthought to ease those who really need their own
build.
So I guess what I'm asking is for this build to be documented
and placed on the download page with the rest of the
official downloads. (Assuming I can just run
install-win32/buildinstaller and have an installer
produced.)
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 5:03 ` Karl O. Pinc
@ 2009-04-08 12:58 ` dave
2009-04-08 15:04 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: dave @ 2009-04-08 12:58 UTC (permalink / raw)
To: "'Karl O. Pinc'" <kop@
> -----Original Message-----
> From: Karl O. Pinc [mailto:kop@...1206...]
...
> I suspect that what I want is exactly what OpenVPN already has at
> http://openvpn.net/prebuilt/. The problem is that it's not
> labeled as such and does not seem to have the same "supported"
...
> So I guess what I'm asking is for this build to be documented
> and placed on the download page with the rest of the
> official downloads. (Assuming I can just run
> install-win32/buildinstaller and have an installer
> produced.)
...
I'm pretty sure you can setup MinGW to build on Linux, though I haven't.
Agreed on the binary tarball, but brace yourself: the source tarball is
not always up-to-date to the current version either. I've experienced
that many times when building for OpenWRT. If you really want the
current source or for a specific version you may have to pull from
repository.
-Dave
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 12:58 ` dave
@ 2009-04-08 15:04 ` Karl O. Pinc
2009-04-08 15:23 ` Matt Wilks
2009-04-08 22:46 ` Alon Bar-Lev
0 siblings, 2 replies; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 15:04 UTC (permalink / raw)
To: dave <dev@; +Cc: openvpn-devel
On 04/08/2009 07:58:12 AM, dave wrote:
> > -----Original Message-----
> > From: Karl O. Pinc [mailto:kop@...1206...]
> ...
> > I suspect that what I want is exactly what OpenVPN already has at
> > http://openvpn.net/prebuilt/. The problem is that it's not
> > labeled as such and does not seem to have the same "supported"
> ...
> > So I guess what I'm asking is for this build to be documented
> > and placed on the download page with the rest of the
> > official downloads. (Assuming I can just run
> > install-win32/buildinstaller and have an installer
> > produced.)
> ...
>
> I'm pretty sure you can setup MinGW to build on Linux, though I
> haven't.
Yeah. On Debian it just installs and seems to work. But there must
be more involved, somewhere, to have it go from source to nsis
installer. I say this because I thought the instructions would
enable me to cross compile, and so I installed the prerequisites
on Linux and gave it a go. The ./configure failed it's tests
for libraries, because of course the Windows libraries would
not run on Linux.
>
> Agreed on the binary tarball, but brace yourself: the source tarball
> is
> not always up-to-date to the current version either.
Well, if the developers grant my wish then it _would_ be current. :)
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 0:58 [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP Karl O. Pinc
2009-04-08 3:21 ` dave
2009-04-08 5:03 ` Karl O. Pinc
@ 2009-04-08 15:10 ` Karl O. Pinc
2 siblings, 0 replies; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 15:10 UTC (permalink / raw)
To: openvpn-devel
On 04/07/2009 07:58:30 PM, Karl O. Pinc wrote:
>
> One issue is that cryptoapi.c works around a
> problem where CryptAcquireCertificatePrivateKey
> is missing from MinGW. However, I've installed
> the latest stable MinGW, 5.1.4, and the function
> is now in MinGW. So, I tried commenting out the
> #ifdef __MINGW32_VERSION hacks in cryptoapi.c.
> This seems to have worked. (So far)
FYI, it does work.
FWIW, I'm thinking myself through the problem and
it occurs to me that the right way to do this
is somewhere in the autoconf related tools.
That way you can test and set a different
variable than __MINGW32_VERSION for the
#ifdefs to use, based on the value of __MINGW32_VERSION
and when the needed components were added.
I'm not competent enough in autoconf to make a patch.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 15:04 ` Karl O. Pinc
@ 2009-04-08 15:23 ` Matt Wilks
2009-04-08 17:02 ` Karl O. Pinc
2009-04-08 22:46 ` Alon Bar-Lev
1 sibling, 1 reply; 23+ messages in thread
From: Matt Wilks @ 2009-04-08 15:23 UTC (permalink / raw)
To: openvpn-devel
Karl O. Pinc wrote:
> On 04/08/2009 07:58:12 AM, dave wrote:
>
> Yeah. On Debian it just installs and seems to work. But there must
> be more involved, somewhere, to have it go from source to nsis
> installer.
Is there a specific reason you are attempting to build the OpenVPN .exe
(are you trying to make a custom executable)? You could just use a
compiled version (install in Windows, grab all the files), set up the
proper directory hierarchy and use NSIS to create a custom installer
package. The NSIS stuff works under Linux.
--
Matt Wilks Colossians 2:6-7
University of Toronto Computing and Networking Services
(416) 978-3328 matt@...273...
4 Bancroft Ave., Rm. 102 Toronto, ON M5S 1C1
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 15:23 ` Matt Wilks
@ 2009-04-08 17:02 ` Karl O. Pinc
2009-04-08 17:48 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 17:02 UTC (permalink / raw)
To: Matt Wilks <matt@; +Cc: openvpn-devel
On 04/08/2009 10:23:57 AM, Matt Wilks wrote:
> Karl O. Pinc wrote:
> > On 04/08/2009 07:58:12 AM, dave wrote:
> >
> > Yeah. On Debian it just installs and seems to work. But there must
> > be more involved, somewhere, to have it go from source to nsis
> > installer.
>
> Is there a specific reason you are attempting to build the OpenVPN
> .exe
> (are you trying to make a custom executable)? You could just use a
> compiled version (install in Windows, grab all the files), set up the
> proper directory hierarchy and use NSIS to create a custom installer
> package. The NSIS stuff works under Linux.
Thanks for the response.
No, I don't want a custom executable. I just want to make my
own Windows installer (on Linux).
I'm not certain that installing in Windows and grabbing all the files
will always work. For example there's an i386 and amd64
tapinstall.exe. Are they both always installed and then one run?
I can imagine similar issues surrounding what's installed and/or
run on various versions of MS Windows. I don't want to have
to have all combinations of Windows and hardware available
on which to do an install just to get the binaries. I don't know
the details of how the installer deals with the combination of
architectures and OS versions. (I don't really care
beyond what I'll have learn to modify the existing
installer for my purposes.) The point being I
don't want to rely on any particular installer implementation
or choice of packaging.
Equally important (for me) is that I don't want to rely
on having to have a (secured) Windows box -- on which to
do anything. In my case access to Windows is an inconvenience,
sometimes more, sometimes less of one but always a bother.
In any case I have a lot more trust in the security of
the OpenVPN build team's Windows boxes than I have in the security
of the Windows boxes to which I have access.
---
On an unrelated note I notice that building the 2.1 rc15
nsis installer on Linux for Windows gives me 3 warnings:
3 warnings:
install function "GetWindowsVersion" not referenced - zeroing code
(125-174) out
label "fileass" not used
label "tryaddtap" not used
I don't get the first when I build an installer on Windows.
(I do get the second 2 warnings.)
The first warning leaves me with an ungood feeling.
I will investigate.
If anyone would care to clue me in that'd be great. Otherwise
should I post a patch to this list if I figure it out?
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 17:02 ` Karl O. Pinc
@ 2009-04-08 17:48 ` Karl O. Pinc
0 siblings, 0 replies; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-08 17:48 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: Matt Wilks <matt@
I apologize for not starting a separate thread for this.
On 04/08/2009 12:02:00 PM, Karl O. Pinc wrote:
>
> On an unrelated note I notice that building the 2.1 rc15
> nsis installer on Linux for Windows gives me 3 warnings:
>
> 3 warnings:
> install function "GetWindowsVersion" not referenced - zeroing code
>
> (125-174) out
>
> label "fileass" not used
> label "tryaddtap" not used
>
> I don't get the first when I build an installer on Windows.
> (I do get the second 2 warnings.)
If I tar up the windows build tree and use that on Linux
to build the installer I don't get the first message.
So it seems I was doing something wrong.
As far as the last message goes, that's likely
because I've not downloaded the tap code
from Microsoft. (I found the instructions
in domake-win unclear on whether this is necessary
when using a pre-built environment.) In any
case I don't need the tap device so I'm not
going to worry about it.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 15:04 ` Karl O. Pinc
2009-04-08 15:23 ` Matt Wilks
@ 2009-04-08 22:46 ` Alon Bar-Lev
2009-04-09 3:03 ` Karl O. Pinc
1 sibling, 1 reply; 23+ messages in thread
From: Alon Bar-Lev @ 2009-04-08 22:46 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, dave <dev@
Available as part of OpenSC build [1].
[1] http://www.opensc-project.org/build
On Wed, Apr 8, 2009 at 6:04 PM, Karl O. Pinc <kop@...1206...> wrote:
>
> On 04/08/2009 07:58:12 AM, dave wrote:
>> > -----Original Message-----
>> > From: Karl O. Pinc [mailto:kop@...1206...]
>> ...
>> > I suspect that what I want is exactly what OpenVPN already has at
>> > http://openvpn.net/prebuilt/. The problem is that it's not
>> > labeled as such and does not seem to have the same "supported"
>> ...
>> > So I guess what I'm asking is for this build to be documented
>> > and placed on the download page with the rest of the
>> > official downloads. (Assuming I can just run
>> > install-win32/buildinstaller and have an installer
>> > produced.)
>> ...
>>
>> I'm pretty sure you can setup MinGW to build on Linux, though I
>> haven't.
>
> Yeah. On Debian it just installs and seems to work. But there must
> be more involved, somewhere, to have it go from source to nsis
> installer. I say this because I thought the instructions would
> enable me to cross compile, and so I installed the prerequisites
> on Linux and gave it a go. The ./configure failed it's tests
> for libraries, because of course the Windows libraries would
> not run on Linux.
>
>>
>> Agreed on the binary tarball, but brace yourself: the source tarball
>> is
>> not always up-to-date to the current version either.
>
> Well, if the developers grant my wish then it _would_ be current. :)
>
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-08 22:46 ` Alon Bar-Lev
@ 2009-04-09 3:03 ` Karl O. Pinc
2009-04-09 6:01 ` Alon Bar-Lev
2010-02-28 12:27 ` David Sommerseth
0 siblings, 2 replies; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-09 3:03 UTC (permalink / raw)
To: Alon Bar-Lev <alon.barlev@; +Cc: openvpn-devel, dave <dev@
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
It occurs to me that if I want to do more than
beg I should submit a patch, so one is attached.
On 04/08/2009 05:46:46 PM, Alon Bar-Lev wrote:
> Available as part of OpenSC build [1].
>
> [1] http://www.opensc-project.org/build
I noticed that. Does that build all of what
OpenVPN 2.1 packages for Windows, i.e. includes
OpenVPN GUI? The project does not seem to release
binaries for OpenVPN GUI, which is a requirement
for me.
I was also a little put off by:
"The OpenVPN overlay is provided in order to solve OpenSSL version
incompatibility between OpenSC and OpenVPN projects."
How can I make sure that I've got what OpenVPN is releasing
so that I can go to OpenVPN for support?
The OpenVPN devs have a "built" source tree in which they run
install-win32/buildinstaller. My point being that
if they would package it up
and release it alongside the resultant installer
none of these sorts of issues would ever come up.
Attached is a patch that produces a un-nsis-installer
windows binary release as part of the build process.
Apply it with:
cd openvpn
patch -p1 < buildbinaryrelease.patch
The result is a file named something like:
openvpn-2.1_rc15-winbinaries.tar.gz
I deliberately produce a tar.gz file
rather than a zip file to keep
Windows people from downloading it accidentally
instead of the Windows installer exe.
There is more work to be done. The file needs to
be signed and put on the website every time there's
a release. I don't see anything in svn to patch
that would aid this process.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
[-- Attachment #2: buildbinaryrelease.patch --]
[-- Type: text/x-patch, Size: 1300 bytes --]
diff -ruN openvpn-2.1_rc15/domake-win openvpn-2.1_rc15.patched/domake-win
--- openvpn-2.1_rc15/domake-win 2008-10-24 00:59:13.000000000 -0500
+++ openvpn-2.1_rc15.patched/domake-win 2009-04-08 20:59:10.000000000 -0500
@@ -133,6 +133,9 @@
# Produce the license text, install README, and sample config files
install-win32/maketext
+# Produce a binary release, not wrapped in an installer.
+install-win32/buildbinaryrelease
+
# This final step builds the OpenVPN installer using generated
# files from GENOUT
install-win32/buildinstaller
diff -ruN openvpn-2.1_rc15/install-win32/buildbinaryrelease openvpn-2.1_rc15.patched/install-win32/buildbinaryrelease
--- openvpn-2.1_rc15/install-win32/buildbinaryrelease 1969-12-31 18:00:00.000000000 -0600
+++ openvpn-2.1_rc15.patched/install-win32/buildbinaryrelease 2009-04-08 21:22:42.000000000 -0500
@@ -0,0 +1,16 @@
+#!/bin/sh
+
+# load version.nsi definitions
+. autodefs/defs.sh
+
+# Make a name for the binary release dir.
+RELEASEDIR="${PRODUCT_UNIX_NAME}-${PRODUCT_VERSION}${OUTFILE_LABEL}-winbinaries"
+
+# Copy the gen directory so it's got a good name
+cp -rp ${GENOUT} "${RELEASEDIR}"
+
+# Make the tarfile.
+tar -cf - "${RELEASEDIR}" | gzip -c > "${RELEASEDIR}.tar.gz"
+
+# Cleanup
+rm -rf "${RELEASEDIR}"
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-09 3:03 ` Karl O. Pinc
@ 2009-04-09 6:01 ` Alon Bar-Lev
2009-04-09 12:58 ` Karl O. Pinc
2010-02-28 12:27 ` David Sommerseth
1 sibling, 1 reply; 23+ messages in thread
From: Alon Bar-Lev @ 2009-04-09 6:01 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, dave <dev@
On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <kop@...1206...> wrote:
> It occurs to me that if I want to do more than
> beg I should submit a patch, so one is attached.
>
> On 04/08/2009 05:46:46 PM, Alon Bar-Lev wrote:
>>
>> Available as part of OpenSC build [1].
>>
>> [1] http://www.opensc-project.org/build
>
> I noticed that. Does that build all of what
> OpenVPN 2.1 packages for Windows, i.e. includes
> OpenVPN GUI? The project does not seem to release
> binaries for OpenVPN GUI, which is a requirement
> for me.
OpenVPN GUI is an application that is not part of OpenVPN.
The fact that it is provided within the same installer is a
mistake in my view.
It also does not working in many scenarios OpenVPN support
as it does not use the management interface.
The tap also is not provided as it also should have been provided
by a different package, as it is too being used by other projects,
such as coLinux.
> I was also a little put off by:
> "The OpenVPN overlay is provided in order to solve OpenSSL version
> incompatibility between OpenSC and OpenVPN projects."
> How can I make sure that I've got what OpenVPN is releasing
> so that I can go to OpenVPN for support?
As OpenSSL does not have stable ABI, compiling two projects with
different versions of OpenSSL, and loading the two into the same
process results in invalid behavior.
> The OpenVPN devs have a "built" source tree in which they run
> install-win32/buildinstaller. My point being that
> if they would package it up
> and release it alongside the resultant installer
> none of these sorts of issues would ever come up.
Wrong.
Alon.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-09 6:01 ` Alon Bar-Lev
@ 2009-04-09 12:58 ` Karl O. Pinc
2009-04-09 17:44 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-09 12:58 UTC (permalink / raw)
To: Alon Bar-Lev <alon.barlev@; +Cc: openvpn-devel, dave <dev@
On 04/09/2009 01:01:50 AM, Alon Bar-Lev wrote:
> On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <kop@...1206...> wrote:
> > It occurs to me that if I want to do more than
> > beg I should submit a patch, so one is attached.
> >
> > On 04/08/2009 05:46:46 PM, Alon Bar-Lev wrote:
> >>
> >> Available as part of OpenSC build [1].
> >>
> >> [1] http://www.opensc-project.org/build
> >
> > I noticed that. Does that build all of what
> > OpenVPN 2.1 packages for Windows, i.e. includes
> > OpenVPN GUI? The project does not seem to release
> > binaries for OpenVPN GUI, which is a requirement
> > for me.
>
> OpenVPN GUI is an application that is not part of OpenVPN.
> The fact that it is provided within the same installer is a
> mistake in my view.
> It also does not working in many scenarios OpenVPN support
> as it does not use the management interface.
>
> The tap also is not provided as it also should have been provided
> by a different package, as it is too being used by other projects,
> such as coLinux.
>
> > I was also a little put off by:
> > "The OpenVPN overlay is provided in order to solve OpenSSL version
> > incompatibility between OpenSC and OpenVPN projects."
> > How can I make sure that I've got what OpenVPN is releasing
> > so that I can go to OpenVPN for support?
>
> As OpenSSL does not have stable ABI, compiling two projects with
> different versions of OpenSSL, and loading the two into the same
> process results in invalid behavior.
>
> > The OpenVPN devs have a "built" source tree in which they run
> > install-win32/buildinstaller. My point being that
> > if they would package it up
> > and release it alongside the resultant installer
> > none of these sorts of issues would ever come up.
>
> Wrong.
Would you care to elaborate? AFAIK my patch produces
a directory structure from which it is easy to
produce an nsis installer containing OpenVPN provided
binaries, on any platform. The only prerequisite
is an NSIS install. You can therefore have an
installer that does not package OpenVPN GUI or tap
if you so choose.
# Untar
cd openvpn-2.1_rc15-winbinaries/
# Hack nsi/openvpn.nsi
makensis nsi/openvpn.nsi
(I actually gave a fully qualified path to makensis
when testing, but that was a bit long to include here.)
Naturally this does not address the issue of those
who want customized binaries, or the lack of a
stable ABI. I did not mean for what I wrote above to
make such claims. There is still a need for a
(cross) compiler to address broader issues.
My patch addresses the need of those who wish
to repackage the binaries made available by the
OpenVPN project for easy deployment
on Windows clients. I would think this addresses
a broad need. Anybody who's using certs to authorize
clients needs to distribute keys and config files that
use them. And many do not want to go to the trouble
of building their own binaries. Yet it makes sense
to put the keys and config files into an installer
along with the rest of the OpenVPN to make installation
as simple as possible for the end-user, avoid
unnecessary helpdesk calls, and mitigate all the other hassles
that come with supporting end users. The installer
could, for example, include help files that tell
the user what to click on connect to which
office. My patch addresses
the needs of what could be a rather large group,
those who don't want to compile but do want
to customize the end-user experience.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-09 12:58 ` Karl O. Pinc
@ 2009-04-09 17:44 ` Karl O. Pinc
2010-08-27 8:50 ` David Sommerseth
0 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2009-04-09 17:44 UTC (permalink / raw)
To: openvpn-devel; +Cc: Alon Bar-Lev <alon.barlev@
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On 04/09/2009 07:58:46 AM, Karl O. Pinc wrote:
>
> On 04/09/2009 01:01:50 AM, Alon Bar-Lev wrote:
> > On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <kop@...1206...> wrote:
> > > It occurs to me that if I want to do more than
> > > beg I should submit a patch, so one is attached.
It occurs to me that it's no good having an unpackaged
Windows binary archive without instructions regarding
how to use it.
Attached is a patch to INSTALL-win32.html that
documents how to make a custom Windows installer using
the archive produced by my previous patch.
I hope OpenVPN will consider these patches for inclusion.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
[-- Attachment #2: INSTALL-win32.html.patch --]
[-- Type: text/x-patch, Size: 3584 bytes --]
--- INSTALL-win32.html 2005-10-18 03:46:47.000000000 -0500
+++ INSTALL-win32.html.patched 2009-04-09 12:38:59.000000000 -0500
@@ -829,6 +829,87 @@
<hr />
+<h2>Notes -- Customizing the Windows installer</h2>
+
+<p><em>This section is for advanced administrators only.</em> The
+recommended approach is to first configure and test your VPN and
+customize the installer only after you have a working
+configuration.</p>
+
+<p>Administrators deploying OpenVPN on Windows may wish to customize
+the Windows installer in a site-specific manner. Certificates,
+configurations, help files and the like can be included in the
+customized installer to provide a single installer, or an installer
+per-client, that installs everything a site requires to run OpenVPN on
+a client.</p>
+
+<p>Note that an MS Windows machine is <em>not</em> a requirement.</p>
+
+<p>Administrators requiring further customization should see the
+section titled <a href="INSTALL-win32.html#building">Building from
+source</a>.</p>
+
+<p>You will need the following:</p>
+
+<ol>
+ <li>The OpenVPN unpackaged Windows binaries from the <a href="http://openvpn.net/index.php/downloads.html">OpenVPN Download</a> page.</li>
+
+ <li>Nullsoft Install System<br />
+ <a href="http://www.nullsoft.com/free/nsis/">http://www.nullsoft.com/free/nsis/</a></li>
+</ol>
+
+<p>To make a custom installer use the NSIS installer compiler:</p>
+
+<ol>
+ <li>Unpack the OpenVPN unpackaged windows binaries. The
+ result should be a directory, the unpacked OpenVPN binary
+ directory. This directory should have subdirectories.</li>
+
+ <li>Using Internet Explorer (TM) navigate to the
+ <code>nsi</code> subdirectory of the unpacked OpenVPN binary
+ directory.
+
+ <li>Right click on the icon labeled <code>openvpn</code> and
+ select "Compile NSIS script". Un*x users can use the
+ <code>makensis openvpn.nsi</code> command.</li>
+</ol>
+
+<p>The result should be a Windows installer in the OpenVPN binary
+directory.</p>
+
+<p>A simple customization is to install a configuration file and a
+certificate authority certificate whenever OpenVPN is installed as a
+service. To do this:</p>
+
+<ol>
+ <li>Put your CA certificate file (i.e. <code>ca.crt</code>)
+ into the <code>nsi</code> subdirectory of the unpacked
+ OpenVPN binary directory.</li>
+
+ <li>Put your configuration file
+ (i.e. <code>myserver.ovpn</code>) into the <code>nsi</code>
+ subdirectory of the unpacked OpenVPN binary directory. Your
+ configuration file should contain the line<br /><code>ca
+ ca.crt</code><br />to direct OpenVPN to your CA certificate.</li>
+
+ <li> Add the 2 lines:<br /><code>File
+ "myserver.ovpn"</code><br /><code>File "ca.crt"</code><br />
+ to the <code>nsi/openvpn.nsi</code> file at the bottom of
+ the section titled: <code>Section "${P`'RODUCT_NAME} Service"
+ SecService</code></li>
+</ol>
+
+<p>Note that putting your configuration and CA certificate files into
+the <code>nsi</code> subdirectory is not the most organized approach.
+It is simply the easiest way to get started with NSIS.</p>
+
+<p>For more information see <a
+href="http://nsis.sourceforge.net/Docs/"> the NSIS
+Documentation</a>.</p>
+
+<hr />
+
+<a name="building"></a>
<h2>Notes -- Building from source</h2>
<p><em>This section is for developers only.</em></p>
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-09 3:03 ` Karl O. Pinc
2009-04-09 6:01 ` Alon Bar-Lev
@ 2010-02-28 12:27 ` David Sommerseth
2010-03-01 3:48 ` Karl O. Pinc
1 sibling, 1 reply; 23+ messages in thread
From: David Sommerseth @ 2010-02-28 12:27 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel
[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/04/09 05:03, Karl O. Pinc wrote:
> It occurs to me that if I want to do more than
> beg I should submit a patch, so one is attached.
>
> On 04/08/2009 05:46:46 PM, Alon Bar-Lev wrote:
>> Available as part of OpenSC build [1].
>>
>> [1] http://www.opensc-project.org/build
>
> I noticed that. Does that build all of what
> OpenVPN 2.1 packages for Windows, i.e. includes
> OpenVPN GUI? The project does not seem to release
> binaries for OpenVPN GUI, which is a requirement
> for me.
>
> I was also a little put off by:
> "The OpenVPN overlay is provided in order to solve OpenSSL version
> incompatibility between OpenSC and OpenVPN projects."
> How can I make sure that I've got what OpenVPN is releasing
> so that I can go to OpenVPN for support?
>
> The OpenVPN devs have a "built" source tree in which they run
> install-win32/buildinstaller. My point being that
> if they would package it up
> and release it alongside the resultant installer
> none of these sorts of issues would ever come up.
>
> Attached is a patch that produces a un-nsis-installer
> windows binary release as part of the build process.
>
> Apply it with:
>
> cd openvpn
> patch -p1 < buildbinaryrelease.patch
>
> The result is a file named something like:
> openvpn-2.1_rc15-winbinaries.tar.gz
>
> I deliberately produce a tar.gz file
> rather than a zip file to keep
> Windows people from downloading it accidentally
> instead of the Windows installer exe.
>
> There is more work to be done. The file needs to
> be signed and put on the website every time there's
> a release. I don't see anything in svn to patch
> that would aid this process.
Hi!
I'm going through the mailing list, picking up patches which seems not
to be included. Is this patch still interesting to get included? This
one applies cleanly to the master branch.
I see that this patch is also followed by this one:
<http://article.gmane.org/gmane.network.openvpn.devel/2581>
This patch do not apply at all, as the standard checked out tree do not
have INSTALL-win32.html, only INSTALL-win32.txt. Is this correct? I
can't find this HTML file in the 2.1_rc15 nor 2.1_rc16, which was
current when this patch was sent to the mailing list.
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkuKYUoACgkQDC186MBRfrpVrACfWBX1kNPygMHKHea8gdSLeP+8
bVUAnj5G6Jo+WFW6ds74mi5h+S+fEnO4
=r1ZL
-----END PGP SIGNATURE-----
[-- Attachment #2: buildbinaryrelease.patch --]
[-- Type: text/x-patch, Size: 1266 bytes --]
diff -ruN openvpn-2.1_rc15/domake-win openvpn-2.1_rc15.patched/domake-win
--- openvpn-2.1_rc15/domake-win 2008-10-24 00:59:13.000000000 -0500
+++ openvpn-2.1_rc15.patched/domake-win 2009-04-08 20:59:10.000000000 -0500
@@ -133,6 +133,9 @@
# Produce the license text, install README, and sample config files
install-win32/maketext
+# Produce a binary release, not wrapped in an installer.
+install-win32/buildbinaryrelease
+
# This final step builds the OpenVPN installer using generated
# files from GENOUT
install-win32/buildinstaller
diff -ruN openvpn-2.1_rc15/install-win32/buildbinaryrelease openvpn-2.1_rc15.patched/install-win32/buildbinaryrelease
--- openvpn-2.1_rc15/install-win32/buildbinaryrelease 1969-12-31 18:00:00.000000000 -0600
+++ openvpn-2.1_rc15.patched/install-win32/buildbinaryrelease 2009-04-08 21:22:42.000000000 -0500
@@ -0,0 +1,16 @@
+#!/bin/sh
+
+# load version.nsi definitions
+. autodefs/defs.sh
+
+# Make a name for the binary release dir.
+RELEASEDIR="${PRODUCT_UNIX_NAME}-${PRODUCT_VERSION}${OUTFILE_LABEL}-winbinaries"
+
+# Copy the gen directory so it's got a good name
+cp -rp ${GENOUT} "${RELEASEDIR}"
+
+# Make the tarfile.
+tar -cf - "${RELEASEDIR}" | gzip -c > "${RELEASEDIR}.tar.gz"
+
+# Cleanup
+rm -rf "${RELEASEDIR}"
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2010-02-28 12:27 ` David Sommerseth
@ 2010-03-01 3:48 ` Karl O. Pinc
2010-04-01 15:19 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2010-03-01 3:48 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: openvpn-devel
On 02/28/2010 06:27:54 AM, David Sommerseth wrote:
> On 09/04/09 05:03, Karl O. Pinc wrote:
<snip>
> > The OpenVPN devs have a "built" source tree in which they run
> > install-win32/buildinstaller. My point being that
> > if they would package it up
> > and release it alongside the resultant installer
> > none of these sorts of issues would ever come up.
> >
> > Attached is a patch that produces a un-nsis-installer
> > windows binary release as part of the build process.
> >
> > Apply it with:
> >
> > cd openvpn
> > patch -p1 < buildbinaryrelease.patch
> >
> > The result is a file named something like:
> > openvpn-2.1_rc15-winbinaries.tar.gz
> >
> > I deliberately produce a tar.gz file
> > rather than a zip file to keep
> > Windows people from downloading it accidentally
> > instead of the Windows installer exe.
> >
> > There is more work to be done. The file needs to
> > be signed and put on the website every time there's
> > a release. I don't see anything in svn to patch
> > that would aid this process.
>
> Hi!
>
> I'm going through the mailing list, picking up patches which seems
> not
> to be included. Is this patch still interesting to get included?
I would like to see it included.
The goal is to allow people to create
custom installers for MS Windows without having to rebuild
the source or cross compile. The point of the patch
is to support an "unpackaged" release of the MS Windows
binaries. In other words raw binaries that are not
part of an installer, which can then be packaged
using the nsis installer to produce a custom install.
As noted above this means that the official OpenVPN project
would have to actually release such binaries. If the
project does not want to do this there is no point in
having the patch.
So, this requires upstream approval. In some ways this
is no different from other patches, except that it requires
ongoing work as new releases come out -- or if not that
then a change to whatever automated process (unavailable to
us, at least at the time the patch was written) that puts
releases out to the public.
> This
> one applies cleanly to the master branch.
>
> I see that this patch is also followed by this one:
>
> <http://article.gmane.org/gmane.network.openvpn.devel/2581>
Yes. The second patch is to the documentation so that people
know what to do with unpackaged MS Windows binaries. Not
much point in releasing the binaries unless there's documentation.
>
> This patch do not apply at all, as the standard checked out tree do
> not
> have INSTALL-win32.html, only INSTALL-win32.txt. Is this correct? I
> can't find this HTML file in the 2.1_rc15 nor 2.1_rc16, which was
> current when this patch was sent to the mailing list.
The OpenVPN site has restructured since this patch was written.
I'd be happy to redo the documentation patch, but I don't see
any point in doing so without some assurance that the effort
will not be wasted. How can I get some feedback on this?
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2010-03-01 3:48 ` Karl O. Pinc
@ 2010-04-01 15:19 ` Karl O. Pinc
2010-04-20 0:09 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2010-04-01 15:19 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel
So, what is the status of this patch? Would Openvpn
release "unpackaged" MS Windows binaries? If so
you can apply the code patch and I'll rework the
documentation patch into where ever the documentation
currently exists.
On 02/28/2010 09:48:46 PM, Karl O. Pinc wrote:
> On 02/28/2010 06:27:54 AM, David Sommerseth wrote:
> > On 09/04/09 05:03, Karl O. Pinc wrote:
>
> <snip>
>
> > > The OpenVPN devs have a "built" source tree in which they run
> > > install-win32/buildinstaller. My point being that
> > > if they would package it up
> > > and release it alongside the resultant installer
> > > none of these sorts of issues would ever come up.
> > >
> > > Attached is a patch that produces a un-nsis-installer
> > > windows binary release as part of the build process.
> > >
> > > Apply it with:
> > >
> > > cd openvpn
> > > patch -p1 < buildbinaryrelease.patch
> > >
> > > The result is a file named something like:
> > > openvpn-2.1_rc15-winbinaries.tar.gz
> > >
> > > I deliberately produce a tar.gz file
> > > rather than a zip file to keep
> > > Windows people from downloading it accidentally
> > > instead of the Windows installer exe.
> > >
> > > There is more work to be done. The file needs to
> > > be signed and put on the website every time there's
> > > a release. I don't see anything in svn to patch
> > > that would aid this process.
> >
> > Hi!
> >
> > I'm going through the mailing list, picking up patches which seems
> > not
> > to be included. Is this patch still interesting to get included?
>
> I would like to see it included.
>
> The goal is to allow people to create
> custom installers for MS Windows without having to rebuild
> the source or cross compile. The point of the patch
> is to support an "unpackaged" release of the MS Windows
> binaries. In other words raw binaries that are not
> part of an installer, which can then be packaged
> using the nsis installer to produce a custom install.
>
> As noted above this means that the official OpenVPN project
> would have to actually release such binaries. If the
> project does not want to do this there is no point in
> having the patch.
>
> So, this requires upstream approval. In some ways this
> is no different from other patches, except that it requires
> ongoing work as new releases come out -- or if not that
> then a change to whatever automated process (unavailable to
> us, at least at the time the patch was written) that puts
> releases out to the public.
>
> > This
> > one applies cleanly to the master branch.
> >
> > I see that this patch is also followed by this one:
> >
> > <http://article.gmane.org/gmane.network.openvpn.devel/2581>
>
> Yes. The second patch is to the documentation so that people
> know what to do with unpackaged MS Windows binaries. Not
> much point in releasing the binaries unless there's documentation.
>
> >
> > This patch do not apply at all, as the standard checked out tree do
> > not
> > have INSTALL-win32.html, only INSTALL-win32.txt. Is this correct?
> I
> > can't find this HTML file in the 2.1_rc15 nor 2.1_rc16, which was
> > current when this patch was sent to the mailing list.
>
> The OpenVPN site has restructured since this patch was written.
>
> I'd be happy to redo the documentation patch, but I don't see
> any point in doing so without some assurance that the effort
> will not be wasted. How can I get some feedback on this?
>
> Regards,
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>
>
>
>
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2010-04-01 15:19 ` Karl O. Pinc
@ 2010-04-20 0:09 ` Karl O. Pinc
0 siblings, 0 replies; 23+ messages in thread
From: Karl O. Pinc @ 2010-04-20 0:09 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel
Hello,
What's happening with this patch? Does OpenVPN
want it?
On 04/01/2010 10:19:01 AM, Karl O. Pinc wrote:
> So, what is the status of this patch? Would Openvpn
> release "unpackaged" MS Windows binaries? If so
> you can apply the code patch and I'll rework the
> documentation patch into where ever the documentation
> currently exists.
>
> On 02/28/2010 09:48:46 PM, Karl O. Pinc wrote:
> > On 02/28/2010 06:27:54 AM, David Sommerseth wrote:
> > > On 09/04/09 05:03, Karl O. Pinc wrote:
> >
> > <snip>
> >
> > > > The OpenVPN devs have a "built" source tree in which they run
> > > > install-win32/buildinstaller. My point being that
> > > > if they would package it up
> > > > and release it alongside the resultant installer
> > > > none of these sorts of issues would ever come up.
> > > >
> > > > Attached is a patch that produces a un-nsis-installer
> > > > windows binary release as part of the build process.
> > > >
> > > > Apply it with:
> > > >
> > > > cd openvpn
> > > > patch -p1 < buildbinaryrelease.patch
> > > >
> > > > The result is a file named something like:
> > > > openvpn-2.1_rc15-winbinaries.tar.gz
> > > >
> > > > I deliberately produce a tar.gz file
> > > > rather than a zip file to keep
> > > > Windows people from downloading it accidentally
> > > > instead of the Windows installer exe.
> > > >
> > > > There is more work to be done. The file needs to
> > > > be signed and put on the website every time there's
> > > > a release. I don't see anything in svn to patch
> > > > that would aid this process.
> > >
> > > Hi!
> > >
> > > I'm going through the mailing list, picking up patches which
> seems
>
> > > not
> > > to be included. Is this patch still interesting to get included?
> >
> > I would like to see it included.
> >
> > The goal is to allow people to create
> > custom installers for MS Windows without having to rebuild
> > the source or cross compile. The point of the patch
> > is to support an "unpackaged" release of the MS Windows
> > binaries. In other words raw binaries that are not
> > part of an installer, which can then be packaged
> > using the nsis installer to produce a custom install.
> >
> > As noted above this means that the official OpenVPN project
> > would have to actually release such binaries. If the
> > project does not want to do this there is no point in
> > having the patch.
> >
> > So, this requires upstream approval. In some ways this
> > is no different from other patches, except that it requires
> > ongoing work as new releases come out -- or if not that
> > then a change to whatever automated process (unavailable to
> > us, at least at the time the patch was written) that puts
> > releases out to the public.
> >
> > > This
> > > one applies cleanly to the master branch.
> > >
> > > I see that this patch is also followed by this one:
> > >
> > > <http://article.gmane.org/gmane.network.openvpn.devel/2581>
> >
> > Yes. The second patch is to the documentation so that people
> > know what to do with unpackaged MS Windows binaries. Not
> > much point in releasing the binaries unless there's documentation.
> >
> > >
> > > This patch do not apply at all, as the standard checked out tree
> do
> > > not
> > > have INSTALL-win32.html, only INSTALL-win32.txt. Is this
> correct?
>
> > I
> > > can't find this HTML file in the 2.1_rc15 nor 2.1_rc16, which was
> > > current when this patch was sent to the mailing list.
> >
> > The OpenVPN site has restructured since this patch was written.
> >
> > I'd be happy to redo the documentation patch, but I don't see
> > any point in doing so without some assurance that the effort
> > will not be wasted. How can I get some feedback on this?
> >
> > Regards,
> >
> > Karl <kop@...1206...>
> > Free Software: "You don't pay back, you pay forward."
> > -- Robert A. Heinlein
> >
> >
> >
> ------------------------------------------------------------------------------
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Openvpn-devel mailing list
> > Openvpn-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/openvpn-devel
> >
> >
> >
> >
>
>
>
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
>
>
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2009-04-09 17:44 ` Karl O. Pinc
@ 2010-08-27 8:50 ` David Sommerseth
2010-08-27 14:20 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: David Sommerseth @ 2010-08-27 8:50 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: Openvpn-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/04/09 19:44, Karl O. Pinc wrote:
>
> On 04/09/2009 07:58:46 AM, Karl O. Pinc wrote:
>>
>> On 04/09/2009 01:01:50 AM, Alon Bar-Lev wrote:
>> > On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <kop@...1206...> wrote:
>> > > It occurs to me that if I want to do more than
>> > > beg I should submit a patch, so one is attached.
Sorry it has taken way too long time to get this one reviewed. It's
just been quite a lot to do, and this was not considered critical enough.
> It occurs to me that it's no good having an unpackaged
> Windows binary archive without instructions regarding
> how to use it.
Agreed!
> Attached is a patch to INSTALL-win32.html that
> documents how to make a custom Windows installer using
> the archive produced by my previous patch.
>
> I hope OpenVPN will consider these patches for inclusion.
Review follows below.
- --- INSTALL-win32.html 2005-10-18 03:46:47.000000000 -0500
+++ INSTALL-win32.html.patched 2009-04-09 12:38:59.000000000 -0500
^^^^^^^^^^^^^^^^^^
This is not a file which is available directly in the source tree. It
is in best case generated somehow. How that is done, I have no idea
(I'm not using Windows platform for development). However, there is a
INSTALL-win32.txt file - the patch should really be against that file -
and without the HTML mark-ups. Please do so against the git tree,
preferably the feat_misc or master branch.
[...snip...]
+<p>Note that an MS Windows machine is <em>not</em> a requirement.</p>
Why so? If I've understood you correctly, if having the needed windows
binaries available, you just rebuild the NSIS installer. This should be
possible to do also in Linux or *BSD.
"Portable Compiler
The NSIS compiler can be compiled for POSIX platforms
like Linux and *BSD. Generated installer will still
run on Windows only, but this way they can be
generated without Windows or WINE."
<http://nsis.sourceforge.net/Features#Portable_Compiler>
[...snip...]
+ <li>Nullsoft Install System<br />
+ <a
href="http://www.nullsoft.com/free/nsis/">http://www.nullsoft.com/free/nsis/</a></li>
This redirects to: http://nsis.sourceforge.net/Main_Page
[...snip...]
+ <li>Unpack the OpenVPN unpackaged windows binaries. The
+ result should be a directory, the unpacked OpenVPN binary
+ directory. This directory should have subdirectories.</li>
Confusing sentences ... a lot of unpacked unpacked binaries unpacked.
+
+ <li>Using Internet Explorer (TM) navigate to the
+ <code>nsi</code> subdirectory of the unpacked OpenVPN binary
+ directory.
Using "Internet Explorer"?!? Why not "Using the file browser ..."?
+ <li>Right click on the icon labeled <code>openvpn</code> and
+ select "Compile NSIS script". Un*x users can use the
+ <code>makensis openvpn.nsi</code> command.</li>
+</ol>
Okay, here you have the cross-platform stuff. I'd probably prefer to
state "Linux or *BSD users", as that is the supported platforms by NSIS.
[...snip...]
+ <li> Add the 2 lines:<br /><code>File
+ "myserver.ovpn"</code><br /><code>File "ca.crt"</code><br />
+ to the <code>nsi/openvpn.nsi</code> file at the bottom of
+ the section titled: <code>Section "${P`'RODUCT_NAME} Service"
^^^^^^^^^^^^^^^
Is this really correct?
+ SecService</code></li>
+</ol>
+
+<p>Note that putting your configuration and CA certificate files into
+the <code>nsi</code> subdirectory is not the most organized approach.
+It is simply the easiest way to get started with NSIS.</p>
What about to explain properly how to do it more organised? Most users
won't care, and when they learn the sloppy way - they will never improve
it if it works.
[...snip...]
Thank you once again for you patch and patience. If we can have these
things straightened up, I'm able to pull it into the git tree. As this
patch do not touch any code, we can pretty sure get this on into the 2.2
release. We're about to send out a beta release pretty soon, but this
patch have the possibility to get accepted into a later beta release.
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkx3fG0ACgkQDC186MBRfrqJPQCdFkQzJzGhh6O3+Jq5tBcOJjkk
zKkAn1CuXj5J9ke5xaZYKdbDG37x4O1p
=GeDb
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2010-08-27 8:50 ` David Sommerseth
@ 2010-08-27 14:20 ` Karl O. Pinc
2010-08-27 16:16 ` David Sommerseth
0 siblings, 1 reply; 23+ messages in thread
From: Karl O. Pinc @ 2010-08-27 14:20 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: Openvpn-devel
On 08/27/2010 03:50:55 AM, David Sommerseth wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/04/09 19:44, Karl O. Pinc wrote:
> >
> > On 04/09/2009 07:58:46 AM, Karl O. Pinc wrote:
> >>
> >> On 04/09/2009 01:01:50 AM, Alon Bar-Lev wrote:
> >> > On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <kop@...1206...>
> wrote:
> >> > > It occurs to me that if I want to do more than
> >> > > beg I should submit a patch, so one is attached.
>
> Sorry it has taken way too long time to get this one reviewed. It's
> just been quite a lot to do, and this was not considered critical
> enough.
>
> > It occurs to me that it's no good having an unpackaged
> > Windows binary archive without instructions regarding
> > how to use it.
>
> Agreed!
So, is it worth doing any work at all on this?
I have not had the time to add to the weekly irc meeting
agenda and advocate live. The arguments previously presented
in email cover the subject already.
>
> > Attached is a patch to INSTALL-win32.html that
> > documents how to make a custom Windows installer using
> > the archive produced by my previous patch.
> >
> > I hope OpenVPN will consider these patches for inclusion.
>
> Review follows below.
>
>
> - --- INSTALL-win32.html 2005-10-18 03:46:47.000000000 -0500
> +++ INSTALL-win32.html.patched 2009-04-09 12:38:59.000000000
> -0500
> ^^^^^^^^^^^^^^^^^^
>
> This is not a file which is available directly in the source tree.
> It
> is in best case generated somehow. How that is done, I have no idea
> (I'm not using Windows platform for development). However, there is
> a
> INSTALL-win32.txt file - the patch should really be against that file
> -
> and without the HTML mark-ups. Please do so against the git tree,
> preferably the feat_misc or master branch.
The file _was_ in the source tree, but is no longer. I will
find the appropriate new file.
>
> [...snip...]
>
> +<p>Note that an MS Windows machine is <em>not</em> a requirement.</
> p>
>
> Why so? If I've understood you correctly, if having the needed
> windows
> binaries available, you just rebuild the NSIS installer. This should
> be
> possible to do also in Linux or *BSD.
We are in agreement here. Did you miss the word "not" in the
sentence or is there some other vagueness in the wording?
> [...snip...]
>
> + <li>Nullsoft Install System<br />
> + <a
> href="http://www.nullsoft.com/free/nsis/">http://www.nullsoft.com/
> free/nsis/</a></li>
>
> This redirects to: http://nsis.sourceforge.net/Main_Page
Probably an a stale link.
>
> [...snip...]
>
> + <li>Unpack the OpenVPN unpackaged windows binaries. The
> + result should be a directory, the unpacked OpenVPN binary
> + directory. This directory should have subdirectories.</li>
>
> Confusing sentences ... a lot of unpacked unpacked binaries unpacked.
How about "Unpack the OpenVPN tar file. The result ..."?
> +
> + <li>Using Internet Explorer (TM) navigate to the
> + <code>nsi</code> subdirectory of the unpacked OpenVPN
> binary
> + directory.
>
> Using "Internet Explorer"?!? Why not "Using the file browser ..."?
I don't know. I'll look into it if we go farther.
>
> + <li>Right click on the icon labeled <code>openvpn</code>
> and
> + select "Compile NSIS script". Un*x users can use the
> + <code>makensis openvpn.nsi</code> command.</li>
> +</ol>
>
> Okay, here you have the cross-platform stuff. I'd probably prefer to
> state "Linux or *BSD users", as that is the supported platforms by
> NSIS.
Ok.
>
> [...snip...]
>
> + <li> Add the 2 lines:<br /><code>File
> + "myserver.ovpn"</code><br /><code>File "ca.crt"</code><br /
> >
> + to the <code>nsi/openvpn.nsi</code> file at the bottom of
> + the section titled: <code>Section "${P`'RODUCT_NAME}
> Service"
> ^^^^^^^^^^^^^^^
> Is this really correct?
Dunno. At one point I tested everything. This would include
in the new installer those files, which are what's needed to
run a openvpn client that validates the server with a certificate.
The point of the entire exercise being to create a single installer
that contains everything needed to run openvpn.
>
> + SecService</code></li>
> +</ol>
> +
> +<p>Note that putting your configuration and CA certificate files
> into
> +the <code>nsi</code> subdirectory is not the most organized
> approach.
> +It is simply the easiest way to get started with NSIS.</p>
>
> What about to explain properly how to do it more organised? Most
> users
> won't care, and when they learn the sloppy way - they will never
> improve
> it if it works.
There are probably multiple good ways to do the job. I can see
a quick mention of the options but past a certain point it's
all theory. I look at it this way; most users' won't read
the instructions anyway.
>
> [...snip...]
>
>
> Thank you once again for you patch and patience. If we can have
> these
> things straightened up, I'm able to pull it into the git tree. As
> this
> patch do not touch any code, we can pretty sure get this on into the
> 2.2
> release. We're about to send out a beta release pretty soon, but
> this
> patch have the possibility to get accepted into a later beta release.
Unfortunately you caught me at a bad time and I won't be able to work
on this for at least a couple of weeks and perhaps longer.
It's waited this long. May as well let it wait and be done right
when it gets done.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2010-08-27 14:20 ` Karl O. Pinc
@ 2010-08-27 16:16 ` David Sommerseth
2010-08-27 18:19 ` Karl O. Pinc
0 siblings, 1 reply; 23+ messages in thread
From: David Sommerseth @ 2010-08-27 16:16 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: Openvpn-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 27/08/10 16:20, Karl O. Pinc wrote:
> On 08/27/2010 03:50:55 AM, David Sommerseth wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 09/04/09 19:44, Karl O. Pinc wrote:
>>>
>>> On 04/09/2009 07:58:46 AM, Karl O. Pinc wrote:
>>>>
>>>> On 04/09/2009 01:01:50 AM, Alon Bar-Lev wrote:
>>>>> On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <kop@...1206...>
>> wrote:
>>>>>> It occurs to me that if I want to do more than
>>>>>> beg I should submit a patch, so one is attached.
>>
>> Sorry it has taken way too long time to get this one reviewed. It's
>> just been quite a lot to do, and this was not considered critical
>> enough.
>>
>>> It occurs to me that it's no good having an unpackaged
>>> Windows binary archive without instructions regarding
>>> how to use it.
>>
>> Agreed!
>
> So, is it worth doing any work at all on this?
> I have not had the time to add to the weekly irc meeting
> agenda and advocate live. The arguments previously presented
> in email cover the subject already.
No problem! I would say it makes sense to give some documentation how
to do this. And you've already done a great job here!
>>> Attached is a patch to INSTALL-win32.html that
>>> documents how to make a custom Windows installer using
>>> the archive produced by my previous patch.
>>>
>>> I hope OpenVPN will consider these patches for inclusion.
>>
>> Review follows below.
>>
>>
>> - --- INSTALL-win32.html 2005-10-18 03:46:47.000000000 -0500
>> +++ INSTALL-win32.html.patched 2009-04-09 12:38:59.000000000
>> -0500
>> ^^^^^^^^^^^^^^^^^^
>>
>> This is not a file which is available directly in the source tree.
>> It
>> is in best case generated somehow. How that is done, I have no idea
>> (I'm not using Windows platform for development). However, there is
>> a
>> INSTALL-win32.txt file - the patch should really be against that file
>> -
>> and without the HTML mark-ups. Please do so against the git tree,
>> preferably the feat_misc or master branch.
>
> The file _was_ in the source tree, but is no longer. I will
> find the appropriate new file.
Thanks a lot! I don't know how/when/why this changed, but that's
history. But thanks for fixing it!
>> [...snip...]
>>
>> +<p>Note that an MS Windows machine is <em>not</em> a requirement.</
>> p>
>>
>> Why so? If I've understood you correctly, if having the needed
>> windows
>> binaries available, you just rebuild the NSIS installer. This should
>> be
>> possible to do also in Linux or *BSD.
>
> We are in agreement here. Did you miss the word "not" in the
> sentence or is there some other vagueness in the wording?
Ahh ... Sorry! My mistake! I somehow was blind of the "not".
>> [...snip...]
>>
>> + <li>Nullsoft Install System<br />
>> + <a
>> href="http://www.nullsoft.com/free/nsis/">http://www.nullsoft.com/
>> free/nsis/</a></li>
>>
>> This redirects to: http://nsis.sourceforge.net/Main_Page
>
> Probably an a stale link.
>
>>
>> [...snip...]
>>
>> + <li>Unpack the OpenVPN unpackaged windows binaries. The
>> + result should be a directory, the unpacked OpenVPN binary
>> + directory. This directory should have subdirectories.</li>
>>
>> Confusing sentences ... a lot of unpacked unpacked binaries unpacked.
>
> How about "Unpack the OpenVPN tar file. The result ..."?
That's a lot better. May I suggest:
"Unpack the OpenVPN tar file. The result should be in a
directory, containing the OpenVPN the OpenVPN binary."
>> +
>> + <li>Using Internet Explorer (TM) navigate to the
>> + <code>nsi</code> subdirectory of the unpacked OpenVPN
>> binary
>> + directory.
>>
>> Using "Internet Explorer"?!? Why not "Using the file browser ..."?
>
> I don't know. I'll look into it if we go farther.
Perfect! It just sounded odd to use IE to browse the local files. Of
course, it's probably a lot of IE mechanisms doing the job "under the hood".
>> [...snip...]
>>
>> + <li> Add the 2 lines:<br /><code>File
>> + "myserver.ovpn"</code><br /><code>File "ca.crt"</code><br /
>>>
>> + to the <code>nsi/openvpn.nsi</code> file at the bottom of
>> + the section titled: <code>Section "${P`'RODUCT_NAME}
>> Service"
>> ^^^^^^^^^^^^^^^
>> Is this really correct?
>
> Dunno. At one point I tested everything. This would include
> in the new installer those files, which are what's needed to
> run a openvpn client that validates the server with a certificate.
> The point of the entire exercise being to create a single installer
> that contains everything needed to run openvpn.
Understood. It was just the syntax with ${P`'RODUCT_NAME} which looked
very odd to me. If it's correct, I won't object to that.
>> + SecService</code></li>
>> +</ol>
>> +
>> +<p>Note that putting your configuration and CA certificate files
>> into
>> +the <code>nsi</code> subdirectory is not the most organized
>> approach.
>> +It is simply the easiest way to get started with NSIS.</p>
>>
>> What about to explain properly how to do it more organised? Most
>> users
>> won't care, and when they learn the sloppy way - they will never
>> improve
>> it if it works.
>
> There are probably multiple good ways to do the job. I can see
> a quick mention of the options but past a certain point it's
> all theory. I look at it this way; most users' won't read
> the instructions anyway.
But remember you have a community which do tell people to read the docs.
At least, we do that pretty often on IRC. And with forums beginning to
get some traction now, I'm sure this will be considered valuable
information!
>> Thank you once again for you patch and patience. If we can have
>> these
>> things straightened up, I'm able to pull it into the git tree. As
>> this
>> patch do not touch any code, we can pretty sure get this on into the
>> 2.2
>> release. We're about to send out a beta release pretty soon, but
>> this
>> patch have the possibility to get accepted into a later beta release.
>
> Unfortunately you caught me at a bad time and I won't be able to work
> on this for at least a couple of weeks and perhaps longer.
> It's waited this long. May as well let it wait and be done right
> when it gets done.
No problem! And we have time to wait for you - in fact, not being
willing to wait would be pretty rude considering it took me some months
to do this review :) And if we miss the 2.2 release, it's always a 2.3
release. But if we get something ready for the 2.2 release, I'm willing
to pull it in, even pretty late in the release cycle.
Thanks again for your feedback!
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkx35KkACgkQDC186MBRfrrCwwCeODxswjDvmZGIJcSbhavkR3Xj
bTcAn2NorMZCczlgYoC1KjLtNx9O8ujq
=zvz3
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
2010-08-27 16:16 ` David Sommerseth
@ 2010-08-27 18:19 ` Karl O. Pinc
0 siblings, 0 replies; 23+ messages in thread
From: Karl O. Pinc @ 2010-08-27 18:19 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: Openvpn-devel
On 08/27/2010 11:16:40 AM, David Sommerseth wrote:
> On 27/08/10 16:20, Karl O. Pinc wrote:
> > On 08/27/2010 03:50:55 AM, David Sommerseth wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> On 09/04/09 19:44, Karl O. Pinc wrote:
> >>>
> >>> On 04/09/2009 07:58:46 AM, Karl O. Pinc wrote:
> > So, is it worth doing any work at all on this?
>
> No problem! I would say it makes sense to give some documentation
> how
> to do this. And you've already done a great job here!
Ok. Good.
> >> [...snip...]
> >>
> >> + <li> Add the 2 lines:<br /><code>File
> >> + "myserver.ovpn"</code><br /><code>File "ca.crt"</
> code><br
> /
> >>>
> >> + to the <code>nsi/openvpn.nsi</code> file at the bottom
> of
> >> + the section titled: <code>Section "${P`'RODUCT_NAME}
> >> Service"
> >> ^^^^^^^^^^^^^^^
> >> Is this really correct?
> >
> > Dunno. At one point I tested everything. This would include
> > in the new installer those files, which are what's needed to
> > run a openvpn client that validates the server with a certificate.
> > The point of the entire exercise being to create a single installer
> > that contains everything needed to run openvpn.
>
> Understood. It was just the syntax with ${P`'RODUCT_NAME} which
> looked
> very odd to me. If it's correct, I won't object to that.
That's what you do in m4 to ensure text is not macro expanded.
(I guess I'm doing some m4 here...)
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2010-08-27 18:19 UTC | newest]
Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-08 0:58 [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP Karl O. Pinc
2009-04-08 3:21 ` dave
2009-04-08 3:50 ` Karl O. Pinc
2009-04-08 5:03 ` Karl O. Pinc
2009-04-08 12:58 ` dave
2009-04-08 15:04 ` Karl O. Pinc
2009-04-08 15:23 ` Matt Wilks
2009-04-08 17:02 ` Karl O. Pinc
2009-04-08 17:48 ` Karl O. Pinc
2009-04-08 22:46 ` Alon Bar-Lev
2009-04-09 3:03 ` Karl O. Pinc
2009-04-09 6:01 ` Alon Bar-Lev
2009-04-09 12:58 ` Karl O. Pinc
2009-04-09 17:44 ` Karl O. Pinc
2010-08-27 8:50 ` David Sommerseth
2010-08-27 14:20 ` Karl O. Pinc
2010-08-27 16:16 ` David Sommerseth
2010-08-27 18:19 ` Karl O. Pinc
2010-02-28 12:27 ` David Sommerseth
2010-03-01 3:48 ` Karl O. Pinc
2010-04-01 15:19 ` Karl O. Pinc
2010-04-20 0:09 ` Karl O. Pinc
2009-04-08 15:10 ` Karl O. Pinc
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.