kclient version 2 [PSARC/2007/401 FastTrack timeout 07/13/2007]

[Roland Mainz]

James Carlson wrote:
> Wyllys Ingersoll writes:
> > -t: configure a simple broadcast/multicast NTP client
> 
> Why is this part of kclient?  Though having a tool to administer NTP
> clients would probably be helpful (and having it tied into something
> like DHCP and thus automatic would be much more helpful still), it
> seems out of place here.

Ugh... since when it is recommended to mix untrusted services like DHCP
with Kerberos5 ?

> > -T kdc_vendor: specify the KDC of the client to be of kdc_vendor.  Supported
> > vendors are currently:
> >       ms_ad: Microsoft Active Directory
> >       mit: MIT KDC server
> >       heimdal: Heimdal KDC server
> >       shishi: Shishi KDC server
> 
> Why does the user have to specify this?  Is there no way for the
> client implementation to detect the proper KDC variant to use?

Erm, AFAIK this will end like the HTTP's "User-Agent:" - you cannot rely
on the value since the submitter may change it intentionally in some
cases to emulate other clients (for example Mozilla/FireFox allows to
set the "User-Agent:" string to any value and other browsers like
Konqueror have a sophosticated feature to set a specific User-Agent
value per domain or URL).
IMO it would be nice to keep such an option around...

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)