lightning

7499 Commits

55 Branches

107 Tags

38 MiB

Tree: b25a8ba29d

Commit Graph

Author	SHA1	Message	Date
Christian Decker	959687bf6d	onion: Pass the position and type of the failing TLV type out We'll need this when returning an error to the sender.	5 years ago
Rusty Russell	f7ebbb2ec5	common: make sphinx code ignorant of payload format. Now "raw_payload" is always the complete string (including realm or length bytes at the front). This has several effects: 1. We can receive an decrypt an onion which is grossly malformed. 2. We can still hand this to the htlc_accepted hook. 3. We then fail it unless the htlc_accepted accepts it manually. 4. The createonion API now takes the raw payload, and does not know anything about "style". The only caveat is that the sphinx code needs to know the payload length: we have a call for that, which simply tells it to copy the entire onion (and treat us as the final node) if it's invalid. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	5 years ago

Author

SHA1

Message

Date

Christian Decker

959687bf6d

onion: Pass the position and type of the failing TLV type out

We'll need this when returning an error to the sender.

5 years ago

Rusty Russell

f7ebbb2ec5

common: make sphinx code ignorant of payload format.

Now "raw_payload" is always the complete string (including realm or length
bytes at the front).

This has several effects:
1. We can receive an decrypt an onion which is grossly malformed.
2. We can still hand this to the htlc_accepted hook.
3. We then fail it unless the htlc_accepted accepts it manually.
4. The createonion API now takes the raw payload, and does not know
   anything about "style".

The only caveat is that the sphinx code needs to know the payload
length: we have a call for that, which simply tells it to copy the
entire onion (and treat us as the final node) if it's invalid.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

5 years ago

2 Commits (b25a8ba29d16cf1e84c2b9a5e93fe9614655e6ad)