[Bro-Dev] #536: protocols/ssh and geoip problems

Bro Tracker bro at tracker.bro-ids.org
Thu Aug 4 20:47:07 PDT 2011

#536: protocols/ssh and geoip problems
  Reporter:  gregor   |      Owner:
      Type:  Problem  |     Status:  new
  Priority:  Normal   |  Milestone:  Bro1.6
 Component:  Bro      |    Version:  git/master
Resolution:           |   Keywords:

Comment (by gregor):

 >  >  Looks like that's because it's expecting to use a City database, but
 >  >  finding it?  The GeoLiteCity database usually has to be downloaded
 >  >  manually, more info here:
 >  I've been meaning to get to that, it's fine to not have the city
 >  but we need to make sure that we don't try to capture city information
 >  we didn't end up loading the city database.  We just need to check the
 >  loaded database with the GeoIP_database_edition function.

 It would also be great if we could prevent libgeoip from printing stuff
 directly on stderr. That's annoying.

 And, calling lookup_location() without geoip support enabled will yield an
 error. If we use lookup_location() in any of the new default policy
 scripts, we should suppress this error.

Ticket URL: <http://tracker.bro-ids.org/bro/ticket/536#comment:3>
Bro Tracker <http://tracker.bro-ids.org/bro>
Bro Issue Tracker

More information about the bro-dev mailing list