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] [day] [month] [year] [list]

Message-ID: <2025052239-swimmer-credibly-49a8@gregkh>
Date: Thu, 22 May 2025 18:36:10 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Brigham Campbell <me@...ghamcampbell.com>
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 10:21:10AM -0600, Brigham Campbell wrote:
> 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.

The documentation should have the git config settings that are needed:
	[core]
	        abbrev = 12