We could get into the technical parts later, but in theory, you could legally challenge the creator of the dissector of X if they have provided you the dissector of X, but is not willing to share the source with you. This is in direct violation of the GPL under which GPL and all dissectors are released (AFAIK). If they gave you the dissector they
have to give you the source if you want it.
I'll think about the technical challenge in a while, but probably someone will beat me to it.
Best regards,
Abhik.
PS: If you have some captures already, perhaps you could try to reverse engineer the headers you want as a start.
On 9/5/07,
taraniteja.vishwanatha@xxxxxxxxx <taraniteja.vishwanatha@xxxxxxxxx> wrote:
Hi ,
There are 2 protocols X and Y. X runs over UDP. Y runs over
X. A payload packet consists some headers of X and some headers of Y.
I am dissecting Y, and X has been dissected by
somebody else , who do not wish to share the source code.
As per my understanding:
- There should be an
identification number which identifies Y over X.
- There should be sufficient
bit-wise information in Y which identify X headers and data .
But I did not get either of the information. Instead I have
a document which describe some headers of Y which contain X data , without
specifying the values.
I am not able to understand how can I integrate the other
protocol with mine and test the complete packet containing both the headers.
BR,
Tarani
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
|
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
