All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Paasch <cpaasch at apple.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [RFC v3 00/15] TCP Extra-option framework for TCP-MD5 and SMC
Date: Fri, 15 Dec 2017 11:00:46 -0800	[thread overview]
Message-ID: <20171215190046.GE36076@Chimay.local> (raw)
In-Reply-To: 20171213000516.GQ85539@da0602a-dhcp135.apple.com

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

On 12/12/17 - 16:05:16, Christoph Paasch wrote:
> On 12/12/17 - 15:40:20, Mat Martineau wrote:
> > 
> > On Mon, 11 Dec 2017, Christoph Paasch wrote:
> > 
> > > 3rd version of the set.
> > > 
> > > Now, fully tested and bugs fixed.
> > > 
> > 
> > One more question - can you elaborate on the testing you did? Were the keys
> > set before connecting, modified or deleted during while connected, etc.? Did
> > you build with KASAN or lockdep?
> 
> Yes, built with KASAN and full lockdep debugging.
> 
> I did tests where I set the keys on one side, not the other one and check
> the connections got rejected.
> 
> Then I tested setting the keys at the beginning.
> 
> I will do an additional test where I change the keys half-way through the
> connection.

FYI, just tested starting with a key set on client and listener, then after
accept() and a write/read, I set the key to 0 (thus removing MD5). Then
after a bunch of reads/writes I set again a different key.

Works as expected.


Christoph


             reply	other threads:[~2017-12-15 19:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 19:00 Christoph Paasch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-14  0:33 [MPTCP] [RFC v3 00/15] TCP Extra-option framework for TCP-MD5 and SMC Christoph Paasch
2017-12-13 16:30 Mat Martineau
2017-12-13  0:05 Christoph Paasch
2017-12-13  0:04 Christoph Paasch
2017-12-12 23:40 Mat Martineau
2017-12-12 23:35 Mat Martineau
2017-12-11 21:42 Christoph Paasch

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=20171215190046.GE36076@Chimay.local \
    --to=unknown@example.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.