-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge with master #7
Commits on Sep 20, 2018
-
json-rpc: Remove upper limit for percentage
The `json_tok_percentage` parser is used for the `fuzzpercent` in `getroute` and `maxfeepercent` in `pay`. In both cases it seems reasonable to allow values larger than 100%. This has bitten users in the past when they transferred single satoshis to things like satoshis.place over a route longer than 2 hops.
Configuration menu - View commit details
-
Copy full SHA for cf52b71 - Browse repository at this point
Copy the full SHA cf52b71View commit details -
doc: Update docs to remove 100% upper bound
Actual change is in the previous commit.
Configuration menu - View commit details
-
Copy full SHA for 674d176 - Browse repository at this point
Copy the full SHA 674d176View commit details -
openingd: prioritize incoming peer traffic over handling (and sending…
… out) gossip - reduces probability for a deadlock where we block on sending data because the other peer cannot receive because it blocks on sending data etc. - when either side sends so much data that it fills up the kernel/network buffer - however sending out gossip can still block when (malicious) peer never receives
Configuration menu - View commit details
-
Copy full SHA for 94e42f2 - Browse repository at this point
Copy the full SHA 94e42f2View commit details -
CHANGELOG.md: catchup with changes so far.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 4198cb3 - Browse repository at this point
Copy the full SHA 4198cb3View commit details -
parse autotor: address before separate_address_and_port
this enables addr like --addr=autotor:127.0.0.1 or --addr=autotor:localhost to just use the default tor service port Signed-off-by: Saibato <Saibato.naga@pm.me>
Configuration menu - View commit details
-
Copy full SHA for d5c3626 - Browse repository at this point
Copy the full SHA d5c3626View commit details -
pytest: wait until mock is called for set_feerates.
Got a spurious failure in test_no_fee_estimate; we fired too soon from the logs (presumably we raced in on the first response, but estimatesmartfee gets called 3 times). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for e41e1a1 - Browse repository at this point
Copy the full SHA e41e1a1View commit details -
hsmd: reorder functions (MOVEONLY).
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 72e7856 - Browse repository at this point
Copy the full SHA 72e7856View commit details -
hsmd: rename per-peer to per-channel.
And remove cut&paste of derive_peer_seed. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 3e63d88 - Browse repository at this point
Copy the full SHA 3e63d88View commit details -
hsmd: implement bitcoin_key() to subsume bitcoin_pubkey and bitcoin_k…
…eypair. This mirrors the node_key() interface we already have. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 1e4e476 - Browse repository at this point
Copy the full SHA 1e4e476View commit details -
lightningd: accept hsmstatus_client_bad_request messages (and log!)
We currently just ignore them. This is one reason the hsm (in some places) explicitly calls log_broken so we get some idea. This was the only subdaemon which had a NULL msgcb and msgname, so eliminate those checks in subd.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for da9d929 - Browse repository at this point
Copy the full SHA da9d929View commit details -
hsmd: use status_conn to send bad_request messages, make handlers uni…
…form. The current code sends hsmstatus_client_bad_request via the req fd; this won't work, since lightningd uses that synchronously and only expects a reply to its commands. So send it via status_conn. We also enhance hsmstatus_client_bad_request to include details, and create convenience functions for it. Our previous handling was ad-hoc; we sometimes just closed on the client without telling lightningd, and sometimes we didn't tell lightningd *which* client was broken. Also make every handler the exact same prototype, so they now use the exact same patterns (hsmd *only* handles requests, makes replies). I tested this manually by corrupting a request to hsmd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 6b6b7ea - Browse repository at this point
Copy the full SHA 6b6b7eaView commit details -
hsmd: move HTLC TX signing next to commitment TX signing.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for f8df069 - Browse repository at this point
Copy the full SHA f8df069View commit details -
It was only used by handshake.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 8f1f178 - Browse repository at this point
Copy the full SHA 8f1f178View commit details -
hsmd: rename hsm_client_wire_csv to hsm_wire.csv
That matches the other CSV names (HSM was the first, so it was written before the pattern emerged). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for e012e94 - Browse repository at this point
Copy the full SHA e012e94View commit details -
hsmd: extract and use common sign_all_inputs() helper.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for cc48e79 - Browse repository at this point
Copy the full SHA cc48e79View commit details -
lightningd: use hsm_get_client_fd() helper for global daemons too.
We couldn't use it before because it asserted dbid was non-zero. Remove assert and save some code. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Header from folded patch 'fixup!_lightningd__use_hsm_get_client_fd()_helper_for_global_daemons_too.patch': fixup! lightningd: use hsm_get_client_fd() helper for global daemons too. Suggested-by: @ZmnSCPxj
Configuration menu - View commit details
-
Copy full SHA for 04c77f4 - Browse repository at this point
Copy the full SHA 04c77f4View commit details -
hsmd: document as part II of our journey.
Thanks greatly to the four people who I *know* have read this: @wythe, @ZmnSCPxj, @SimonVrouwe, and @cdecker Your feedback will help future developers seeking enlightenment! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 573f2f0 - Browse repository at this point
Copy the full SHA 573f2f0View commit details -
hsmd: don't use daemon_conn for clients.
It offers them a DoS vector, if they don't read the replies. We really want to use raw ccan/io so we can avoid buffering for this. It makes the handing of fds for new clients a bit more complex (callback based), but it's not too bad. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for b0769d9 - Browse repository at this point
Copy the full SHA b0769d9View commit details -
hsmd: reorder functions (MOVEONLY).
We don't need to pre-declare any more, but I left it in the previous patch for review simplicity. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 019bc4f - Browse repository at this point
Copy the full SHA 019bc4fView commit details -
We used to use it to complain about bad requests, but we use the status conn now, so it's unused except for tests and asserts. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 5b2e829 - Browse repository at this point
Copy the full SHA 5b2e829View commit details