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 what other info to provide > right now.
Thanks for the bug report, and that's indeed nasty.
My suspicion is that you are running an iodine 5.x client against an
iodined 4.x server -- is that true?
I tried now by starting the 0.4.2 server and connecting with the 0.5.1
client, and the result looks looks yours:
[..]
select(5, [4], NULL, NULL, {1, 0}) = 1 (in [4], left {0, 920000})
recvfrom(4, "\374\226\0\0\0\1\0\0\0\0\0\0\vVaaaakaaaaa\6tunnel\6c"..., 65536,
0, {sa_family=AF_INET, sin_port=htons(59285),
sin_addr=inet_addr("195.34.133.10")}, [16]) = 51
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
(With the 0.5.1 client against the 0.5.1 server evreything is fine.)
I'm not surprised that the protocols are not compatible but what
suprises me is
* that I don't find the documentation for the behaviour at the moment
(ok, later I saw in my svn log that I added and removed in in/from
README.Debian but forgot about it with the 5.x release)
* that the client doesn't spit out a warning although there are some
lines in the code that check the protocol versions. Ok, the server
probably segfaults _before_
Could you please
* check if my suspicion with the protocol discrepancy is true?
* maybe try with a 5.x version on the server?
I will add the note to README.Debian again, and I can also create a
backport package after the package I'm going to upload later hits
testing.
Any other ideas?
Cheers,
gregor
--
.''`. Home: http://info.comodo.priv.at/{,blog/} / GPG Key ID: 0x00F3CFE4
: :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/
`. `' Member of VIBE!AT, SPI Inc., fellow of FSFE | http://got.to/quote/
`- NP: U2: Unchained Melody (live bootleg
signature.asc
Description: Digital signature
