I should note I know not a single thing about windows :) let alone cmdlets, powershell, and what is this mmc magic you all speak of.
> On Sep 17, 2014, at 9:55 PM, "Jeremy Rossi" <[email protected]> wrote: > > You will never have to sell me on less code :) > > Code wins :) pull requests matter :) I might even take a look see at the > code. Hey powershell is popular now. And can do GUIs and is much easier > then c. So what about ossec cmdlets? > >> On Sep 17, 2014, at 9:21 PM, "SoulAuctioneer" <[email protected]> >> wrote: >> >> Good suggestion but I just think the GUI does more than it needs to. >> Especially with the service management. Keeping that code around and >> building it into the CLI just isnt' worth it to me. Easy enough to do with >> mmc or existing CLI tools most Windows Administrators know and love. >> >> If you take that away you are left with some quick links to help and version >> information and key importation. Key importation can be made available VIA >> CLI (should already be there) and the rest can be done with Windows >> shortcuts. >> >> We could keep the GUI around build it on top of the CLI tools but frankly >> that is a lot of work and and time and again I'd rather spend that on other >> things right now. We can possibly bring the GUI back when the code base is >> ready and the Windows agent as a whole is ready. >> >> In other words... easier said than done :) >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "ossec-list" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
