--- Log opened Sun Sep 13 00:00:17 2020
00:11 -!- Kiminuo [~mix@141.98.103.204] has joined #rust-bitcoin
00:13 -!- guest534543 [~mix@89.187.189.206] has quit [Ping timeout: 258 seconds]
00:17 -!- Kiminuo [~mix@141.98.103.204] has quit [Ping timeout: 260 seconds]
00:20 -!- belcher [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
00:25 -!- Netsplit over, joins: paultroon, wumpus
00:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
00:33 -!- jonatack [~jon@37.165.131.50] has joined #rust-bitcoin
00:54 -!- jonatack [~jon@37.165.131.50] has quit [Ping timeout: 244 seconds]
01:03 -!- jonatack [~jon@37.165.131.50] has joined #rust-bitcoin
01:07 -!- jonatack [~jon@37.165.131.50] has quit [Ping timeout: 244 seconds]
01:08 -!- jonatack [~jon@37.165.131.50] has joined #rust-bitcoin
01:13 -!- jonatack [~jon@37.165.131.50] has quit [Ping timeout: 244 seconds]
01:14 -!- jonatack [~jon@109.202.107.20] has joined #rust-bitcoin
01:33 < elichai2> dr-orlovsky: the problem is that bitcoin doesn't send EOF at the end of every message, so `read_to_end` will just get stuck
01:54 < elichai2> rust's async-blocking compatibility is a mess
03:13 < dr-orlovsky> Well, you have to read message header specifying the length of the message payload, allocate the buffer of appropriate size and read into it with read_exact
03:13 < dr-orlovsky> https://docs.rs/tokio/0.2.22/tokio/io/trait.AsyncReadExt.html#method.read_exact
03:18 -!- Dena68Hickle [~Dena68Hic@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
03:19 -!- prusnak_ is now known as prusnak
03:19 -!- prusnak [sid403625@gateway/web/irccloud.com/x-nficguliffcrpcdy] has quit [Changing host]
03:19 -!- prusnak [sid403625@unaffiliated/prusnak] has joined #rust-bitcoin
03:19 -!- prusnak [sid403625@unaffiliated/prusnak] has quit [Changing host]
03:19 -!- prusnak [sid403625@gateway/web/irccloud.com/x-nficguliffcrpcdy] has joined #rust-bitcoin
03:41 -!- Kiminuo [~mix@141.98.103.204] has joined #rust-bitcoin
04:11 -!- guest534543 [~mix@89.238.186.252] has joined #rust-bitcoin
04:14 -!- Kiminuo [~mix@141.98.103.204] has quit [Ping timeout: 240 seconds]
05:55 -!- guest534543 [~mix@89.238.186.252] has quit [Quit: Leaving]
05:55 -!- Kiminuo [~mix@89.238.186.252] has joined #rust-bitcoin
06:18 -!- Kiminuo [~mix@89.238.186.252] has quit [Quit: Leaving]
06:24 -!- jonatack [~jon@109.202.107.20] has quit [Ping timeout: 244 seconds]
07:05 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
07:08 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds]
07:22 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
12:52 -!- belcher_ is now known as belcher
13:42 -!- Dena68Hickle [~Dena68Hic@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 256 seconds]
13:52 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds]
14:18 -!- belcher [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
16:59 < ariard> BlueMatt: git grep review #633 :p
17:01 < BlueMatt> ariard: cool! will do...tomorrow
17:01 < BlueMatt> ariard: also, can you ack 688?
17:04 < ariard> BlueMatt: sure doing it, also bookmark #684, SGTM
17:06 < BlueMatt> yea, i was just about to review 684
17:06 < BlueMatt> once i stop being distracted by ntp
17:09 < ariard> lol are you aware of https://www.cs.bu.edu/~goldbe/papers/NTPattack.pdf
17:10 < ariard> I really want to try if I can force a node to reject block by hijacking its primary server
17:11 < ariard> BlueMatt: ack'ed 688
17:15 < BlueMatt> ariard: yea, I mean ntp is *not* designed to provide any security, and even if it did, people use the ntp pool usually, which any random joe can add their server to, and which often has servers with all kinds of nonsense time set.
17:15 < BlueMatt> ariard: bitcoin core does have the clock fudge thing, but iirc it like ignores times after the first few hundred so is basically not a thing, it probably needs to just be removed wholesale tbh.
17:15 < BlueMatt> I do sync my clocks against gps directly, though :)
17:16 < ariard> ahah I didn't expect less!
17:16 < ariard> yeah and switching to roughtime will introduce certificate authorities assumptions
17:17 < ariard> I need to verify but Core is still relying on the local clock for diverse things in the p2p stack, beyond consensus
17:17 < ariard> GetTime(), not the adjusted/fudged things
17:23 < BlueMatt> right, but the "adjusted" things don't adjust much iirc
17:23 < BlueMatt> yea, basically anything to do with time screws you - there is no good option
23:31 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds]
--- Log closed Mon Sep 14 00:00:18 2020