Bug #99
If unable to connect to ripe DB glastopf doesn't write to DB
| Status: | Closed | Start date: | 11/19/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Lukas Rist | % Done: | 100% |
|
| Category: | Glastopf | Spent time: | 0.10 hour | |
| Target version: | - | |||
| Resolution: | fixed |
Description
If glastopf is running on a host behind a very restrictive firewall, which doesn't permit access to RIPE DB, it reports attacks to the logfile, but fails on writing the information into database.
In this case glastopf should at least write the information it could acquire so far into database.
IMHO it might be a good idea, to have the possibility to configure to whether or not access RIPE in the config file. Thus on secured systems it might be possible to do the RIPE stuff on another host in a more secure network.
History
Updated by Lukas Rist about 2 years ago
- Status changed from New to Closed
- Assignee set to Lukas Rist
- % Done changed from 0 to 100
- Resolution set to fixed
Fixed in r204