All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 1/4] eap-tls-common: Address PEAPv0 interoperability with Windows
Date: Mon, 03 Feb 2020 11:35:01 -0600	[thread overview]
Message-ID: <f3708708-e600-90f9-ad6f-470efa67c5ed@gmail.com> (raw)
In-Reply-To: <20200131222517.8182-1-tim.a.kourt@linux.intel.com>

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

Hi Tim,

On 1/31/20 4:25 PM, Tim Kourt wrote:
> Windows Server 2008 - Network Policy Server (NPS) generates an invalid
> Compound MAC for Cryptobinding TLV when is used within PEAPv0 due to
> incorrect parsing of the message containing TLS Client Hello.
> Setting L bit and including TLS Message Length field, even for the
> packets that do not require fragmentation, corrects the issue. The
> redundant TLS Message Length field in unfragmented packets doesn't
> seem to effect the other server implementations.
> ---
>   src/eap-tls-common.c | 35 +++++++++++++++++++++++++++++++++++
>   1 file changed, 35 insertions(+)
> 

patches 1-3 applied, thanks.

Regards,
-Denis

      parent reply	other threads:[~2020-02-03 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 22:25 [PATCH 1/4] eap-tls-common: Address PEAPv0 interoperability with Windows Tim Kourt
2020-01-31 22:25 ` [PATCH 2/4] peap: Add inner EAP key material into imsk calculation Tim Kourt
2020-01-31 22:25 ` [PATCH 3/4] auto-t: Test PEAPv0 cryptobinding Tim Kourt
2020-01-31 22:25 ` [PATCH 4/4] peap: Fail auth. if invalid compound MAC is received Tim Kourt
2020-02-06 21:18   ` Denis Kenzior
2020-02-03 17:35 ` Denis Kenzior [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=f3708708-e600-90f9-ad6f-470efa67c5ed@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.01.org \
    /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.