Re: [Sshguard-users] Patch to fix blacklist loading with ipfw

[Kevin Z. <kev...@gm...>]

Hi Greg,

You should consider checking out the latest sources from the Bitbucket
repository. That might be easier to work with than running from ports.

On 05/26/2015 21:34, Greg Putrich wrote:
> While sshguard was still running, confirmed it did not add the entry. Then I 
> stopped sshguard. I copy & pasted the command from the log and it went in
> without issue. 

This seems odd.

> Copied a blacklist.db file with 213 entries. Upon start, it attempted to 
> insert, but failed. It made a long command, but was chopped off on the 
> 67th IP address (that address had its last digit cut off). and there are 
> still 146 more after that one that never made the list. 

I'm not entirely certain why it was truncated, either.

> The latter command clearly could not be added as it was truncated. However,
> unsure why it didn't like the first one.

If anything, I think this is an indication that the current `ipfw`
backend is unsalvagable and should be replaced with the command
framework thing. I'll start taking a closer look at that.

It would end up being similar to how `pf` is currently handled: you
create a table 'sshguard', then SSHGuard would be responsible for adding
and removing addresses from the table. This means that SSHGuard wouldn't
have to fiddle with rule numbers. Thoughts?

Thanks,
Kevin Zheng

-- 
Kevin Zheng
kev...@gm... | ke...@kd... | PGP: 0xC22E1090