linux-kernel - Re: [PATCH 1/1] usb: typec: tipd: fix typo in TPS_STATUS_HIGH_VOLAGE

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: <DA2TS4HXZHLK.1WH4DSREYSAP4@brighamcampbell.com>
Date: Thu, 22 May 2025 10:21:10 -0600
From: "Brigham Campbell" <me@...ghamcampbell.com>
To: "Greg KH" <gregkh@...uxfoundation.org>
Cc: "Jihed Chaibi" <jihed.chaibi.dev@...il.com>,
 <heikki.krogerus@...ux.intel.com>, <linux-usb@...r.kernel.org>,
 <linux-kernel@...r.kernel.org>, <linux-kernel-mentees@...ts.linux.dev>,
 <skhan@...uxfoundation.org>
Subject: Re: [PATCH 1/1] usb: typec: tipd: fix typo in
 TPS_STATUS_HIGH_VOLAGE_WARNING macro

On Thu May 22, 2025 at 2:30 AM MDT, Greg KH wrote:
>
> Too many characters for that sha1 value :)

I heard recently about concerns regarding the collision of 12-character
sha1 abbreviations [1] and had assumed that using 16 characters is
acceptable. Regrettably, I neglected to read Linus's response to the
email which rose those concerns. After reading his response, I'm
satisfied knowing that there is still very little risk of a collision
between the abbreviations of commit objects specifically.

I'll modify my git config to use 12 character abbrevs.

Thanks,
Brigham

[1]: https://lore.kernel.org/lkml/cover.1733421037.git.geert+renesas@glider.be/