* sven falempin sven.falem...@gmail.com [2013-09-11 22:30]:
At his point struct pf_state **sm is available.
Lets assume pf_state got a struct pf_osfp_enlist l_osfp
To get back the info from userland, doing
Would a diff like this hurts ??
everything that grows the state hurts (last not
On Thu, Sep 12, 2013 at 2:50 AM, Henning Brauer
lists-openbsdt...@bsws.dewrote:
* sven falempin sven.falem...@gmail.com [2013-09-11 22:30]:
At his point struct pf_state **sm is available.
Lets assume pf_state got a struct pf_osfp_enlist l_osfp
To get back the info from userland, doing
If I want this on FreeBSD i am alone, but here...
So this code check the fingerprint, and does not bother to save it, because
it is never used , and that s good :-)
I read the code a bit:
pf.c : around line 3232
- - - - - -
case IPPROTO_TCP:
PF_TEST_ATTRIB(((r-flagset th-th_flags) !=
* sven falempin sven.falem...@gmail.com [2013-09-05 18:14]:
Reading pfctl manual and net/pfvar.h i didnt find the ospf information
inside a states entry .
So i assume it is not possible to recover the fingerprint of a state trough
the ioctl.
otoh this is the case.
- creatorId is something i
openBSDs,
Reading pfctl manual and net/pfvar.h i didnt find the ospf information
inside a states entry .
So i assume it is not possible to recover the fingerprint of a state trough
the ioctl.
Unless
- i didnt read enough (help is welcome)
- creatorId is something i hould look into.
or i have to
