Page MenuHomeFreeBSD

krb5: create the KDC database directory
ClosedPublic

Authored by glebius on Oct 7 2025, 9:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Nov 7 2025, 5:21 AM
Unknown Object (File)
Nov 2 2025, 1:28 AM
Unknown Object (File)
Nov 2 2025, 1:19 AM
Unknown Object (File)
Oct 27 2025, 2:01 AM
Unknown Object (File)
Oct 25 2025, 5:46 PM
Unknown Object (File)
Oct 25 2025, 12:41 AM
Unknown Object (File)
Oct 24 2025, 6:20 PM
Unknown Object (File)
Oct 24 2025, 6:12 PM
Subscribers

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 67627
Build 64510: arc lint + arc unit

Event Timeline

Looks fine to me. Is there somewhere that we can stick
examples for krb5.conf, kdc.conf and kadm5.acl?

This revision is now accepted and ready to land.Oct 7 2025, 9:13 PM

Looks fine to me. Is there somewhere that we can stick
examples for krb5.conf, kdc.conf and kadm5.acl?

In share/examples/krb5 maybe?

In D52970#1210155, @cy wrote:

Looks fine to me. Is there somewhere that we can stick
examples for krb5.conf, kdc.conf and kadm5.acl?

In share/examples/krb5 maybe?

Fine with me. For Heimdal, krb5.conf is in crypto/heimdal,
so crypto/krb5 might be more consistent?

However, I have no real opinion w.r.t. where. I just think
having an example of each somewhere makes setup
easier.

This revision was automatically updated to reflect the committed changes.
In D52970#1210155, @cy wrote:

Looks fine to me. Is there somewhere that we can stick
examples for krb5.conf, kdc.conf and kadm5.acl?

In share/examples/krb5 maybe?

Fine with me. For Heimdal, krb5.conf is in crypto/heimdal,
so crypto/krb5 might be more consistent?

However, I have no real opinion w.r.t. where. I just think
having an example of each somewhere makes setup
easier.

I'd prefer not to put it in crypto/krb5. That could be construed not do belong there during a vendor import. If we are to create our own examples we should put them were people might intuitively look. Like /usr/share/examples/krb5 or a similar location. Remember src/crypto is the same as src/contrib except that it contains crypto. src/crypto are vendor imports. We should leave src/crypo for that purpose only.