public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Rhys Perry <rhysperry111@gmail.com>, iwd@lists.linux.dev
Subject: Re: TLS session key?
Date: Tue, 30 Jan 2024 04:35:16 -0800	[thread overview]
Message-ID: <d6b782f1-2e72-470e-9423-a4be993cdf43@gmail.com> (raw)
In-Reply-To: <CAGTBY+uz6kxvM7OEVQUVCyHNnz6APuPgvmQkHBemN1wFkQpiGg@mail.gmail.com>

Hi Rhys,

On 1/30/24 2:48 AM, Rhys Perry wrote:
> Hi,
>
> Just wondering whether it's possible to get IWD to dump the TLS
> session key it uses for EAP on an enterprise network? I'm trying to
> debug some odd behavior that some network users are experiencing and
> think that there might be some clues in the encrypted messages.

No, IWD doesn't dump any keys in the debug log, so it would probably 
require a source code change for debugging. You can use l_util_hexdump() 
to make this easier.

Thanks,

James

>
> Kind regards,
> Rhys
>

      reply	other threads:[~2024-01-30 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 10:48 TLS session key? Rhys Perry
2024-01-30 12:35 ` James Prestwood [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=d6b782f1-2e72-470e-9423-a4be993cdf43@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=rhysperry111@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox