[35981] in Kerberos

home help back first fref pref prev next nref lref last post

Re: ping for kdc utility?

daemon@ATHENA.MIT.EDU (Wang Shouhua)
Wed Apr 2 15:50:55 2014

MIME-Version: 1.0
In-Reply-To: <alpine.GSO.1.10.1404021544190.21026@multics.mit.edu>
Date: Wed, 2 Apr 2014 21:50:36 +0200
Message-ID: <CANzOW+KSEOtpp14+SErRSERpR_fQJy32zi8rwfj3Msf4txyFtw@mail.gmail.com>
From: Wang Shouhua <shouhuaw@gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: kerberos@mit.edu
Content-Type: multipart/mixed; boundary="===============1901012611=="
Errors-To: kerberos-bounces@mit.edu

--===============1901012611==
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit

On 2 April 2014 21:46, Benjamin Kaduk <kaduk@mit.edu> wrote:
> On Wed, 2 Apr 2014, Wang Shouhua wrote:
>
>> Is there such an utility which can issue a "ping" (null command) to
>> the kdc to see if it is still responding?
>
>
> I'm not aware of a dedicated utility.  However, the KDC is basically a
> stateless UDP service, so recording a live transaction and replaying an
> input packet is expected to yield some sort of response packet.  Doing this
> periodically allows for a very primitive "liveness check" which can be used
> in some monitoring setups.  Of course, if one wants to monitor that the KDC
> is actually functioning properly and not just spewing error packets, more
> effort is required.

Does the Kerberos5 core protocol have a 'null' operation?

Wang
-- 
Wang Shouhua - shouhuaw@gmail.com
中华人民共和国科学技术部 - HTTP://WWW.MOST.GOV.CN


--===============1901012611==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

--===============1901012611==--

home help back first fref pref prev next nref lref last post