From laolu32 at gmail.com Tue Nov 6 07:08:17 2018 From: laolu32 at gmail.com (Olaoluwa Osuntokun) Date: Tue, 6 Nov 2018 18:08:17 +1100 Subject: [Lightning-dev] Wireshark plug-in for Lightning Network(BOLT) protocol In-Reply-To: References: Message-ID: Hi tomokio, This is so dope! We've long discussed creating canned protocol transcripts for other implementations to assert their responses again, and I think this is a great first step towards that. > Our proposal: > Every implementation has compile option which enable output key information > file. So is this request to add an option which will write out the _plaintext_ messages to disk, or an option that writes out the final derived read/write secrets to disk? For the latter path, it the tools that read these transcripts would need to be aware of key rotations, so they'd be able to continue to decrypt the transact pt post rotation. -- Laolu On Sat, Oct 27, 2018 at 2:37 AM wrote: > Hello lightning network developers. > Nayuta team is developing Wireshark plug-in for Lightning Network(BOLT) > protocol. > https://github.com/nayutaco/lightning-dissector > > It?s alpha version, but it can decode some BOLT message. > Currently, this software works for Nayuta?s implementation(ptarmigan) and > ?clair. > When ptarmigan is compiled with some option, it write out key information > file. This Wireshark plug-in decode packet using that file. > When you use ?clair, this software parse log file. > > Through our development experience, interoperability test is time > consuming task. > If people can see communication log of BOLT message on same format > (.pcap), it will be useful for interoperability test. > > Our proposal: > Every implementation has compile option which enable output key > information file. > > We are glad if this project is useful for lightning network eco-system. > _______________________________________________ > Lightning-dev mailing list > Lightning-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: