https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6000
Summary: [PATCH] Bitcoin dissector
Product: Wireshark
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: bc@xxxxxxxx
Created an attachment (id=6470)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6470)
Bitcoin dissector
Build Information:
wireshark 1.6.0rc2 (SVN Rev Unknown from unknown)
Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.4, with GLib 2.28.6, with libpcap 1.1.1, with
libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre, with SMI 0.4.8,
with c-ares 1.7.4, with Lua 5.1, with Python, with GnuTLS 2.10.5, with Gcrypt
1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Apr 16
2011 18:31:04), without AirPcap.
Running on Linux 2.6.39-1-amd64, with libpcap version 1.1.1, with libz 1.2.3.4,
GnuTLS 2.10.5, Gcrypt 1.4.6.
Built using gcc 4.6.1 20110526 (prerelease).
--
I've created a dissector for the Bitcoin protocol. This is a protocol in early
development but yet stable enough to have a dissector.
Protocol information can be found at
https://en.bitcoin.it/wiki/Protocol_specification
I would like to have the code reviewed and if possible merged. The dissector
currently only supports the part of the protocol where the official client
actually have implemented the methods, will this be a problem to patch in a
later stage? Should I implement a "how this works" as per the specification?
Code can be found attached but also in the github repository:
https://github.com/blueCommand/bitcoin-dissector
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
