linux-kernel - Re: [PATCH] oid_registry: allow arbitrary size OIDs

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: <20251125103325.561b88615d1f0a21ddc6262d@linux-foundation.org>
Date: Tue, 25 Nov 2025 10:33:25 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>, David Howells
 <dhowells@...hat.com>, Blaise Boscaccy <bboscaccy@...ux.microsoft.com>
Subject: Re: [PATCH] oid_registry: allow arbitrary size OIDs

On Tue, 25 Nov 2025 13:19:56 -0500 James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> The current OID registry parser uses 64 bit arithmetic which limits us
> to supporting 64 bit or smaller OIDs.  This isn't usually a problem
> except that it prevents us from representing the 2.25. prefix OIDs
> which are the OID representation of UUIDs and have a 128 bit number
> following the prefix.  Rather than import not often used perl
> arithmetic modules, replace the current perl 64 bit arithmetic with a
> callout to bc, which is arbitrary precision.
> 

How big a problem is this in shipped kernels?  Should we backport it?