-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/02/10 04:39, Karl O. Pinc wrote:
> On 02/19/2010 05:11:38 PM, David Sommerseth wrote:
>> On 20/02/10 00:06, Karl O. Pinc wrote:
>>> On 02/19/2010 04:57:30 PM, David Sommerseth wrote:
>>>
>>> Am I wrong or does using --disable-depr-random-resolv
>
>
>> Btw. what do you think about including the full IRC chatlog in these
>> emails?
>>
>
> I like it. (And don't see the point in having a separate attachment
> either. It's just one more thing to have to click on.)
>
Ok, this week I'll add the chatlog as an attachment (due to it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/02/10 23:57, David Sommerseth wrote:
> From: David Sommerseth
>
> (I'm withdrawing the first version, and suggesting this patch to be used
> instead,
> as this one follows the new feature deprecation process.)
>
> Based on a discussion on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/02/10 22:27, Bernhard Schmidt wrote:
> On Sun, Feb 21, 2010 at 08:00:27PM +0100, JuanJo Ciarlante☀ wrote:
>
>> This patch makes ipv6_payload successfully cross *compile*
>> (and just that :) under my mingw32msvc setup on Linux.
>>
>> Because sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/02/10 12:56, JuanJo Ciarlante wrote:
> Hey David,
>
> On Fri, Feb 19, 2010 at 12:29 PM, JuanJo Ciarlante wrote:
> I've created an feat_ipv6_transport branch where I'll track your
> patches. Gert's IPv6 patches are in feat_ipv6_payload (which a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/02/10 18:58, Karl O. Pinc wrote:
>
> Hi,
>
> Re: [PATCH] Change verify-cn so cn is no longer hardcoded in openvpn's config
> file
>
> This patch should be easy to process.
> A resubmission of the patch sent to this list on 04/23/2009.
>
> Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/02/10 17:37, David Sommerseth wrote:
> With --verb 5, openvpn logs a single letter (rwRW) for each package
> received or sent. I recently ran into a problem with the tun device on
> Linux where the read from that device returned 0. Unfortunately
On 02/22/2010 01:46:53 AM, David Sommerseth wrote:
The commit log
> will
> state that this begins the feature deprecation process, with a
> warning
> when this feature is used and the feature can be removed at compile
> time
> with --disable-depr-random-resolv.
I've thought a bit more about t
On 02/19/2010 05:11:38 PM, David Sommerseth wrote:
> On 20/02/10 00:06, Karl O. Pinc wrote:
> > On 02/19/2010 04:57:30 PM, David Sommerseth wrote:
> >
> > Am I wrong or does using --disable-depr-random-resolv
> > not remove the random choice?
>
> That is correct. According to the newly agreed fea
Karl O. Pinc wrote:
> Someone may be relying on the behavior but, at the moment
> or depending on present dns circumstances, does not have
> multiple A records returned. In this case no warning will
> be generated.
The flip side of that coin is also valid I think.
Consider independent configurat
On 02/22/2010 10:52:17 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > Someone may be relying on the behavior but, at the moment
> > or depending on present dns circumstances, does not have
> > multiple A records returned. In this case no warning will
> > be generated.
>
> The flip side of that
Hello all!
I'm using the openvpn-client with connmand (Redhat Moblin connection
manager) and everything seems to be working fine although once every
hour, like perfect clockwork, I get a segfault although there are no
noticeable issues, crashes, exits. Everything just keeps chuggin along.
-
From: David Sommerseth
Added a new function, warn_deprecated_features(), which is located in
deprecated.[ch]. All deprecated features should present a warning here.
This function will be called during start-up and will show all warnings
after the OpenVPN title string.
Included a deprecated feat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/10 18:16, Karl O. Pinc wrote:
> On 02/22/2010 10:52:17 AM, Peter Stuge wrote:
>> Karl O. Pinc wrote:
>>> Someone may be relying on the behavior but, at the moment
>>> or depending on present dns circumstances, does not have
>>> multiple A reco
On 02/22/2010 03:46:33 PM, David Sommerseth wrote:
>
> Does that cover your concerns?
Yes. It's all somewhat a matter of taste, so if you
find it tasty that's good enough for me. :-)
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/10 22:25, mark wrote:
> Hello all!
>
> I'm using the openvpn-client with connmand (Redhat Moblin connection
> manager) and everything seems to be working fine although once every
> hour, like perfect clockwork, I get a segfault although the
16 matches
Mail list logo
