Message-ID:

Always try to do things in chronological order; it's less confusing that way.

computers / comp.dcom.telecom / 100 million Samsung phones affected by encryption weakness [telecom]

100 million Samsung phones affected by encryption weakness [telecom]

<20220309202221.325B4892@telecom2018.csail.mit.edu>

https://www.novabbs.com/computers/article-flat.php?id=2994&group=comp.dcom.telecom#2994

copy link Newsgroups: comp.dcom.telecom

Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!post.local
From: malQRMas...@gmail.com (Bill Horne)
Newsgroups: comp.dcom.telecom
Subject: 100 million Samsung phones affected by encryption weakness [telecom]
Date: Wed, 9 Mar 2022 20:22:21 +0000 (UTC)
Organization: The Telecom Digest
Lines: 11
Sender: news@iecc.com
Approved: telecom-moderator@telecom.csail.mit.edu
Message-ID: <20220309202221.325B4892@telecom2018.csail.mit.edu>
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970";
logging-data="92579"; mail-complaints-to="abuse@iecc.com"
Authentication-Results: iecc.com; spf=none spf.mailfrom=moder8@telecom.csail.mit.edu spf.helo=telecom2018.csail.mit.edu smtp.remote-ip="128.31.0.70"; dmarc=none header.from=gmail.com polrec.p=none polrec.pct=100

by: Bill Horne - Wed, 9 Mar 2022 20:22 UTC

by Brandon Vigliarolo

The vulnerability lies in how Samsung implemented a portion of the
Android Trusted Execution Environment, leading to devices as new as
the S21 being vulnerable to initialization vector reuse attacks.

https://www.techrepublic.com/article/100-million-samsung-phones-affected-by-encryption-weakness/

--
(Please remove QRM from my email address to write to me directly)

Subject	Author
100 million Samsung phones affected by encryption weakness [telecom]	Bill Horne