Summary: | [patch] security/fwknop new version 2.6.6 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Jens Grassel <freebsd-ports> | ||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | cs, sean.greven | ||||
Priority: | --- | Keywords: | patch | ||||
Version: | Latest | Flags: | sean.greven:
maintainer-feedback+
|
||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Comment on attachment 159386 [details]
Patch for the fwknop port directory.
The patch applies and fwknop compiles. I am interested to know whether you have tested it with pf
(In reply to sean.greven from comment #1) Actually my whole motivation for bringing the port up to 2.6 is to be able to use it with pf. ;-) But I haven't tested this currently. It seems not to break the ipfw stuff and I wanted to give pf a shot after the port is upgraded. According to the fwknop people it should work. Could this be applied to the ports? (In reply to Jens Grassel from comment #3) Hi Jens I have prepared the upgrade to 2.2.7, Will submit the change PR. Regards Sean New PR 203168 submitted for port upgrade to latest version - This PR should be closed |
Created attachment 159386 [details] Patch for the fwknop port directory. Hi, I just updated fwknop to the current version (2.6.6) so far no issues were encountered by me. Regards, Jens