On 10/27/2011 03:28 AM, carlopmart wrote:
On 10/27/2011 01:55 AM, Michael Starks wrote:
On 10/26/2011 07:15 AM, carlopmart wrote:
b) Ability to use agent collectors. For example for remote locations,
one server acts a collector for a remote LAN and forwards all alerts,
logs, etc to the central
On 10/27/2011 01:55 AM, Michael Starks wrote:
On 10/26/2011 07:15 AM, carlopmart wrote:
b) Ability to use agent collectors. For example for remote locations,
one server acts a collector for a remote LAN and forwards all alerts,
logs, etc to the central OSSEC server.
You should be able do this
On 10/26/2011 01:36 PM, dan (ddp) wrote:
On Wed, Oct 26, 2011 at 1:47 PM, James M Pulver wrote:
Well, not silently, it still pops up a command window for a second in my
experience.
If you can help fix that, it'd be appreciated.
If I recall correctly, I actually had it working completely s
On 10/26/2011 07:15 AM, carlopmart wrote:
b) Ability to use agent collectors. For example for remote locations,
one server acts a collector for a remote LAN and forwards all alerts,
logs, etc to the central OSSEC server.
You should be able do this now. Install a manager in one of your
downstre
On 10/26/2011 10:46 AM, sami zimbra wrote:
Hi,
I have noticed a problem when i was looking if OSSEC can meet PCI-DSS
requirements on detecting malicious modifications of log files 10.5.5.
The problem is that ossec-logcollector do it automatically and randomly
without any user contrôl over this b
Please also consider adding a /? and other command line parameter options for
installing Windows clients so that users don't have to go digging for help. It
also seems silly to not be able to specify a server address and key on the
command line during installation, and to not know if this opt
On Wed, Oct 26, 2011 at 3:56 PM, carlopmart wrote:
> On 10/26/2011 08:33 PM, dan (ddp) wrote:
>>
>> Please excuse my ignorance. I'll take notes. :)
>>
>> On Wed, Oct 26, 2011 at 8:15 AM, carlopmart wrote:
>>>
>>> On 10/26/2011 01:00 PM, Michael Starks wrote:
List the most annoying bugs.
On 10/26/2011 08:33 PM, dan (ddp) wrote:
Please excuse my ignorance. I'll take notes. :)
On Wed, Oct 26, 2011 at 8:15 AM, carlopmart wrote:
On 10/26/2011 01:00 PM, Michael Starks wrote:
List the most annoying bugs. What makes OSSEC difficult to use? What is
the biggest area for improvement?
his option is
> available.
>
> -Original Message-
> From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
> Behalf Of Michael Starks
> Sent: Wednesday, October 26, 2011 10:19 AM
> To: ossec-list@googlegroups.com
> Subject: RE: [ossec-list] 3WoO Day 4: W
Please excuse my ignorance. I'll take notes. :)
On Wed, Oct 26, 2011 at 8:15 AM, carlopmart wrote:
> On 10/26/2011 01:00 PM, Michael Starks wrote:
>>
>> List the most annoying bugs. What makes OSSEC difficult to use? What is
>> the biggest area for improvement? What are we missing? Any rules fp t
On Wed, Oct 26, 2011 at 8:21 AM, James M Pulver wrote:
> The biggest problem for me was the need to write scripts to deploy the
> agents, specifically on Windows clients. I expect the new auth-d would work
> on Linux but didn't seem to be supported on Windows.
>
Have you tried the post 2.6 Wind
P Computer Group
> Cornell University
>
>
> -Original Message-
> From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
> Behalf Of Michael Starks
> Sent: Wednesday, October 26, 2011 1:19 PM
> To: ossec-list@googlegroups.com
> Subject: RE: [ossec-list
er 26, 2011 10:19 AM
To: ossec-list@googlegroups.com
Subject: RE: [ossec-list] 3WoO Day 4: What bugs you: problems, challenges and
room for improvement.
On Wed, 26 Oct 2011 15:49:33 +, Brown, Ryan David wrote:
> Lack of Windows command line install parameters and quiet install
> makes i
On Wed, 26 Oct 2011 17:47:19 +, James M Pulver wrote:
Well, not silently, it still pops up a command window for a second in
my experience.
Ok, non-interacively. :) I actually tried to make that go away but it
caused problems. Something for another day...
--
Michael Starks
[I] Immutable S
Michael Starks
Sent: Wednesday, October 26, 2011 1:19 PM
To: ossec-list@googlegroups.com
Subject: RE: [ossec-list] 3WoO Day 4: What bugs you: problems, challenges and
room for improvement.
On Wed, 26 Oct 2011 15:49:33 +, Brown, Ryan David wrote:
> Lack of Windows command line install paramet
On Wed, 26 Oct 2011 15:49:33 +, Brown, Ryan David wrote:
Lack of Windows command line install parameters and quiet install
makes it difficult/annoying to install for large organizations. This
is likely a deal-breaker for lots of large Windows shops.
The Windows agent can be installed silen
Lack of Windows command line install parameters and quiet install makes it
difficult/annoying to install for large organizations. This is likely a
deal-breaker for lots of large Windows shops.
On 10/26/2011 01:00 PM, Michael Starks wrote:
> List the most annoying bugs. What makes OSSEC diffic
Hi,
I have noticed a problem when i was looking if OSSEC can meet PCI-DSS
requirements on detecting malicious modifications of log files 10.5.5. The
problem is that ossec-logcollector do it automatically and randomly without
any user contrôl over this behavior.
It will be appreciated to add some
On 10/26/2011 01:00 PM, Michael Starks wrote:
List the most annoying bugs. What makes OSSEC difficult to use? What is
the biggest area for improvement? What are we missing? Any rules fp too
much? Now is the time to get it all out.
--
Michael Starks
[I] Immutable Security
http://www.immutablesecu
The biggest problem for me was the need to write scripts to deploy the agents,
specifically on Windows clients. I expect the new auth-d would work on Linux
but didn't seem to be supported on Windows.
The second thing for me is the difficulty of getting the logs viewable in some
web based method
20 matches
Mail list logo
