I'm all for doing what is necessary to spend more time on the core of OSSEC
functionality on Windows. OSSEC offers security folks a lot of powerful
features for dealing with logs and the OS itself. I'd rather see the time
spent developing those things more fully on the Windows side.
I'm dow
I love the idea of doing less in C. Most of this code doesn't even belong
in C IMO. Using something like powershell is probably the right answer to
this problem and will probably explore it at some point (unless of course
someone beats me to it) but even this solution requires tearing down the
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" wrote:
>
> You will never have to sell me on less code :)
>
> Code wins :) pull requests matter :) I might even t
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"
> 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 t
Suggestion. Break out the logic to cli only and then have the GUI call that.
This allows the dropping of the gui or not or moving it into the installer or a
lot of other options.
> On Sep 17, 2014, at 10:26 AM, "SoulAuctioneer"
> wrote:
>
> I want to do a lot of work on the Windows agent
ago, but
that’s because they were well documented and accurate.
Randy Dover
From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
Behalf Of SoulAuctioneer
Sent: Wednesday, September 17, 2014 11:31 AM
To: ossec-list@googlegroups.com
Subject: Re: [ossec-list] I want to get rid of
I will add it to my todo list as part of the work I'd like to do.
--
---
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 ossec-list+unsubscr...@googlegroups.com.
Fo
e with a Windows system and the
time/desire to contribute
> James Whittington
>
>
> -Original Message-
> From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
> Behalf Of dan (ddp)
> Sent: Wednesday, September 17, 2014 11:36
> To: ossec-list@googlegrou
r 17, 2014 11:36
To: ossec-list@googlegroups.com
Subject: Re: [ossec-list] I want to get rid of OSSEC's Windows GUI. What do
you think?
On Wed, Sep 17, 2014 at 11:23 AM, Michael Starks
wrote:
> On 2014-09-17 10:15, James M. Pulver wrote:
>>
>> If you're a Windows admin
On Wed, Sep 17, 2014 at 11:23 AM, Michael Starks
wrote:
> On 2014-09-17 10:15, James M. Pulver wrote:
>>
>> If you're a Windows admin who's afraid of the command line, I doubt
>> you'll be one for long. Doubly so if you can't do scripting...
>
>
> Maybe so, but why make someone's job more difficul
How many times does someone actually need to fire up the GUI to configure
something? We are probably only asking someone to figure out some command
line arguments once when they first configure the agent. Our documentation
should be the thing that helps them.
Something like "How to install Win
Don't get me wrong. I wouldn't mind keeping the GUI around. The problem is
the GUI creates a huge code base that isn't really well designed IMO and is
semi-buggy. There are enough problems on the Windows side already at the
core of what OSSEC does. I'd rather put the focus there than on some
no
On 2014-09-17 10:15, James M. Pulver wrote:
If you're a Windows admin who's afraid of the command line, I doubt
you'll be one for long. Doubly so if you can't do scripting...
Maybe so, but why make someone's job more difficult? I think his point
is that in the Windows world, a configuration GU
On Sep 17, 2014 11:09 AM, "Mauricio Tavares" wrote:
>
> On Wed, Sep 17, 2014 at 10:29 AM, James M. Pulver
wrote:
> > I'm perfectly happy to not have the GUI. I would like to keep the key
file
> > the same so my wrapper install script can just drop in the key.
> >
> While I prefer using conf
googlegroups.com] On
Behalf Of Mauricio Tavares
Sent: Wednesday, September 17, 2014 10:50 AM
To: ossec-list@googlegroups.com
Subject: Re: [ossec-list] I want to get rid of OSSEC's Windows GUI. What do you
think?
On Wed, Sep 17, 2014 at 10:29 AM, James M. Pulver wrote:
> I’m perfectly happy
On Wed, Sep 17, 2014 at 10:29 AM, James M. Pulver wrote:
> I’m perfectly happy to not have the GUI. I would like to keep the key file
> the same so my wrapper install script can just drop in the key.
>
While I prefer using config files and command line, the average
Windows user in general --
Yes. The key file's format will stay the same so anything existing for that
will not need to change. You should be able to use manage_agents.exe to
import the key programatically now as well. The hope is to do that atleast.
If it isn't possible now it should be.
--
---
You received this mess
On 09/17/2014 09:22 AM, SoulAuctioneer wrote:
> I want to do a lot of work on the Windows agent to try and make it
> better. One of the big changes I have planned is getting rid of the
> Windows GUI. In my opinion the GUI doesn't provide enough value to make
> it worth maintaining the fairly signif
I’m perfectly happy to not have the GUI. I would like to keep the key file the
same so my wrapper install script can just drop in the key.
--
James Pulver
CLASSE Computer Group
Cornell University
From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
Behalf Of SoulAuctioneer
20 matches
Mail list logo
