nayutaco / lightning-dissector Goto Github PK

View Code? Open in Web Editor NEW

89.0 89.0 12.0 243 KB

WIP: A wireshark plugin to analyze communication between lightning network nodes

License: MIT License

Lua 100.00%

bitcoin lightning-network

lightning-dissector's People

Contributors

Stargazers

Watchers

Forkers

nayuta-gondo arowser nakajo2011 gcoinman t-bast milochen0418 char1yxok lohanspies 5l1v3r1 amrt1n3zm x2k2l 22388o

lightning-dissector's Issues

Support lightning message split across TCP packets

c-lightning decryption key not found

I am testing out the new c-lightning beta plugin. I have installed Lua, luarocks, wireshark, and the special lightning-cli. Wireshark can detect lightning packets but cannot decrypt them.

I am not sure if this is a bug or if I am missing something.

lightning-dissector should show decrypted message even if deserializer is not defined

Every time we see analyzed frame, it have different order

Currently, analyzed result is managed as a Lua table.

However, Lua table doesn't have order.
http://lua-users.org/wiki/ForTutorial

Note that the order that items are returned is not defined.

We need something like OrderedDict in Python.

Treat handshake message correctly

Currently, it raises MAC does not match error

decryption fails when I start Wireshark after ptarmigan launch

create a preference

dst port number
debug.log path

can be set in LN protocol preference.

MAC does not match when receiving pong

TCP payload is 71e74fbe80bae31d263211d2e1555b510e12c8deb00c52bb915649c3e2d40028eb324fceb1c0e4a2dec0ab

Support Wireshark 3

The patch on README does not work for Wireshark 3.x

Start using a version

If there is a version in this repo, I could not find it. Semver (semver.org) is usually used to create version numbers. You can then use these version numbers as github tags for releases.

If this is not stable, it's fine to use a 0.x.y version.

Make it possible to specify decryption keys manually

Write deserializer for channel_update

Wireshark truncates long lines

I can't see full text on this field.
Is there any workaround?

Optimize key searching

Currently, KeyLogSecretFactory searches whole key log file.
It can be made to search lines following a previously found key only.

Write deserializer for channel_announcement

define and describe debug.log(keys) format

deserialize tor onion addresses in node_announcement

Eclair and ptarmigan both does not support tor hidden service so priority of this is low.

decript and parse incoming packets

Make `luarocks make` not need sudo

Encode signatures in DER format

Support Eclair

I think this repo should support at least one implementation except ptarmigan.
Eclair already have a feature that dumps key/nonce to debug log so supporting eclair is relatively easy.

decryption fails mysteriously

After channel_announcement, decryption fails mysteriously.
MAC does not match

[Eclair] Dissector can't parse keys

Hey,

First of all thanks for doing this, it's going to be really helpful for newcomers such as myself.
I'm trying to use the dissector with 3 eclair nodes running locally.
I'm on Ubuntu 18.04, capturing with Wireshark on the loopback interface. I configured the logs location with the path to my 3 nodes (with the : separator as indicated in the tool).
I launched Wireshark before my Eclair nodes, made a few payments, but nothing appears when I filter for lightning.
How can I troubleshoot where the issue is coming from? Could it be a change in Eclair that doesn't dump the keys/nonces properly to the log file (I am in debug mode as instructed)?

Thanks!