#pest | 2021-11-13

asciilifeform: ( tho erryone in e.g. asciilifeform's dc can easily have a perma-port, just need to remember to set one below 32768 , under linux higher ones aint externally routed into )

shinohai: Speaking of yer dc asciilifeform, wat do with this rk jurov gave me access to ?

asciilifeform: shinohai: it's running http://btc.yt/lxr/satoshi/source/ , let it alone for nao

shinohai: o7

asciilifeform: shinohai: eventually i'ma consolidate whole thing ( still hoping to get tarball of original www from jurov )

shinohai: $vwap

shinohai: hmm

shinohai: $vwap

busybot: The 24-Hour VWAP for BTC is $ 64672.71 USD

shinohai: So I can crash blatta by doing this: `echo "Here is some garbage" | socat - udp:<myip>:7778`

shinohai: wait - seems to be anomaly now correctly rejects as malformed packet

asciilifeform: shinohai: hm so did it crash (paste eggog) ?

shinohai: Only happened once, now just rejects the packets as it should.

asciilifeform: shinohai: right, but do you still have the barf from that crash ?

asciilifeform: i expect awt will find it interesting

shinohai was just curious what would happen if I fed garbage to socket ....

asciilifeform: ( recall, this is intended specifically a device for eating unlimited liquishit w/out choking )

asciilifeform: shinohai: from your description i suspect the current proggy doesn't handle malformed packets properly

shinohai: Nah it keeps running now when I send it garbage, outputs this:

shinohai: 2021-11-13 19:17:47.014037 [67.166.203.177:37831] -> 6875656875656272

shinohai: Discarding malformed black packet from 1IRaEkAxKn7ltD1R3zfA9CQIyincq0ppgRme/sNoMuYihksPsFOY3pSpK<.......>

asciilifeform: shinohai: see if you can set up sumthing to feed it liquishit, replicate crash

asciilifeform: given as you saw 1

shinohai: I'll bang out a bash script to it automajically and see what happens (now that station is remote on znc server).

asciilifeform: shinohai: loox like your last msg seen by log bot but not asciilifeform's station

shinohai: >.>

asciilifeform: this one shows

asciilifeform: maybe 1st confirmed case of udp packet loss since we started, lol

asciilifeform: ( 'getdata' is the eventual pill, there )

shinohai: OOOOH I know what's up, I restarted with fresh db so asciilifeform isn't in my peers .... AGAIN.

shinohai: Now lessee

asciilifeform: aa lolk

asciilifeform suggests to awt that blatta oughta emit sumthing like 'hey wot is empty... add some peers?' to irc session

asciilifeform: wb billymg

asciilifeform: and hmm awt, where does the ip in e.g. '(billymg@179.50.191.76) has joined #pest' come from ? (given as he hasn't showed up in asciilifeform's AT..)

billymg: asciilifeform: that's the ip i'm connecting from at home

asciilifeform: rright but q was re how it ended up in the console

asciilifeform: given that billymg's home station has not ended up in my AT

billymg: not sure, but for clarity, i'm not running a station at home, i'm connecting to my remote pest station via a standard IRC client

asciilifeform: (i.e. evidently i'm seeing billymg via hearsay atm)

asciilifeform: billymg: even more odd, then

asciilifeform: awt: if stations are in fact broadcasting 'hellos' of some kind, containing local ip -- this aint in-spec.

asciilifeform: nobody but a direct peer has any biz knowing your ip (either station's or irc console's)

asciilifeform must bbl

awt: asciilifeform: yeah I think the irc server includes your client host info as part of your id in the irc messages. Should be able to mitigate that server side.

asciilifeform: awt: makes sense

asciilifeform evidently had a rather narrow view of irc protocol on acct of only ever having written bots, which simply ignore 95% of it, rather than server

asciilifeform oughta actually read the whole rfc, lol

asciilifeform: awt: simplest 'mitigate' is to simply (as per spec) only pass along from irc to pest 1) nick 2) msg payloads

← 2021-11-12 | 2021-11-14 → ↑