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
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
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,
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
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
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
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 sch...@lagunawayconsulting.com
wrote:
Paul,
Thanks for including my suggestions in p4!I found a small bug in the new antiloop code (module/owserver/src/c/owserver.c) please see the attached patch.Stefano
diff --git a/module/owserver/src/c/owserver.c b/module/owserver/src/c/owserver.c
index 374f64a..0f08913 100644
---
Hi Paul,
Thanks a lot, I'll give it a whirl as soon as I can (read: early next week
the earliest) and report back.
br,
Ors
On Wed, Apr 30, 2014 at 2:35 AM, Paul Alfille paul.alfi...@gmail.comwrote:
Release Notes owfs 2.9p4
4/30/2014
New features
1. Switch to git for source management
Hi,
big up for git.. :)
Compiles fine on FreeBSD now, without any extra patches! Haven't tried
to use it yet though. If it works OK I will probably submit the owfs
port to the ports system.
/Johan
On 4/30/14 02:35 , Paul Alfille wrote:
Release Notes owfs 2.9p4
4/30/2014
New features
1.
Release Notes owfs 2.9p4
4/30/2014
New features
1. Switch to git for source management
Still hosted on sourceforge.net
git clone git://git.code.sf.net/p/owfs/code owfs-code
cvs history brought over.
2. Clean and test DS2409 (Microlan) hubs
Addressing problem found by Ors Tiszay
Works well with
Hello!
SF delivers both Git and CVS and probably SVN (still) and probably any
others we can dream up. So when was CVS depreciated? I believe I
managed to update the CVS one last night, and even tried to build the
P3 release of 2.9 on my Slackware 13.37 system. (Currently the only
one running.) It
Hi Gregg,
The transition (cvs-git) was recent (a couple of weeks). The biggest
barrier was teaching an old dog (me) new tricks.
You are right, there are many source management systems available, but it
adds complexity to use them simultaneously.
cvs was working fine, and I had some nice
nice :)
there's a github like site at source forge?
2014-04-29 22:07 GMT-03:00 Paul Alfille paul.alfi...@gmail.com:
Hi Gregg,
The transition (cvs-git) was recent (a couple of weeks). The biggest
barrier was teaching an old dog (me) new tricks.
You are right, there are many source
14 matches
Mail list logo
