NC_Net v2.15 - New Version (with Perfomance counter FIX)

[Anthony Montibello]

That is true,  However my concern about adding encryption to check_nt
is how to implement it so that the TCP listener port of NC_Net does
not loose backwards compatibility with older versions of check_nt.
(this is a part of my original requirements goals of NC_Net being a
drop in replacement for NS_Client)


About the level of complexity for the conversion; this would be
moderate. It did take over full week to get the Xor running when I
converter send_NSCA to c#.  This is mostly due to c# being more like
Java than C in both semantics and syntax.  Once some of the current
objective are met, I can look into adding encryption to the
check_nt/NC_Net port while still maintaining its backwards
compatibility.



On Fri, 11 Feb 2005 10:10:05 +0100, Andreas Ericsson <ae at op5.se> wrote:
> Anthony Montibello wrote:
> > I am not sure how I would be able to add non-plaintext authentication
> > scheme to this command at this time.  How would this be implemented
> > into check_nt? because check_NT uses plain only.
> >
> 
> But nsca is able to select from a wide range of different ciphers. It
> wouldn't be an overwhelming feat to add that same sort of encryption to
> check_nt (although a bit timeconsuming).
> 
> >>--
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Lead Developer
> >>
Thanks for the advise,
Tony


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null