All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bzzzz <lazyvirus@gmx.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: About compression
Date: Mon, 31 Jul 2017 21:36:10 +0200	[thread overview]
Message-ID: <20170731213610.5a1304ab@msi.defcon1> (raw)
In-Reply-To: <CAHmME9q2HWQuOciL73HCo+epVbruSO=sP5syAP2GPw5wQ=upKA@mail.gmail.com>

On Mon, 31 Jul 2017 18:10:39 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

> especially contentious issue because of the history of complex and
> catastrophic interactions between compression and encryption (such as
> the CRIME and BREACH attacks against TLS).

Hmm, it just made it much more apparent.

Recently, nsa dismissed the elliptic curve crypto, however, even if I'm
not a mathematico-differencio-analyso-crypto god (but I compensate with
huge premonitions;), something is telling me it's because they can't
break it, compressed or not.

> What workload are you currently experiencing that would measurably
> benefit from having layer 3 compression?

It was more a generic question, somewhat linked to cell phone data
monthly quota, than something vital.

I take good note of your explanation and about what Daniel said,
which is quite logical (doing app level compression.)

Thanks to the both of you.

JY

      parent reply	other threads:[~2017-07-31 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 16:06 About compression Bzzzz
2017-07-31 16:10 ` Jason A. Donenfeld
2017-07-31 16:57   ` Daniel Kahn Gillmor
2017-07-31 19:36   ` Bzzzz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170731213610.5a1304ab@msi.defcon1 \
    --to=lazyvirus@gmx.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.