On 27-Apr-10, at 5:11 AM, Karl O. Pinc wrote:
On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
Karl O. Pinc wrote:
the project is already releasing unpackaged Linux
binaries
Really?
They seem to have stopped sometime after July 30 2008.
http://web.archive.org/web/20080730205524/openvpn.net/
On 27-Apr-10, at 1:58 AM, Karl O. Pinc wrote:
On 04/26/2010 10:23:21 AM, David Sommerseth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 16:47, Karl O. Pinc wrote:
Speaking of the standard release process there is still this
thread:
Re: [Openvpn-devel] Unpackged Windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 21:11, Karl O. Pinc wrote:
> On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
>> Karl O. Pinc wrote:
[...snip...]
> IMO people who don't rely on their distro for systems integration
> and security patches are asking for trouble. There are of
On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > the project is already releasing unpackaged Linux
> > binaries
>
> Really?
They seem to have stopped sometime after July 30 2008.
http://web.archive.org/web/20080730205524/openvpn.net/index.php/
downloads.html
It's hard to
Hi all,
Patel ("openvpn2009" in IRC) just informed me that he fixed the Trac
(Apache) certificate issue. The problem was caused by rekeying of the
wildcard certificate, which was required for our internal servers. This
caused the (old) certificate on community.openvpn.net to be revoked.
Anyways, T
Davide Brini wrote:
> The users are supposed to adapt it to their needs and make it more
> robust.
Hah! Users will not.
//Peter
Karl O. Pinc wrote:
> the project is already releasing unpackaged Linux
> binaries
Really?
> and it now talking about doing the same for OS/X binaries.
Recently discussed work for contrib/ produces a .dmg, very much a
package in my view.
> There's clear utility.
I guess it depends. I'm not s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 17:55, Davide Brini wrote:
> On Monday 26 Apr 2010 16:19:20 David Sommerseth wrote:
>
>>> (I still think it would be nice to have some sort of channel to send
>>> errors to OpenVPN's main log from the children scripts or programs, so
>>> u
On 04/26/2010 10:23:21 AM, David Sommerseth wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 26/04/10 16:47, Karl O. Pinc wrote:
> > Speaking of the standard release process there is still this
> thread:
> >
> > Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems
> buildi
On Monday 26 Apr 2010 16:19:20 David Sommerseth wrote:
> > (I still think it would be nice to have some sort of channel to send
> > errors to OpenVPN's main log from the children scripts or programs, so
> > users could inspect it.)
>
> This begins to look very good!
>
> Just for the errors ... t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 16:47, Karl O. Pinc wrote:
> On 04/26/2010 03:42:37 AM, Arnoud Vermeer wrote:
>> Hi Toby,
>>
>> I for one appreciate your effort and would love to see this in the
>> standard
>> release process.
>
> Speaking of the standard release process
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 17:08, Davide Brini wrote:
> On Monday 26 Apr 2010 15:50:56 Karl O. Pinc wrote:
>
itself. So if the script could fail gracefully giving a hint like
"you've not done as I told you to", some support issues will be
avoided.
>>
On Monday 26 Apr 2010 15:50:56 Karl O. Pinc wrote:
> > > itself. So if the script could fail gracefully giving a hint like
> > > "you've not done as I told you to", some support issues will be
> > > avoided.
> >
> > Ok, that makes sense. I didn't look at it this way, but then I
> > perfectly know
On 04/26/2010 05:48:38 AM, Davide Brini wrote:
> On Monday 26 Apr 2010 11:04:16 David Sommerseth wrote:
> >
> > Agreed, but from experience with many users ... it's a lot of users
> who
> > just take a script and try it out without even looking at the
> script
> > itself. So if the script could
On 04/26/2010 03:42:37 AM, Arnoud Vermeer wrote:
> Hi Toby,
>
> I for one appreciate your effort and would love to see this in the
> standard
> release process.
Speaking of the standard release process there is still this thread:
Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems buildi
On 04/26/2010 03:56:16 AM, Davide Brini wrote:
> On Monday 26 Apr 2010 00:13:39 David Sommerseth wrote:
> > > +# OCSP responder URL (mandatory)
> > > +ocsp_url="http://some.ocsp.server/";
> > > +#ocsp_url="https://some.secure.ocsp.server/";
> >
> > Wouldn't it be better to use a more valid URL?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 14:08, Toby Thain wrote:
[...snip...]
>>> cc'd devel list in case there is any interest in adopting the
>>> packaging script(s), perhaps as contrib?
>>>
>>> http://telegraphics.com.au/svn/openvpn-package/trunk/
>>
>> Even though I don't hav
On 26-Apr-10, at 9:34 PM, David Sommerseth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 01:47, Toby Thain wrote:
Hi,
I have put together a generic packaging script for OS X (pkg/dmg),
and
created basic binary Installer packages for PowerPC and Intel. It's
meant only fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 01:47, Toby Thain wrote:
> Hi,
>
> I have put together a generic packaging script for OS X (pkg/dmg), and
> created basic binary Installer packages for PowerPC and Intel. It's
> meant only for distributing the generic binary distributi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 12:48, Davide Brini wrote:
> On Monday 26 Apr 2010 11:04:16 David Sommerseth wrote:
[...snip...]
> I have another (unrelated) question. The GIT master branch lacks the
> configure
> script, so how do you go about building it for testing?
On Monday 26 Apr 2010 11:04:16 David Sommerseth wrote:
> >> ... and have a check that this variable is set? If unset, exit with
> >> error.
> >
> > Ah well, as I said the script is meant to be a barebone skeleton to
> > demonstrate basic usage. That is by no means the only thing that lacks
> > pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 10:56, Davide Brini wrote:
> On Monday 26 Apr 2010 00:13:39 David Sommerseth wrote:
[...snip...]
>>> +# OCSP responder URL (mandatory)
>>> +ocsp_url="http://some.ocsp.server/";
>>> +#ocsp_url="https://some.secure.ocsp.server/";
>>
>> Wouldn
Hi Toby,
I for one appreciate your effort and would love to see this in the standard
release process.
Kind regards,
Arnoud Vermeer
On Mon, Apr 26, 2010 at 1:47 AM, Toby Thain wrote:
> Hi,
>
> I have put together a generic packaging script for OS X (pkg/dmg), and
> created basic binary Installe
On Monday 26 Apr 2010 00:13:39 David Sommerseth wrote:
> Btw! Very good idea by introducing the OCSP_check.sh example! And even
> a proper git patch! I like that :)
Thanks!
> > +# OCSP responder URL (mandatory)
> > +ocsp_url="http://some.ocsp.server/";
> > +#ocsp_url="https://some.secure.ocsp
From: David Sommerseth
For OpenVPN clients with long living connections, this message is repeated
everytime the connection is renegotiated. This patch removes this behaviour
and will only show this warning once.
Signed-off-by: David Sommerseth
---
misc.c |4 +++-
1 files changed, 3 insert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/10 00:42, David Sommerseth wrote:
> From: David Sommerseth
>
> For OpenVPN clients with long living connections, this message is repeated
> everytime the connection is renegotiated. This patch removes this behaviour
> and will only show thi
26 matches
Mail list logo
