[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debian shishi package bug

From: Simon Josefsson
Subject: Re: Debian shishi package bug
Date: Sat, 22 Apr 2006 12:02:54 +0200
User-agent: Gnus/5.110005 (No Gnus v0.5) Emacs/22.0.50 (gnu/linux)

Russ Allbery <address@hidden> writes:

> Russ Allbery <address@hidden> writes:
>> I'll take a look and see about getting the packages uploaded tomorrow.
> shishid appears to be broken, at least on my system, and I'm not sure how
> to fix it.  In the current package, the init script starts the daemon in
> the foreground and it just hangs until one types Ctrl-D.  It then dies and
> the boot process continues.  Using --background fixes this, but shishid
> just starts and immediately exits.  It spits out the following in syslog:
> Apr 20 19:09:08 wanderer /usr/sbin/shishid: Starting (GNUTLS `1.2.9')
> Apr 20 19:09:08 wanderer /usr/sbin/shishid: Listening on IPv6:*:kerberos/udp 
> socket 0 
> Apr 20 19:09:08 wanderer /usr/sbin/shishid: Listening on IPv4:*:kerberos/tcp 
> socket 4 
> Apr 20 19:09:08 wanderer /usr/sbin/shishid: Listening on IPv4:*:kerberos/udp 
> socket 5 
> Apr 20 19:09:08 wanderer /usr/sbin/shishid: Error reading from 
> IPv6:*:kerberos/udp on socket 0 (-1): Unknown error 4294967295
> Apr 20 19:09:08 wanderer /usr/sbin/shishid: Closing IPv6:*:kerberos/udp 
> socket 0
> before it disappears.

I've fixed this, so shishid should not crash now.

I'm beginning to rethink the idea of disabling shishid by default, I'd
like for 'apt-get install shishid' to install a working and fully
configured shishi KDC.  One of my ideas with shishi is that every
machine run its own KDC, and if you have a few more machines, you pool
them together using cross-realm trust.  But maybe we can revisit this
later on, too...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]