Mailinglist Archive: opensuse-security (396 mails)
| < Previous | Next > |
Re: [suse-security] SuSEfirewall2 Logging Options
- From: Lars Ellenberg <l.g.e@xxxxxx>
- Date: Fri, 10 Jan 2003 12:56:56 +0100
- Message-id: <20030110115656.GD1313@minna>
On Sat, Jan 11, 2003 at 02:44:03AM -0500, Andrew Longstreet wrote:
> Here is my dilemma.
>
> I currently have 9 SuSE 7.3 boxes logging to a centralized, remote
> syslog-ng daemon.
> I have a postgres database operating, some scripts running to insert
> incoming messages into the postgres database.
> All works fine.
>
> Now, I am trying to securely publish some of this firewall logging for
> my clients.
> My postgres skills are weak, so on the backend I have sucked a bunch
> of data into MS Access2000 through 32 ODBC connect to postgres.
uh. well, whatever you feel comfortable with 8-/
seems like you have plenty of idle resources ...
> The problem is Access only supports a field of 255. The mesg_txt field
> is longer than this on some records, in the mesg_txt field from
> postgres.
OT here ;)
not exactly true. we did work with text fields up to several kB.
something similar to BLOBs, but I cannot remember the exact type
definition in postgress, nor in access.
maybe you should ask some MSAccess and/or postgress list?
or google for "access postgres blob" or some such...
... or use perl.
> Can I change some options on the SuSEfirewall2 log parameter to log a
> little less info (TTL, maybe MAC addr. etc) ?
don't think so, but I may be wrong.
Lars
> Here is my dilemma.
>
> I currently have 9 SuSE 7.3 boxes logging to a centralized, remote
> syslog-ng daemon.
> I have a postgres database operating, some scripts running to insert
> incoming messages into the postgres database.
> All works fine.
>
> Now, I am trying to securely publish some of this firewall logging for
> my clients.
> My postgres skills are weak, so on the backend I have sucked a bunch
> of data into MS Access2000 through 32 ODBC connect to postgres.
uh. well, whatever you feel comfortable with 8-/
seems like you have plenty of idle resources ...
> The problem is Access only supports a field of 255. The mesg_txt field
> is longer than this on some records, in the mesg_txt field from
> postgres.
OT here ;)
not exactly true. we did work with text fields up to several kB.
something similar to BLOBs, but I cannot remember the exact type
definition in postgress, nor in access.
maybe you should ask some MSAccess and/or postgress list?
or google for "access postgres blob" or some such...
... or use perl.
> Can I change some options on the SuSEfirewall2 log parameter to log a
> little less info (TTL, maybe MAC addr. etc) ?
don't think so, but I may be wrong.
Lars
| < Previous | Next > |