On Tue, Mar 30, 2021 at 12:00:10AM +0200, Balder Oddson wrote:
> On Thu, Mar 25, 2021 at 12:46:24PM -0600, Theo de Raadt wrote:
> > No way for this diff. This is the wrong way. Surely there are ways
> > to disable compression negotion on specific sessions, but removing
> &
not the same as the path of a particle.
Vroom?
>
> Balder Oddson wrote:
>
> > Compression in PPP was great in the age of ISDN to increase speeds.
> > The more common use cases, and trends concerning TLS1.3 advancements.
> >
> > Having this enabled by default, an
On Thu, Mar 25, 2021 at 08:46:10PM -0600, Theo de Raadt wrote:
> Balder Oddson wrote:
>
> > On Thu, Mar 25, 2021 at 03:40:15PM -0600, Theo de Raadt wrote:
> > > Stuart Henderson wrote:
> > >
> > > > > Not having read the code, case in point on princ
On Thu, Mar 25, 2021 at 03:40:15PM -0600, Theo de Raadt wrote:
> Stuart Henderson wrote:
>
> > > Not having read the code, case in point on principle, I'm arguing that
> > > there should be solid reasoning to enable it by default, as those with a
> > > need for it can certainly enable it and buil
On Thu, Mar 25, 2021 at 07:09:37PM +0100, Balder Oddson wrote:
> Compression in PPP was great in the age of ISDN to increase speeds.
> The more common use cases, and trends concerning TLS1.3 advancements.
>
> Having this enabled by default, and infrequently used could lead to
Compression in PPP was great in the age of ISDN to increase speeds.
The more common use cases, and trends concerning TLS1.3 advancements.
Having this enabled by default, and infrequently used could lead to
unintended consequences around how the data is passed around.
Index: GENERIC
=
On Wed, Dec 30, 2020 at 02:09:46AM +0100, Klemens Nanni wrote:
> On Wed, Dec 30, 2020 at 02:02:44AM +0100, Klemens Nanni wrote:
> >default (alias for "secure")
> >legacy (alias for "all")
> without double quotes
>
First time poster, so, Hi!
Been browsing around this TLS topic, cip
