Having problems running two different kinds of authentiation on the same client?

I am trying to connect to two different NTP Servers, each using a
different type of authentication (one uses IFF, the second GQ).

The IFF connection works fine, but the GQ never seems to connect.

If I remove all of the IFF keys, the GQ works fine.

Is there a limitation that NTPD can only use one type of authentication
at a time?

Michael



This message is confidential to Prodea Systems, Inc unless otherwise indicated
or apparent from its nature. This message is directed to the intended recipient
only, who may be readily determined by the sender of this message and its
contents. If the reader of this message is not the intended recipient, or an
employee or agent responsible for delivering this message to the intended
recipient:(a)any dissemination or copying of this message is strictly
prohibited; and(b)immediately notify the sender by return message and destroy
any copies of this message in any form(electronic, paper or otherwise) that you
have.The delivery of this message and its information is neither intended to be
nor constitutes a disclosure or waiver of any trade secrets, intellectual
property, attorney work product, or attorney-client communications. The
authority of the individual sending this message to legally bind Prodea Systems
is neither apparent nor implied,and must be independently verified.
_______________________________________________
questions mailing list
questions@xxxxxxxxxxxxx
https://lists.ntp.org/mailman/listinfo/questions

.

Relevant Pages

  • Re: Having problems running two different kinds of authentiation on the same client?
    ... I verified IFF and GQ work here, but don't run both in the same box. ... This message is directed to the intended recipient only, who may be readily determined by the sender of this message and its contents. ... If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient:any dissemination or copying of this message is strictly prohibited; andimmediately notify the sender by return message and destroy any copies of this message in any formthat you have.The delivery of this message and its information is neither intended to be nor constitutes a disclosure or waiver of any trade secrets, intellectual property, attorney work product, or attorney-client communications. ...
    (comp.protocols.time.ntp)
  • Private certificate authentication
    ... Certificates for authentication of NTP servers (or can write a quick ... This message is directed to the intended recipient ... authority of the individual sending this message to legally bind Prodea Systems ...
    (comp.protocols.time.ntp)
  • Re: symmetric-active mode (peer) and autokey
    ... Finally I got TC and even IFF working, but it took me a lot of trial and error: ... but authentication would never complete. ... too restrictive capability set. ... Where is the right place to put the leapseconds file? ...
    (comp.protocols.time.ntp)
  • SMTP Authenticated Relay
    ... there's no authentication. ... privileged information. ... If you are not the intended recipient, ... and permanently delete this message and any attachments. ...
    (RedHat)