Correctly verify and forward excess data post-signature in signed announcement messages

[TheBlueMatt]

Title plus a few other things for BOLT 7 compliance. See commit messages for more info.

[TheBlueMatt]

This is gonna have to inform the design of #119, so I'm gonna go ahead and take this.

[yuntai]

Can we assume underlying Read can raise EOF at the end of the message (including excess data), so we can loop until EOF to collect data for hashing?

[TheBlueMatt]

I think we have to? I don't see how we can make the serialize round-trip properly without it. At least for messages off the wire it's trivial as they are length-descripted and decrypted at a certain length.

…

On August 31, 2018 11:30:49 AM UTC, yuntai ***@***.***> wrote: Can we assume underlying `Read` can raise EOF at the end of the message (including excess data), so we can loop until EOF to collect data for hashing? -- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: #136 (comment)