1
63%
master: 63%

Ran 09 Jan 2018 04:38AM UTC

Files 101

Run time 4s

Badge

Embed ▾

Committed 09 Jan 2018 03:50AM UTC coverage: 72.77% (-0.03%) from 72.796%

Job # RACE=false

Build Type

push

travis-ci

Committed by

Roasbeef

Commit Message

lnwallet: only forward freshly locked in HTLC's in ReceiveRevocation

This commit fixes a nasty bug that has been lingering within lnd, and
has been noticed due to the added retransmission logic. Before this
commit, upon a restart, if we had an active HTLC and received a new
commitment update, then we would re-forward ALL active HTLC’s. This
could at times lead to a nasty cycle:
  * We re-forward an HTLC already processed.
  * We then notice that the time-lock is out of date (retransmitted
HTLC), so we go to fail it.
  * This is detected as a replay attack, so we send an
UpdateMalformedHTLC
  * This second failure ends up creating a nil entry in the log,
leading to a panic.
  * Remote party disconnects.
  * Upon reconnect we send again as we need to retransmit the changes,
this goes on forever.

In order to fix this, we now ensure that we only forward HTLC’s that
have been newly locked in at this next state. With this, we now avoid
the loop described above, and also ensure that we don’t accidentally
attempt an HTLC replay attack on our selves.

Fixes #528.

Fixes #545.

Coverage Stats

15051 of 20683 relevant lines covered (72.77%)

23172.01 hits per line

lightningnetwork / lnd / 2502 / 1
63%
master: 63%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2502.1 (RACE=false)

lightningnetwork / lnd / 2502 / 1 63% master: 63%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2502.1 (RACE=false)

lightningnetwork / lnd / 2502 / 1
63%
master: 63%

README BADGES
x