Hi Matthias, I'll admit that project sounds pretty cool - and I don't want to discourage you from working on it; but I suspect that implementing that sort of functionality in Wireshark might open a giant can of worms, legally. (Especially since MS now own Skype's developers). ;)
Anyway, for getting started with writing dissectors, I'd recommend looking at the documentation in http://anonsvn.wireshark.org/viewvc/trunk/doc/ (especially "README.developer"), and reading the source code of existing dissectors. When working on new dissectors, I tend to take one of my existing ones, and modify it accordingly, in order to meet the needs of the new protocol in question. All dissectors are written against a "lowest common denominator" variant of C (C89? C99?), and the EPAN APIs, to ensure portability, and consistency. I hope that helps, Tyson. 2012/8/9 Matthias Bock <m...@matthiasbock.net> > Hi everybody, > > there is a project at GitHub, > uncovering the protocol structure of Skype. > Currently only UDP is documented (there is also > a TCP component somehow). > > https://github.com/matthiasbock/OpenSkype/wiki/Skype's-UDP-Format > > Documentation is not completed, but quite far > and dissecting (and decrypting) pcap captures > using Python on the console already works. > > The "next step" would be to implement a Wireshark > dissector for "SkypeUDP". > > I have no idea, how to do this ... > Anybody here who would like to help me? ;-) > > Cheers, Matthias > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > -- Fight Internet Censorship! http://www.eff.org http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | 00447934365844
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
