From nobody Wed Sep 3 15:28:20 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cH62c5Yrrz66c0G for ; Wed, 03 Sep 2025 15:28:40 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cH62c07BDz3vXX; Wed, 03 Sep 2025 15:28:40 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=D2D2wAtA; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-61edf1686ffso991960a12.0; Wed, 03 Sep 2025 08:28:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1756913313; x=1757518113; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=uketxR9MtJnTCDPW+UNcXi6AE3WSIwPZTW/h7nPPl80=; b=D2D2wAtAdID5EFIZEnVLsrnL0lL1rP1hGaUiuOXHEO9m+TdnSqh+1Kw6wL6nhLFoK8 HxRluXXNXiFhQRjB4xt8nSYcMBKJkjV4iyOvhiUurwnU5UMUbcQO4GuRqWZOG3Zr5xRa j8gR5Bg5/d5X5njx6NzIVT2FaiOKg8/LQzSgnPw52Qu68jzh01L2km+6F0T9ujAw9Q63 tUw6n5ZkycWfK7pxl7X18BJH8nqfvFszWfSL8av2Yu9Dh4SVm3fi7MkluShbtfrvMCma Stk7H4xhCt2E0kKeXQExIV2a0RPk066c8LLsq7NmTnOLsWOeyIaEKUjfXCqgPlrddkgD IsXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756913313; x=1757518113; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=uketxR9MtJnTCDPW+UNcXi6AE3WSIwPZTW/h7nPPl80=; b=f2uLSMD0eEalU21nWnMULY7v2aAX+LyHkV4ou87oAlc4dblYqfIO0azDQwB5vZi9ex 92h15daXoZ/tpaMI5v3dZbi7RZsjRON4FCncQpiK+2AiZ4eIWvhqeNwAYdB7vqjiLHaV 2Ns9MyKZFEtTJnOpUEQ/2J3s4hPgTycsc86X8DoYiY4Mf/vYksdmPqfMhsw+XBCZOCsi dVhQffP1Vo/vMfVeZGR8ZifJNWqcnLxfKP59+6jKYv/t3Be1+0vCnUPauHqCBVZWIH2b RHmw34Fd/FxVBNMmp3GYbDCrWVoC0wp5j2YlYt9B+mwzwAVOhQtWHmgYB52FxUnJgQ0f cKng== X-Forwarded-Encrypted: i=1; AJvYcCXeQJlC4srrxXHiu8EO4ROwhMOgFhGzyLV48IZbOzZxBndOllLQYdp9Dy8K/1ru8AMs83vin2xf1Vps0rYf2k4=@freebsd.org X-Gm-Message-State: AOJu0YxrTjikR0AO4VOUcjc1AmxcEUVEsUOU7Bowq8eeNzDUejgqOSLo ntu/RBUXII2yu5s8F+gPTHLSiNrTuG1P9k/P0d5r/mPoIXSP2eVgUs6btwVC0pA/R0IjnNWboUu MD7weJqDazrMVEdqpAiMbzfMCd9nQmj0SElg= X-Gm-Gg: ASbGncuTpxg3d+KKQ7F58AsKpMZntbb7+JEXtCg7b+x2Bz639LUkRE7/6WbW6VDe0hV TwpGRY5UE3OBJ2aTZrUegPLwArJayay3bQl3sRj6ERJdwkBn21I3UdJdctUSnzwxGCzll+KUsOM w/TdUTddOq2u/gJzmchXz6tqX5RuQe1vpeOtwdgxjh6MQGJV/Pi/74g150CYFutgd6BuMYGGol4 4DfjD7Y+p03dcD6d1LTdt1eBsjVHrjX2T7e9kQ= X-Google-Smtp-Source: AGHT+IGdWZqtZH/p8pwWhmiTmHM5K1TJW4a46YbOaVuwJAjzKrhXJ/l0MOy1eKy9HCJIc+96dcjdpzw/YT24zT+G8jw= X-Received: by 2002:a05:6402:50c7:b0:61e:acff:8e20 with SMTP id 4fb4d7f45d1cf-61eacff9df1mr8993670a12.6.1756913312568; Wed, 03 Sep 2025 08:28:32 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <56dd78c6-a53a-4c4c-989a-335cc5fed405@FreeBSD.org> <1578a4eac5402d0496d8989e5258bc78@Leidinger.net> <20250903043714.370F5311@slippy.cwsent.com> In-Reply-To: From: Rick Macklem Date: Wed, 3 Sep 2025 08:28:20 -0700 X-Gm-Features: Ac12FXyavvwhK_vJxW84ugnkeJsEK4zQrz9W1AxFYu2kT-18eIw7lf-jR4Fh0y4 Message-ID: Subject: Re: heimdal -> MIT kdc migration To: Cy Schubert Cc: Gleb Smirnoff , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.07 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.07)[-0.071]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::529:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4cH62c07BDz3vXX On Tue, Sep 2, 2025 at 10:10=E2=80=AFPM Rick Macklem wrote: > > On Tue, Sep 2, 2025 at 9:37=E2=80=AFPM Cy Schubert wrote: > > > > In message > om> > > , Rick Macklem writes: > > > On Sun, Aug 31, 2025 at 5:58=3DE2=3D80=3DAFPM Rick Macklem > > m> wrote: > > > > > > > > On Sun, Aug 31, 2025 at 5:41=3DE2=3D80=3DAFPM Rick Macklem > > com> wrote: > > > > > > > > > > On Sat, Aug 30, 2025 at 9:47=3DE2=3D80=3DAFPM Rick Macklem > > l.com> wrote: > > > > > > > > > > > > On Sat, Aug 30, 2025 at 4:22=3DE2=3D80=3DAFPM Rick Macklem > > ail.com> wrote: > > > > > > > > > > > > > > On Sat, Aug 30, 2025 at 8:56=3DE2=3D80=3DAFAM Rick Macklem > > gmail.com> wrote: > > > > > > > > > > > > > > > > On Fri, Aug 29, 2025 at 1:05=3DE2=3D80=3DAFPM Rick Macklem = > > m@gmail.com> wrote: > > > > > > > > > > > > > > > > > > On Fri, Aug 29, 2025 at 7:43=3DE2=3D80=3DAFAM Rick Mackle= m > > lem@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > On Wed, Aug 27, 2025 at 8:39=3DE2=3D80=3DAFPM Rick Mack= lem > > cklem@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > On Wed, Aug 27, 2025 at 7:43=3DE2=3D80=3DAFPM Rick Ma= cklem > > macklem@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Aug 26, 2025 at 9:35=3DE2=3D80=3DAFAM Gleb = Smirnoff > > ebius@freebsd.org> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Aug 26, 2025 at 08:31:13AM -0700, Gleb Sm= irnoff=3D > > > wrote: > > > > > > > > > > > > > T> On Tue, Aug 26, 2025 at 08:13:26AM -0700, Rick= Mackl=3D > > > em wrote: > > > > > > > > > > > > > T> R> Ok. If you install FreeBSD-13.5 and then "p= kg ins=3D > > > tall heimdal", you get a > > > > > > > > > > > > > T> R> working Heimdal-7.8 in ports. > > > > > > > > > > > > > T> R> > > > > > > > > > > > > > T> R> Now, I have another challenge. Fixing the m= aster =3D > > > passwords. > > > > > > > > > > > > > T> R> I'll work on it later to-day. > > > > > > > > > > > > > T> > > > > > > > > > > > > > T> I have applied two commits from Heimdal from 2= 012 th=3D > > > at add 'kadmin dump -f MIT' > > > > > > > > > > > > > T> feature to our base heimdal and polished them = to com=3D > > > pile. So far it doesn't > > > > > > > > > > > > > T> work yet, either create an empty dump or creat= e a co=3D > > > re dump, instead of > > > > > > > > > > > > > T> database dump :) I'll see how difficult it is = going =3D > > > to further resolve that to > > > > > > > > > > > > > T> a working condition. If I succeed, then having= 'dump=3D > > > -f MIT' in base without > > > > > > > > > > > > > T> any ports would be the best solution. Can als= o be m=3D > > > erged to FreeBSD 14.4. > > > > > > > > > > > > > > > > > > > > > > > > > > Good news. In the above paragraph I was testing = my cha=3D > > > nge incorrectly - threw > > > > > > > > > > > > > the new binary on a system running unpatched libr= aries.=3D > > > When run correctly, > > > > > > > > > > > > > it successfully produced something that looks lik= e a co=3D > > > rrect dump in MIT format. > > > > > > > > > > > > > I haven't yet tried to load it into MIT kdc yet, = though=3D > > > . > > > > > > > Well, would you like the not so bad news or the bad news??;-) > > > > > > > Your patch works, in that it produces a dump that "kdb5_util = load > > > > > > > -update" can load. > > > > > > > After loading, if the principal only has keys for the newer e= ncrypt=3D > > > ion types of > > > > > > > aes256-cts-hmac-sha1-96 > > > > > > > aes128-cts-hmac-sha1-96 > > > > > > > then you can look at the principal via kadmin.local, but the = passwo=3D > > > rd must > > > > > > > be changed before it works. > > > > > > > --> This is the same behaviour as you get if you use Heimdal-= 7.8 to=3D > > > do the > > > > > > > dump conversion. > > > > > > > So far, so good... > > > > > > > > > > > > > > Now, the not so good news. Once you update the Heimdal librar= ies > > > > > > > (libhdb.so and libkadm5srv.so) "kadmin -l" is broken on the s= ystem > > > > > > > running the old KDC. "kadmin -l dump" works, but something li= ke: > > > > > > > # kadmin -l > > > > > > > kadmin> get rmacklem > > > > > > > kadmin: get rmacklem: Service key not available > > > > > > > - I have not yet looked in your patched sources to see where = this > > > > > > > failure comes from? > > > > > > > > > > > > > > Now, more not so good news... > > > > > > > My patch doesn't help. > > > > > > > It does re-encrypt the key in the master key from the MIT KDC > > > > > > > system, but that doesn't make the password work. > > > > > > > When I compared the dump generated via kadmin with both > > > > > > > your patch and mine, the key for aes256-cts-hmac-sha1-96 > > > > > > > is 34bytes long. > > > > > > > After doing the change_password so that it works, a dump > > > > > > > generated by "kdb5_util dump -r13" (the same dump format) > > > > > > > has a key that is 62bytes long. > > > > > > > --> So, there is more to converting the key than just re-ecry= pting > > > > > > > it. (I'll try and find where the MIT code encrypts a ke= y in a=3D > > > master > > > > > > > key to see why it ends up at 62bytes and whether that c= an be =3D > > > done > > > > > > > in the old code.) > > > > > > > > > > > > > > So, if we are going to continue with this... > > > > > > > - We need to figure out why your patch breaks "kadmin" for ot= her > > > > > > > things and fix that. > > > > > > > - I/we need to figure out how to convert the 34byte key to th= e MIT > > > > > > > 62byte key (and then maybe the password won't need to be ch= anged?=3D > > > ). > > > > > > > > > > > > > > Or do we just say "When you convert the KDC database, all the= passw=3D > > > ords > > > > > > > must be changed to get them to work?". > > > > > > All I've got sofar is this patch... > > > > > > https://people.freebsd.org/~rmacklem/print.patch > > > > > > > > > > > > It tweaks entry2mit_string_int() so that it skips over the keys= for > > > > > > old encryption types and fills in a fake "modified by" entry if= none > > > > > > exists. > > > > > > > > > > > > These changes at least make the MIT dump such that the records > > > > > > don't end up "incomplete or corrupted" when you try to do somet= hing > > > > > > like "get_principal " in kadmin.local. > > > > > > > > > > > > As noted, your patch makes "kadmin -l" break for most things, > > > > > > reporting "Service key not available". The failures go away if > > > > > > you revert back to the non-patched libraries. > > > > > > I have not located the problem yet. > > > > > > > > > > > > As for the passwords...no luck yet, rick > > > > > Finally..it works. (First off, apologies for all the posts, just = ignore > > > > > them.;-) > > > > > > > > > > The patch is at: > > > > > https://people.freebsd.org/~rmacklem/kadmin.patch > > > I just updated the patch with a fix for the case where the > > > Heimdal principal does not have any keys for string encryption. > > > (That is fixed now and I haven't found any other bugs, so I > > > think I am done playing with it. Yippee!!) > > > > > > Please test when you can find the time, rick Outstanding issue/question w.r.t. converting the KDC database from Heimdal 1.5.2->MIT. Right now, the patch I have drops the weak encryption type keys (des3.. and arcfour..). If the principal in the Heimdal KDC does not have keys for either of: aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 the patch generates a "fake" one. As a result, a change_password for the principal is needed for this case. The alternative to doing this would be an option that converts the weak keys, but... - The MIT KDC will find the principal "incomplete or corrupted" for at least the "out-of-the-box" configuration. - It might accept them if "accept_weak_ecntypes" is set in the kdc.conf. This leads to a couple of questions: - Does anyone know if MIT 1.22 still allows "accept_weak_enctypes? If it does not allow them, I don't think there is much use for this option? Given the release schedule, it would be nice to get this resolved soon. Also, someone needs to document this. The Handbook section does a nice job of explaining the setup of a Heimdal KDC, but has nothing w.r.t. setting up an MIT KDC nor converting the KDC database over to it. rick > > > > I think the problem is with OpenSSL 3.5. With the legacy provider loade= d in > > OpenSSL 3.5 I get, > > > > test3# openssl list -providers > > Providers: > > default > > name: OpenSSL Default Provider > > version: 3.5.1 > > status: active > > test3# > > > > Whereas in 3.0 I get, > > > > bob# openssl list -providers > > Providers: > > default > > name: OpenSSL Default Provider > > version: 3.0.16 > > status: active > > legacy > > name: OpenSSL Legacy Provider > > version: 3.0.16 > > status: active > > bob# > > > > Some symbol must be missing. > Ok, I seem to have missed something here? > Just in case it wasn't clear, I was referring to testing of the > kadmin patches for the old Heimdal, so that the KDC database > can be moved to an MIT KDC and still work. > > rick > > > > > > > -- > > Cheers, > > Cy Schubert > > FreeBSD UNIX: Web: https://FreeBSD.org > > NTP: Web: https://nwtime.org > > > > e**(i*pi)+1=3D0 > > > >