From: Laszlo Ersek <lersek@redhat.com>
To: Jiaxin Wu <Jiaxin.wu@intel.com>, edk2-devel@lists.01.org
Cc: Ye Ting <ting.ye@intel.com>, Fu Siyuan <siyuan.fu@intel.com>
Subject: Re: [PATCH v1] NetworkPkg/TlsDxe: Fix failure to process multiple TLS records.
Date: Mon, 5 Nov 2018 19:32:41 +0100 [thread overview]
Message-ID: <6571c3cf-7db2-4e88-f5a0-56aef5bf63c3@redhat.com> (raw)
In-Reply-To: <20181031054212.3276-1-Jiaxin.wu@intel.com>
On 10/31/18 06:42, Jiaxin Wu wrote:
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1290.
>
> Current implementation failed to parse the multiple TLS record
> messages due to the incorrect pointer of TLS record header. This
> patch is to resolve that problem.
>
> Cc: Ye Ting <ting.ye@intel.com>
> Cc: Fu Siyuan <siyuan.fu@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Wu Jiaxin <jiaxin.wu@intel.com>
> ---
> NetworkPkg/TlsDxe/TlsImpl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/NetworkPkg/TlsDxe/TlsImpl.c b/NetworkPkg/TlsDxe/TlsImpl.c
> index ea83dbd04f..2d4169b0a5 100644
> --- a/NetworkPkg/TlsDxe/TlsImpl.c
> +++ b/NetworkPkg/TlsDxe/TlsImpl.c
> @@ -142,11 +142,11 @@ TlsEncryptPacket (
> }
>
> BufferOutSize += ThisMessageSize;
>
> BufferInPtr += TLS_RECORD_HEADER_LENGTH + ThisPlainMessageSize;
> - TempRecordHeader += ThisMessageSize;
> + TempRecordHeader = (TLS_RECORD_HEADER *)((UINT8 *)TempRecordHeader + ThisMessageSize);
> }
>
> FreePool (BufferIn);
> BufferIn = NULL;
>
> @@ -315,11 +315,11 @@ TlsDecryptPacket (
> CopyMem (TempRecordHeader, RecordHeaderIn, TLS_RECORD_HEADER_LENGTH);
> TempRecordHeader->Length = ThisPlainMessageSize;
> BufferOutSize += TLS_RECORD_HEADER_LENGTH + ThisPlainMessageSize;
>
> BufferInPtr += TLS_RECORD_HEADER_LENGTH + ThisCipherMessageSize;
> - TempRecordHeader += TLS_RECORD_HEADER_LENGTH + ThisPlainMessageSize;
> + TempRecordHeader = (TLS_RECORD_HEADER *)((UINT8 *)TempRecordHeader + TLS_RECORD_HEADER_LENGTH + ThisPlainMessageSize);
> }
>
> FreePool (BufferIn);
> BufferIn = NULL;
>
>
What is the practical impact of this issue? In what scenario was it
encountered? What were the symptoms?
I realize the patch may have been pushed by now -- please consider
adding the information to the BZ. (Or, please answer here, and then add
the message URL to the BZ.)
Thanks
Laszlo
next prev parent reply other threads:[~2018-11-05 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 5:42 [PATCH v1] NetworkPkg/TlsDxe: Fix failure to process multiple TLS records Jiaxin Wu
2018-10-31 5:53 ` Fu, Siyuan
2018-11-05 18:32 ` Laszlo Ersek [this message]
2018-11-06 2:13 ` Wu, Jiaxin
2018-11-06 14:25 ` Laszlo Ersek
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-list 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=6571c3cf-7db2-4e88-f5a0-56aef5bf63c3@redhat.com \
--to=devel@edk2.groups.io \
/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