--- Log opened Tue Oct 18 00:00:51 2022
00:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
00:32 -!- lash [~nolash@94.46.24.41] has joined #c-lightning
00:35 < lash> if someone steals a device running the daemon, how likely is it they can discover what addresses and channels the daemon is serving?
00:37 < lash> either by break-in while daemon is running, OR traces left in persistent storage even if seed is encrypted.
00:47 < jasan> lash: generally all 'they' need to one-sidedly steal funds from the channel is to ensure the other side does not come online (which your described case with stealing a device does). The other channels would be able to steal 100% funds from this stolen node once it is offline (and they see it is permanent), but 'they' (those who steal the node) will not have the possibility to get the funds
00:47 < jasan> (only if the seed was not encrypted and they properly do the timing after the other side of the channel tries to steal).
00:49 < lash> jasan right, but the question is not about theft of funds, but to determine WHICH funds the node is in custody of / is managing
00:51 < lash> also, will the lightning node leave traces of the same on the bitcoind node? i noticed that the electrum-personal-server i was running actually registers all addresses its looking for with the bitcoin node, which seems like  a security risk to me, if you want to keep what addresses are yours a secret
00:53 -!- Zenton [~user@user/zenton] has joined #c-lightning
01:10 < jasan> lash: Ah, I see. CLN has its own Bitcoin wallet implementation and does not leave any traces, just its own database (be it in sqlite3 file or Postgres).
01:10 < lash> jasan cool and that db is encrypted?
01:10 < lash> or at least obfuscated?
01:11 < jasan> lash: nope, by default no, and I am not sure if it can be
01:12 < lash> so effectively if the db is protected somehow, and the seed is encrypted, then only way to glean addresses (aside from being a counterparty on the network) would be to root and inspect addresses in memory?
01:13 < lash> sounds like encrypting the database entries would be a good feature to add.
01:14 < jasan> maybe it's there already, I just never used it.
01:36 -!- StocksRoomm [~StocksRoo@185.76.9.58] has joined #c-lightning
01:36 -!- StocksRoomm [~StocksRoo@185.76.9.58] has quit [K-Lined]
02:00 -!- Traca[m] [~tracamatr@2001:470:69fc:105::1:d463] has quit [Quit: You have been kicked for being idle]
02:07 -!- lash [~nolash@94.46.24.41] has quit [Quit: leaving]
03:03 -!- kexkey [~kexkey@static-198-54-132-120.cust.tzulo.com] has quit [Ping timeout: 252 seconds]
03:05 -!- kexkey [~kexkey@198.54.132.120] has joined #c-lightning
04:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 258 seconds]
04:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
05:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
05:17 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
05:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:43 -!- StocksRoomm [~StocksRoo@185.76.9.58] has joined #c-lightning
06:43 -!- StocksRoomm [~StocksRoo@185.76.9.58] has quit [K-Lined]
--- Log closed Tue Oct 18 06:49:04 2022
--- Log opened Tue Oct 18 06:49:04 2022
07:02 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
07:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
07:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
08:22 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
08:54 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
08:56 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
08:59 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
08:59 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
09:19 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
09:20 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
10:04 -!- StocksRoomm [~StocksRoo@185.76.9.58] has joined #c-lightning
10:04 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
10:04 -!- StocksRoomm [~StocksRoo@185.76.9.58] has quit [K-Lined]
11:00 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
13:11 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
13:13 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
13:51 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
13:52 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
14:14 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
14:19 -!- StocksRoomm [~StocksRoo@185.76.9.58] has joined #c-lightning
14:20 -!- StocksRoomm [~StocksRoo@185.76.9.58] has quit [K-Lined]
14:53 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
15:45 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
16:14 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
16:20 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
16:22 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
16:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:07 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
20:08 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
20:48 -!- Netsplit *.net <-> *.split quits: jonasschnelli, cdecker[m], niftynei, kakolainen[m]
20:48 -!- Netsplit over, joins: jonasschnelli
20:49 -!- Netsplit over, joins: niftynei
20:50 -!- Netsplit over, joins: cdecker[m]
20:51 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has joined #c-lightning
23:26 -!- raj- [~raj@2602:ffb6:4:e396:f816:3eff:fe47:ca2a] has quit [Ping timeout: 260 seconds]
--- Log closed Wed Oct 19 00:00:31 2022