krb5

[Earl Killian]

Thank you for further detail. I wish that gethostname returned a FQDN,
but since I don't know the reason that people have decided that it not
do so, I probably shouldn't go that route.

I think the problem arises from glibc implementing
gethostname/getdomainname using uname(2), and that seems difficult to
change now.

I suppose you could add something to krb5.conf to provide the default
value to append to what gethostname() returns, but that seems not
sufficiently flexible to be worth the complication. Since krb5.conf is
per-machine, I suppose you could just have it specify the host principal
to use, and ignore gethostname() altogether.

-Earl

On 10/18/17 17:42, Greg Hudson wrote:
> On 10/17/2017 06:04 PM, Earl Killian wrote:
>> However, I would like to inquire
>> of the mailing list how things are supposed to work when those are set
>> to false as in the openSUSE distro.
> Not as easily as I would like.  For the specific issue you mention, I
> think the only two workarounds are:
>
> 1. Create a principal "host/alpha" and put it in keytabs and ACL files
> alongside "host/alpha.killian.com".
>
> 2. Arrange for gethostname() to return the FQDN (alpha.killian.com)
> instead of just "alpha".  This might have undesirable side effects as it
> would be a system-wide change.
>
> POSIX does not make it easy to get this right without risking using
> insecure DNS, although there are some improvements we could make (such
> as looking to see if there is exactly one search domain in _res.dnsrch,
> and expanding single-component hostnames using that domain if so).