--- Log opened Fri Jan 18 00:00:24 2019
00:13 -!- mkebitcoin [ae6186e0@gateway/web/cgi-irc/kiwiirc.com/ip.174.97.134.224] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
01:26 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
01:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:39 < rusty> cdecker: hmm, https://travis-ci.org/ElementsProject/lightning/jobs/481221455 showing timeouts on getmanifest on Travis under valgrind.  I've seen this before: maybe we need to allow more than 10 (!) seconds for that case?
01:53 < blockstream_bot> [Christian Decker, Blockstream] Sure, shall we make it dependent on an env var? It wouldn't be much use outside the valgrind runs
02:18 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:30 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:32 < rusty> cdecker: I think we can just extend it to 30 or 60, TBH.  THe only reason for timeout is to give some diagnosis if something does go horribly wrong?
06:19 -!- kexkey [~kexkey@192.230.35.148] has joined #c-lightning
06:52 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode]
07:11 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:18 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
07:44 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
08:03 <@cdecker> Sounds good to me, will open a PR
08:07 <@cdecker> PR #2276, just a constant bump to 60 seconds
08:08 <@cdecker> roasbeef: I'm looking for nice ways to increase isolation for plugins, so that'll improve over time
08:09 < nothingmuch> isolation at the level of the resources controlled by RPC, or process model?
08:10 <@cdecker> Both, but I'd like to lock down the processes first, dropping to an unprivileged user, isolating using app-armor, or similar
08:11 <@cdecker> And then we can start segmenting the RPC as well. We could for example give plugins policies on how they can talk to `lightningd` through the existing connection instead of them having to reach around to the RPC socket
08:14 < nothingmuch> sounds a bit similar to cloudabi's access model
08:15 < nothingmuch> (it transfers access to resources using by passing file descriptors on a socket, along with a manifest, i believe in yaml, for metadata)
08:19 < nothingmuch> might also also worth looking at cap'n'proto for inspiration, it's much more vertically integrated but its notion of capabilities i think can be mapped quite elegantly to json-rpc, where the provider can notify or give responses that contain e.g. hmaced values that are then used as method names or something
08:28 -!- kexkey [~kexkey@192.230.35.148] has quit [Quit: Scaling pentatonically]
08:32 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 250 seconds]
08:33 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
08:37 -!- kexkey [~kexkey@192.230.35.148] has joined #c-lightning
09:16 < nothingmuch> to be clear what i meant by that is e.g. plugins only being allowed to call methods on rpc methods they have been delegated access to via other rpc methods
09:58 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 244 seconds]
10:00 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
11:07 -!- billybigpotatoes [~billybigp@2a02:c7f:c21f:8100:1c08:34e:f30b:3b06] has joined #c-lightning
11:14 -!- kexkey [~kexkey@192.230.35.148] has quit [Quit: Scaling pentatonically]
11:15 -!- kexkey [~kexkey@192.230.35.148] has joined #c-lightning
11:21 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
11:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
11:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
11:46 < blockstream_bot> [Christian Decker, Blockstream] The major complication with this kind of thing is how to describe what a plug-in may be allowed to do. Similar issues also come up with other things like apparmor and selinux
11:47 < blockstream_bot> [Christian Decker, Blockstream] At some point the policies become so hard to describe that it's no longer intuitive to users
11:55 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 250 seconds]
11:59 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
12:06 < roasbeef> heads up y'all our next major release will require DLP from connections/channels we make (new ones), old ones may become inactive or even closed at upgrade time (possibly, haven't decided on this) 
12:06 < roasbeef> would like to avoid a network partition
12:24 -!- kexkey [~kexkey@192.230.35.148] has quit [Quit: Scaling pentatonically]
12:34 -!- billybigpotatoes [~billybigp@2a02:c7f:c21f:8100:1c08:34e:f30b:3b06] has quit [Quit: Leaving]
12:39 < ctrlbreak> AAAAhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh!!!!.jpg
12:40 < ctrlbreak> roasbeef; You guys have any idea on a timeline for this atm ?
12:41 < ctrlbreak> I will not be up to speed fast enough to help <:-(
13:04 < nothingmuch> cdecker: yep, can't argue with that, merely having the ability to specify access control in terms of capabilities doesn't absolve of the need to define them
13:08 < nothingmuch> s/(?=need)/ or difficulty/
13:24 -!- charltonh [~charltonh@189.160.97.62] has quit [Quit: leaving]
13:36 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
13:39 -!- Rempentant [5921f648@gateway/web/freenode/ip.89.33.246.72] has quit [Ping timeout: 256 seconds]
13:39 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
13:42 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:07 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:34 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:49 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:56 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:01 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:05 -!- kexkey [~kexkey@192.230.35.148] has joined #c-lightning
15:05 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:05 -!- mkebitcoin [ae6186e0@gateway/web/cgi-irc/kiwiirc.com/ip.174.97.134.224] has joined #c-lightning
15:06 < mkebitcoin> Hi! I have a node running! Is there a way to view funds available to allocate to new channels?
15:09 < mkebitcoin> I tried "lightning-cli listfunds" however that seems to give only the funded channels, not the funds in the wallet of the node
15:10 -!- kexkey [~kexkey@192.230.35.148] has quit [Ping timeout: 250 seconds]
15:10 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:22 < rusty> mkebitcoin: listfunds does show total funds, too.
15:25 < mkebitcoin> ok, thanks, I see the outputs value, but it was less than I was expecting after sending funds on chain to the node's wallet
15:26 -!- kexkey [~kexkey@192.230.35.148] has joined #c-lightning
15:31 < rusty> mkebitcoin: it won't count until after a confirmation....
15:35 < mkebitcoin> ah, OK and the outputs[0].value property is in satoshis?
16:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
16:34 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection]
16:35 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning
16:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
16:56 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:08 < ctrlbreak> woot!  Have a modern patch for dumping an xpriv key from CL!  That was fun.
17:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:29 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
17:30 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:35 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
17:35 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
17:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
17:55 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:02 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
18:08 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:15 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
18:15 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:23 -!- kexkey [~kexkey@192.230.35.148] has quit [Ping timeout: 240 seconds]
18:23 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:33 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
18:36 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:41 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
18:41 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:47 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
18:51 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
18:53 -!- mkebitcoin [ae6186e0@gateway/web/cgi-irc/kiwiirc.com/ip.174.97.134.224] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
19:00 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
19:01 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:08 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:11 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:15 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:20 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
19:32 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:37 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:38 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:43 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
19:43 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:48 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
19:49 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:51 -!- raucao [~raucao@skippe2.nine.ch] has quit [Quit: kthxbai]
19:52 -!- raucao [~raucao@skippe2.nine.ch] has joined #c-lightning
19:53 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
19:54 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:59 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds]
20:01 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:35 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
20:36 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
21:39 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:40 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
22:56 -!- booyah [~bb@193.25.1.157] has quit [Excess Flood]
23:11 -!- booyah [~bb@193.25.1.157] has joined #c-lightning
23:16 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 245 seconds]
--- Log closed Sat Jan 19 00:00:25 2019