No aging needed. The token is generated once per owserver run and reused.
owserver only needs to see if a message is repeatedly coming in, and it
knows the direction (query or response) of the message.
On Fri, May 2, 2014 at 1:05 PM, Jerry Scharf wrote:
> Paul,
>
> If you let the sender set th
Great work! A quick test on my lab net indicates all fine!
/Johan
On 5/2/14 17:48 , Paul Alfille wrote:
> Thanks to quick testing by Stefano Miccoli and Johan Strom!
>
> Release Notes owfs 2.9p5
> 5/2/2014
>
> Fixes some show-stopper bugs in 2.9p4
> Fixes:
> 1. Token creation problem from Stefan
Paul,
If you let the sender set the limit and it's something like a 8 or 16
bit value, it is effectively not limited. If the entire internet can
work with 64 router hops, it is really hard for me to imagine that
owserver forwarding can't. With this, the state is in the forwarded
message rathe
Thanks to quick testing by Stefano Miccoli and Johan Strom!
Release Notes owfs 2.9p5
5/2/2014
Fixes some show-stopper bugs in 2.9p4
Fixes:
1. Token creation problem from Stefano Miccoli
2. Select when no DS2409 (Microlan hub) present
Found by Johan Strom
Redacted release 2.9p4:
Release Note
Yes, I chose the second approach (hash of some relatively unique data) just
to avoid arbitrary limits, even if they are unlikely to be exceeded in
actual use. That's a general design objective throughout owfs.
I'm amused that you designed just about the same scheme, including the
hash, that is act
Actually your second option is exactly what is implemented in 2.9p4, with the
md5 implementation from http://en.wikipedia.org/wiki/MD5#Simple_implementation,
see SetupAntiloop in module/owserver/src/c/owserver.c
My concerns about this approach are not linked to the security, but the
robustness
Paul,
If all you are trying to do is loop detection, there are a couple ways I
know to do it.
The simplest way to do it is a "time to live" field like IP does it.
Start it at some number (64 in standard for IP, but we would probably
want it to be lower) and every time you forward it, decreme
Hi,
after some testing it seems 2.9p4 is broken, on my lab net (DS9097u) no
devices appear at all when doing owdir. On my primary net (LinkUSB), the
search revealed some devices, but not all.. Reading did not seem
possible (something about device not on bus, but did not look closer
since I di
Good catch on the bug you patched.
I'd love to open a discussion of the UUID feature.
Let me state the problem area for background information:
1. owserver can be configured to send requests "upstream" -- to another
owserver
A. This is done at the command line or via a configuration file
B
