| 02:55 |
asciilifeform |
meanwhile, coupla thoughts re pest cpu cycle shaving : |
| 02:56 |
asciilifeform |
sha384 (and 224 for that matter) don't expose their full internal state from the output, and so don't actually need the double-pass hmac construction. |
| |
↖ |
| 02:57 |
asciilifeform |
in fact, with these, you can compute e.g. S = SHA384(K + Message) and cache the state for SHA384(K) per peer, and farm the remainder out to worker threads |
| 02:58 |
asciilifeform |
i suspect there's no actual risk to 224, for that matter -- K aint a long-lived seekrit (we're doing rekeys at reasonable intervals) , and on top of this enemy has ~15min to usefully collide the hash |
| 03:01 |
asciilifeform |
faster hash -- moar ddos resistance, with the obv. tradeoff. |
| |
↖ |
| 03:04 |
asciilifeform |
upstack, must remind folx that whether $box keeps up 'at line rate' will depend also on # of ~keys~ in the wot (and not strictly # of peers, recall that at various times there may be >1 key per) |
| 03:04 |
dulapbot |
Logged on 2021-09-23 15:21:07 asciilifeform: i expect you'd have at least 8cores on reasonable box, which gives you ~105840 ticks to process a packet, imho entirely doable. |
| |
~ 11 hours 24 minutes ~ |
| 14:29 |
asciilifeform |
$ticker btc usd |
| 14:29 |
busybot |
Current BTC price in USD: $42512.3 |
| 14:29 |
asciilifeform |
!w poll |
| 14:29 |
watchglass |
Polling 17 nodes... |
| 14:29 |
watchglass |
205.134.172.26:8333 : Alive: (0.021s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=701997 |
| 14:29 |
watchglass |
185.85.38.54:8333 : Could not connect! |
| 14:29 |
watchglass |
84.16.46.130:8333 : Could not connect! |
| 14:29 |
watchglass |
185.163.46.29:8333 : Could not connect! |
| 14:29 |
watchglass |
205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=701997 |
| 14:29 |
watchglass |
71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.031s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 (Operator: asciilifeform) |
| 14:29 |
watchglass |
205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.082s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 |
| 14:29 |
watchglass |
205.134.172.28:8333 : Alive: (0.022s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=701997 (Operator: whaack) |
| 14:29 |
watchglass |
54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.171s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=701993 |
| 14:29 |
watchglass |
143.202.160.10:8333 : Alive: (0.234s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 |
| 14:29 |
watchglass |
208.94.240.42:8333 : Alive: (0.220s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 |
| 14:29 |
watchglass |
213.109.238.156:8333 : Alive: (0.424s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 |
| 14:29 |
watchglass |
205.134.172.27:8333 : Alive: (0.099s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 (Operator: asciilifeform) |
| 14:29 |
watchglass |
103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.656s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=701997 |
| 14:30 |
watchglass |
54.38.94.63:8333 : Violated BTC Protocol: Bad header length! |
| 14:30 |
watchglass |
176.9.59.199:8333 : Violated BTC Protocol: Bad header length! (Operator: jurov) |
| 14:31 |
watchglass |
192.151.158.26:8333 : Busy? (No answer in 100 sec.) |
| |
~ 54 minutes ~ |
| 15:25 |
asciilifeform |
following up re upstack -- went and rtfm'd, sha384 is simply sha512 with mutilated init state and truncated output; and ditto 224 (mutilated 256) ; i.e. no speed win over the full-length one, only point of'em was pill against length extensionism |
| 15:25 |
dulapbot |
Logged on 2021-09-23 23:01:04 asciilifeform: faster hash -- moar ddos resistance, with the obv. tradeoff. |
| 15:25 |
dulapbot |
Logged on 2021-09-23 22:56:04 asciilifeform: sha384 (and 224 for that matter) don't expose their full internal state from the output, and so don't actually need the double-pass hmac construction. |
| 15:29 |
* |
asciilifeform will stick w/ 384 unless someone has a convincing objection |
| |
~ 1 hours 8 minutes ~ |
| 16:38 |
punkman |
asciilifeform: instead of HMAC-512? |
| 16:39 |
asciilifeform |
punkman: well, in current draft hmac384 |
| |
~ 1 hours 11 minutes ~ |
| 17:51 |
asciilifeform |
apropos/for-noobs: a notbad likbez re 'length extension attack'. |
| 17:52 |
punkman |
found a small irc server to embed in my pest prototype |
| 17:54 |
punkman |
was planning to use separate ircd, but this seems handy, can make it think it has a connected user for each WoT peer |
| |
~ 2 hours 53 minutes ~ |
| 20:47 |
asciilifeform |
punkman: neato. if it's golang or somesuch horror tho, asciilifeform prolly won't be able to test yours, doesn't keep that toolchain around (nor would it likely run under asciilifeform's gentoo) |