Christian Decker 21355edc43 plugin: Do not send the internal framed message over the wire ... Looks like #4394 treated a symptom but not the root cause. We were actually sending the message framed with the WIRE_CUSTOMMSG_OUT and the length prefix over the encrypted connection to the peer. It just happened to be a valid custommsg... This fixes the issue, and this time I made sure we actually send the raw message over the wire. However for backward compatibility we needed to imitate the faulty behavior which is 90% of this patch :-) Changelog-Fixed: plugin: `dev-sendcustommsg` included the type and length prefix when sending a message.		2021-03-09 14:39:22 +10:30
..
common.c	df: use dev-env flagged upfront shutdown script	2021-01-10 13:44:04 +01:00
common.h	df: use dev-env flagged upfront shutdown script	2021-01-10 13:44:04 +01:00
dualopend_wire.csv	rbf: consolidate failure paths, use "warnings"	2021-03-06 15:03:56 +10:30
dualopend_wiregen.c	rbf: consolidate failure paths, use "warnings"	2021-03-06 15:03:56 +10:30
dualopend_wiregen.h	rbf: consolidate failure paths, use "warnings"	2021-03-06 15:03:56 +10:30
dualopend.c	plugin: Do not send the internal framed message over the wire	2021-03-09 14:39:22 +10:30
Makefile	openingd: check upfront shutdown script.	2021-03-02 14:42:34 +10:30
openingd_wire.csv	openingd: convert wire to new scheme.	2020-08-25 12:53:13 +09:30
openingd_wiregen.c	tools/generate-wire.py: include digits in #ifndef idempotent header.	2021-01-13 14:45:36 +01:00
openingd_wiregen.h	tools/generate-wire.py: include digits in #ifndef idempotent header.	2021-01-13 14:45:36 +01:00
openingd.c	plugin: Do not send the internal framed message over the wire	2021-03-09 14:39:22 +10:30