On Tue, 02 Jul 2002, James Yonan wrote:
> Here are some answers that come to mind:
>
> (1) Accumulate such patches and merge them all at once in a future release
> such as 1.3.0 or 2.0.0, while warning users that this release will not be
> backward compatible.
That's the way to go. Anything else
I agree,
I think that allowing the usage of multiple,
possibly old, protocols adds complexity and
may couse some vulnerabilities.
A cracker could force the daemon to use
some old protocol with security holes
fixed in later versions.
Sampo
> > I'd like to hear your opinions on how the OpenVPN
On Wed, Jul 03, 2002 at 11:16:14AM +0200, Jan Johansson wrote:
> On Tue, 2002-07-02 at 20:34, James Yonan wrote:
> > I'd like to hear your opinions on how the OpenVPN project should handle
> > patches which break backward compatibility.
> > Here are some answers that come to mind:
> >
> > (1) Acc
On Tue, 2002-07-02 at 20:34, James Yonan wrote:
> I'd like to hear your opinions on how the OpenVPN project should handle
> patches which break backward compatibility.
> Here are some answers that come to mind:
>
> (1) Accumulate such patches and merge them all at once in a future release
> such
