Re: enable/disable features in running configuration
Alexandre Cassen <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Patrick, Any option are open, as netop guy mainly I am used to play with CLI, that is the way most of us are conditioned to play around :D, but for sure every options are open. Please feel free to discuss and bring idea here. But we are all on the same line of saying, current conf parser MUST be changed… My main constraint is not to rely on any third party lib as much as possible, that is my only constraint. cheers, Alexandre > On 02 May 2015, at 20:17, Patrick Schaaf <[email protected]> wrote: > > Am 02.05.2015 18:24 schrieb "Alexandre Cassen" <[email protected] <mailto:[email protected]>>: > > > > What is great with CLI/VTY, IMHO, is the fact that client to access is really simple and widely supported on every OS (telnet). > > Hi, > > I hope telnet (TCP on localhost) will not be the only alternative. Unix domain sockets would be preferred. For TCP, do you tack on some kind of ad hoc authentication? I think keepalived is quite often deployed on hosts that also run internet facing non-root processes (think apache), and a nonauthenticated TCP interface would open a path for a hacked non-root apache process to command the root-run keepalived process. > > best regards > Patrick > ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Keepalived-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/keepalived-devel