Hi,
I just found the same bug while I was trying to connect to the iodined
from a debian stable using the iodine client from the source code
(version 0.5.1).
I have seen in the code, that it checks the version number, but it isn't
done correctly. I know that the last version of this code have
On Sun, 26 Apr 2009 13:05:20 +0200, Albert Sellarès wrote:
I have seen in the code, that it checks the version number, but it isn't
done correctly. I know that the last version of this code have solved
this issue, but the current version in debian stable has this bug, and
it is very
On Fri, 27 Mar 2009 10:11:02 +0100, martin f krafft wrote:
My suspicion is that you are running an iodine 5.x client against
an iodined 4.x server -- is that true?
Yes, good analysis. Silly that I didn't think of it. :)
:)
Well, it's not really obvious without clear documentation/error
also sprach gregor herrmann gre...@debian.org [2009.03.26.1712 +0100]:
My suspicion is that you are running an iodine 5.x client against
an iodined 4.x server -- is that true?
Yes, good analysis. Silly that I didn't think of it. :)
* check if my suspicion with the protocol discrepancy is
Package: iodine
Version: 0.4.2-1
Severity: important
When iodined starts
iodined -f -DDD -u iodine -t /var/run/iodine -P foo -l
130.60.75.73 192.168.254.245 r.neokon.ch
and a client connects, iodined segfaults. strace is attached. I can
reproduce at will but don't really know what other
On Thu, 26 Mar 2009 10:32:42 +0100, martin f krafft wrote:
When iodined starts
iodined -f -DDD -u iodine -t /var/run/iodine -P foo -l
130.60.75.73 192.168.254.245 r.neokon.ch
and a client connects, iodined segfaults. strace is attached. I can
reproduce at will but don't really know
6 matches
Mail list logo
