new port: sshguard-ipfw

[nefar@…]

Protects hosts from brute force attacks against ssh and other services using ipfw

[nefar@…]

If there's a better way of doing the startupitems, let me know. I've tested this and it works fine, but it ain't pretty.

[jpmat296@…]

Thanks nefar. I have used your Portfile without any problem.

[danielluke (Daniel J. Luke)]

1.5 should be out soon, and with LogSucker it can be configured using startupitem.executable instead of start/stop which cleans this up a bit

[nefar@…]

riiight, because after waiting 4 months for this port to be committed, someone is going to be very happy to spend the time and submit a new updated port version... which won't get submitted either...

[danielluke (Daniel J. Luke)]

Replying to nefar@…:

riiight, because after waiting 4 months for this port to be committed,

It happens sometimes (all volunteer project, you know).

Often the person submitting the port will need to ping the mailing list in order to get attention from a committer who has time to review the port.

someone is going to be very happy to spend the time and submit a new updated port version...

... which you would probably be doing anyway because you put yourself as the maintainer for the port ;-)

which won't get submitted either...

It will. I'm interested in this port since I use sshguard now and noticed that this ticket was here (because it's linked to from the sshguard website).

If you're still interested in maintaining the port, let me know (and if you're not, please let me know that too).

[nefar@…]

Since this really isn't the forum to keep this discussion going, let's just say that I'm interested in maintaining the port should it start being committed.

[danielluke (Daniel J. Luke)]

port added in r64382

I changed startupitem.stop a bit so that it only needs one grep. Feel free to ping me when you update this port so that it gets committed (at least until you apply for and get commit access).