lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <SEZPR02MB5495C6CAF78EC669F65CD6398E5C2@SEZPR02MB5495.apcprd02.prod.outlook.com>
Date: Thu, 7 Nov 2024 07:47:14 +0000
From: "Haowei Cheng(Harvey)" <harvey.cheng@...ocom.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: "chunfeng.yun@...iatek.com" <chunfeng.yun@...iatek.com>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-mediatek@...ts.infradead.org"
	<linux-mediatek@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject:
 回复: 回复: 0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch

Hi greg k-h,
   We have configured the USB RNDIS port protocol by default on the product and conducted extensive stress testing and validation.
This issue was discovered during compatibility verification, and after making clear modifications to the API usage,
the issue has not been reproduced in subsequent tests.

________________________________________
发件人: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
发送时间: 2024年11月7日 13:14
收件人: Haowei Cheng(Harvey)
抄送: chunfeng.yun@...iatek.com; linux-usb@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-mediatek@...ts.infradead.org; linux-kernel@...r.kernel.org
主题: Re: 回复: 0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch

On Wed, Nov 06, 2024 at 07:39:59PM +0000, Haowei Cheng(Harvey) wrote:
> Hi greg k-h,
>
> We found during development that when there are data packets to be sent on the USB RNDIS network card,

Also, wait, why in the world are you using RNDIS when it is documented
to be an insecure and broken protocol?  Do you really trust both sides
of that connection?  If so, that's fine, but if not, please do not use
that protocol at all.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ