| Re: [leshan-dev] Strange exception? |
|
Hello Kraus
Yes, a server with debug output (that outputs intermediate steps) can definitely provide a lot of help, since you can compare steps and see where misunderstandings lie. And reviewing the code, there are a lot of debug info available (even though more could be added), if such is activated. It's a lot more, than just no reply. Especially in this case, since there are 3 messages being processed by the server, and many things that could go wrong. Even a message, with the expected MAC would be helpful, because then you at least had evidence that it is precisely that test that went wrong. Logging of intermediate steps, such as nonces, verifydata, content hashed, hash, etc., would be even more useful.
A possibility to download an executable, perhaps with extensive debug logging as an option, would be greatly appreciated by anyone not familiar with the environments (like Maven) required to build each project. What TinyDTLS uses, it doesn't say yet. Perhaps it will become more clear closed to the publishing date (20th of September).
Best regards, Peter Från: leshan-dev-bounces@xxxxxxxxxxx <leshan-dev-bounces@xxxxxxxxxxx> för Kraus Achim (INST/ECS4) <Achim.Kraus@xxxxxxxxxxxx>
Skickat: den 11 augusti 2017 16:54 Till: leshan developer discussions Ämne: Re: [leshan-dev] Strange exception? Hi Peter,
I feel, there is a basic misunderstanding: A server would not be able to give you much more information except, that the MAC is wrong. It may be able to write the right MAC to the log (I could change an experimental scandium build for that, but in my experience this is mostly not that useful, because you don't see in the right MAC what was going wrong, when calculating yours). Though you said, java is not yours, I thought C maybe and therefore pointed to tinydtls. So I'm wrong or are you used to C? if you're not used C, I understand, that tinydtls also doesn't help you. But if you're used to C, the common way in open source is to fetch the source, build it, and run it. And then start to modify it for your needs, e.g. add or enable more logging. So: please move now to californium, I will no longer answer here in the leshan list [1]https://dev.eclipse.org/mailman/listinfo/cf-dev [2]https://github.com/eclipse/californium/issues and clarify, if you used to C or really still need a special scandium build with extended logging. Mit freundlichen Grüßen / Best regards Achim Kraus (INST/ECS4) Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY | http://www.bosch-si.com
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn From: leshan-dev-bounces@xxxxxxxxxxx [mailto:leshan-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Waher Sent: Freitag, 11. August 2017 16:29 To: leshan developer discussions <leshan-dev@xxxxxxxxxxx> Subject: Re: [leshan-dev] Strange exception? Hello Thanks Kraus. I saw that project too, and contacted them. They have a release of their server in September. So, no way (yet) to advance on this unfortunately, unless a kind soul can help me with some debug logging on the server end, or perhaps provide me with an executable with debug logging activated, that I can use here. Best regards, Peter _______________________________________________ leshan-dev mailing list leshan-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/leshan-dev | |||