Re: [AMaViS-user] p0f & sql

2007-03-15 Thread Alan Munday
Mark Martinec wrote the following on 16/12/2006 01:35: > Alan, > >> In 2.4.4 I've uncommented the "# , p0f=?" in the sql statement. As this is >> not logging into the p0f field in msgs I presumed some additional changes >> are still required? > > The ->execute part of the patch is needed too. >

Re: [AMaViS-user] p0f & sql

2006-12-15 Thread Mark Martinec
Alan, > In 2.4.4 I've uncommented the "# , p0f=?" in the sql statement. As this is > not logging into the p0f field in msgs I presumed some additional changes > are still required? The ->execute part of the patch is needed too. Here is the same patch, but made against 2.4.4: --- amavisd~Mon

Re: [AMaViS-user] p0f & sql

2006-12-15 Thread Alan Munday
Mark Martinec wrote the following on 17/10/2006 13:51: > > You mean how to store p0f fingerprint to SQL logging database? > > Try the following: > > - add a field 'p0f' to table msgs: > ALTER TABLE msgs ADD p0f varchar(255) DEFAULT ''; > > - and apply the following change to amavisd: > >

Re: [AMaViS-user] p0f & sql

2006-10-17 Thread Alan Munday
Mark Martinec wrote the following on 17/10/2006 15:47: > Alan, > >> I was trying to make sure I understood how you implemented >> $policy_bank{'MYNETS'}{os_fingerprint_method} = undef; >> when the policies are in SQL tables. > > Don't mix policy banks with SQL lookup policy table. There is

Re: [AMaViS-user] p0f & sql

2006-10-17 Thread Mark Martinec
Alan, > I was trying to make sure I understood how you implemented > $policy_bank{'MYNETS'}{os_fingerprint_method} = undef; > when the policies are in SQL tables. Don't mix policy banks with SQL lookup policy table. There is an unfortuate similarity in names, but these are two unrelated con

Re: [AMaViS-user] p0f & sql

2006-10-17 Thread Alan Munday
Mark Martinec wrote the following on 17/10/2006 14:55: > Alan, > >> I was checking if a field needs to be added to the policy table so that >> sql_select_policy would handle os_fingerprint_method as required. > > No new fields are needed in SQL tables in order for p0f to work. > > See RELEASE_NO

Re: [AMaViS-user] p0f & sql

2006-10-17 Thread Mark Martinec
Alan, > I was checking if a field needs to be added to the policy table so that > sql_select_policy would handle os_fingerprint_method as required. No new fields are needed in SQL tables in order for p0f to work. See RELEASE_NOTES, search for where p0f was introduced. Mark --

Re: [AMaViS-user] p0f & sql

2006-10-17 Thread Alan Munday
Mark Martinec wrote the following on 17/10/2006 13:51: > Alan, > >> Has anyone posted information on how to update the (my)sql tables to >> support p0f? > > You mean how to store p0f fingerprint to SQL logging database? > > Try the following: > > - add a field 'p0f' to table msgs: > ALTER T

Re: [AMaViS-user] p0f & sql

2006-10-17 Thread Mark Martinec
Alan, > Has anyone posted information on how to update the (my)sql tables to > support p0f? You mean how to store p0f fingerprint to SQL logging database? Try the following: - add a field 'p0f' to table msgs: ALTER TABLE msgs ADD p0f varchar(255) DEFAULT ''; - and apply the following chang

[AMaViS-user] p0f & sql

2006-10-17 Thread Alan Munday
Has anyone posted information on how to update the (my)sql tables to support p0f? thanks Alan - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technolog