Re: [SSHGuard-users] Port update failed

[Jos C. <ssh...@cl...>]

I managed to install sshguard 2.0.0

sshguard-ipfw-1.7.1 is gone and is now sshguard 2.0.0

The only issue I now have is that I cannot retrieve in which file the 
blacklist is filled.

My old blacklist @ /var/db/sshguard/blacklist.db is still existing and 
ip addresses are blocked but not in that file?

Can you tell me where to find that list tab(22)?

thanks,

Jos


Op 20-7-2017 om 22:32 schreef Dan McGregor:
> On 2017-07-20 2:08 PM, Kevin Zheng wrote:
>> On 07/20/2017 11:56, Jos Chrispijn wrote:
>>> Just to let you know that something goes wrong with the recent port 
>>> update:
>>>
>>> ===>  Installing for sshguard-2.0.0
>>> ===>  Checking if sshguard already installed
>>> ===>   Registering installation for sshguard-2.0.0 as automatic
>>> Installing sshguard-2.0.0...
>>> pkg-static: sshguard-2.0.0 conflicts with sshguard-ipfw-1.7.1 (installs
>>> files into the same place).  Problematic file: /usr/local/sbin/sshguard
>>> *** Error code 70
>>>
>>> Stop.
>>> make: stopped in /usr/ports/security/sshguard
>> This is an issue on the port's side. I've CC'd the maintainer.
>>
>> You'll want to uninstall your old sshguard-ipfw using `pkg remove` and
>> then install the new one. Make sure you check the changelog and follow
>> any additional updating instructions.
>>
>> pkg here is getting confused by the different origins (that went away
>> when 2.0 came around). I'm not sure what the best way to solve that is.
>>
>
> I'm not sure of the best way either. I removed the subports (for 
> -ipfw, -pf, etc) when 2.0 came around because 2.0 can install more 
> than one backend, so perhaps an UPATING entry to warn users? You'll 
> also want to edit the sshguard.conf file in /usr/local/etc/sshguard.conf.

-- With both feed on the ground you will never make a step forward