log☇︎
1900+ entries in 0.017s
Framedragger: asciilifeform: that's why i didn't wave around with the result :) yeah need to do more testing for sure.
Framedragger: asciilifeform: nah if you iterate thru pages will be other packages as well
Framedragger tried fg last weekend, was all good, (very) small sample (2.7MB) had 7.999936 bits of entropy per byte. but yet to test more thoroughly, including removing shields, etc.
Framedragger: ^ could be useful
Framedragger: via that HN post, https://codesearch.debian.net/search?q=recvfrom+.*+MSG_PEEK
Framedragger: asciilifeform: busy at work unfortunately but would be a good effort, yeah
Framedragger: that makes sense :) circulation is the keyword i suppose
Framedragger: need to start thinking about internetcensus2012 reboot, i tell ya
Framedragger: xchat.. RCE on irc users heh
Framedragger: BingoBoingo: i smell bile and i hate that taste. but possibly i am misconstruing things (i.e., not actual bile in #t)
Framedragger: pkg-config, oh good
Framedragger: asciilifeform: neat
Framedragger sees point.
Framedragger: re manpage, thanks for educating me, as always - yeah ok it's the same thing
Framedragger: http://btcbase.org/log/2017-04-13#1642864 << just for context/posterity, i meant ungetc() here, what a load of crap ☝︎
Framedragger: also there is an easy habit to slip into by which you start discarding any things a priori. (mp-emulator: that's not a bad thing(tm))
Framedragger: i'll grant you that i'm this overly naive kid as regards these matters. but i fear the psychological alternative :) (becoming an angry man full of bile; principle of charity has a psychological function to me, too). and eh, 'empire'. very binary ☟︎☟︎
Framedragger: you read in to a fixed size buffer and then discard info/connection if need be. they're pretending to be 'only reading one byte' but it's the kernel which chops off one byte from the rest of the packet
Framedragger: hm i guess you don't save *any* memory, i can see why
Framedragger: yeah i know i know, ultimately pointless
Framedragger: yeah i see what you mean. ultimately it's bullshit/snakeoil. i was just saying that ~some~ sense was had (but you'll prolly deny even that - fair enough)
Framedragger: asciilifeform: hah, omg i've only heard about this and checking now, even the description is lulzy. "put stuff back into stream" ☟︎
Framedragger: it saves program-internal memory, but the card itself reads in the data regardless, sure.
Framedragger: (sure, data comes in to network card's buffer anyway)
Framedragger: i guess you could also do `recv(&one_byte_buffer)` and then later `recv(&larger_buffer)`, too; but their use at least makes some sense to me. imho.
Framedragger: it seems to use MSG_PEEK to check info on the connected peer (and drop it if need be), and by using this, it can avoid allocating additional memory to take in whole buffer
Framedragger: asciilifeform: actually i can see some rationale. checking that socat source and that line (https://github.com/craSH/socat/blob/master/xio-udp.c#L220), if you check the definition of buff1, it's `char[1]`.
Framedragger: !~google site:github.com "MSG_PEEK"
Framedragger: i can find it elsewhere, too, but small/stupid projects
Framedragger: there is that.
Framedragger: and commits in linux are pgp-signed, not just "ok"d
Framedragger: can't you use `git blame` to find out the latter?
Framedragger: maybe it is.. someone could be using it to get buffer length (folx exist who ask 'so how do i use MSG_PEEK for this...')
Framedragger: what are they supposed to say? that this is socat-specific? because it's not
Framedragger: so hm good point, pretty retarded
Framedragger: you can get the length of incoming message by other means than just reading it into the buffer (through ioctl or w/e)
Framedragger: prolly no cases where you couldn't use something saner instead?
Framedragger: hm. are there cases when the program would be like, "i don't have resources to handle this, later", in some embedded/realtime/low-resource context
Framedragger: asciilifeform: i dunno who uses it, either, and why would it be used. it's kind of "remind me about this later" feature, pretty weird/useless
Framedragger: ah nice.
Framedragger: ahh blade runner
Framedragger: trinque: sounds like a line from a text based adventure game :)
Framedragger: ^ fuckload of android sheep affected. did i hear, 'another internet survey?'
Framedragger: (the latter is a proper RCE)
Framedragger: multibugs for multiusers
Framedragger: << this one *does* apply to everyone < 4.5 i think
Framedragger: ohno wait this is something else.. i was planning to link https://nvd.nist.gov/vuln/detail/CVE-2016-10229 ☟︎
Framedragger: it's great fun!
Framedragger: mircea_popescu: i don't think so, and i thought about linking this, too heh (need to update/patch kernels if they are < 4.5)
Framedragger: http://btcbase.org/log/2017-04-12#1642514 << well, run the query that the python runs prepended with explain analyze, see if it's doing some slow sequential scan or sth, perhaps just need to pop an index in :) ☝︎
Framedragger: (just fyi, mkj (which hosts scriba; separate from siphnos which hosts scan data, phuctor cache, etc.) is going down soon for maintenance, but downtime shouldn't exceed 15min)
Framedragger: !~google RFC 1149
Framedragger: i mean
Framedragger: my logs say it's the russians
Framedragger: but that requires me to actually be able to do math, so no-go.
Framedragger: mircea_popescu: i tried to think of a diagonal argument along the fashion of "if you make it conform to that narrow spec, the conformance itself is an additional statement which needs a larger spec, which in turn needs a larger spec, DO YOU WANT ME TO GO INSANE WITH INFINITY";
Framedragger: :o PROTOCOL MISBEHAVIOUR, i shall endeavour to fix that m'lord.
Framedragger: (inflated right after being de-pegged, that is)
Framedragger: random thing re ^ is that *for some reason*, a huge bunch of polish folks had bank loans in swiss franc. because "switzerland stable, good country for banking", something something. when swiss franc inflated by *a whole lot* vs. the zloty, they weren't exactly exalted. :/ kinda lulzy thought process must have been
Framedragger: that particular query had to sift through 93749 seems like
Framedragger: touché
Framedragger: explain (analyze, buffers) would tell if it's just hitting cache
Framedragger vaguely recalls some theory based on algae. will check laters
Framedragger: actually haven't, just recall searching around when you referred to it. kk. :)
Framedragger: the genesis of gender in biology is indeed interesting
Framedragger: right, right :) hm i suppose i'd like to do some semantic matching as well, but maybe unneeded dickwaving
Framedragger: ben_vulpes: curious, is this using pg full text search (including taking care of tokenising etc)?
Framedragger: http://btcbase.org/log/2017-01-27#1608458 ☝︎
Framedragger: HA
Framedragger: fwiw when i was running searchable tor metrics db (>= 80GB tho would need to check) and had search there, it ran ~fine~, including wildcard support.
Framedragger: shots fired, i will see if i can find time to implement search using pg full text search :)
Framedragger: i'd offer to go for a beer shinohai but unfortunately no portals yet. :/ sad!
Framedragger: (http://btcbase.org/log/2016-08-24#1528254) ☝︎
Framedragger: ^ SSH-1.99-HUAWEI-1.5 & SSH-1.99-DOPRA-1.5 (respectively), heh
Framedragger: http://qntra.net/2017/04/altcointradingbot-io-is-very-sorry-for-your-loss/ href for "Web of Trust" is broken, just fyi shinohai , BingoBoingo
Framedragger: http://btcbase.org/log/2017-04-11#1641991 << thank you everyone for the trust :) ☝︎
Framedragger: very unrelated old story for good humour in the forum: https://thedailywtf.com/articles/Special-Delivery
Framedragger: "your http client tries to re-request after request failed. DDoS!!"
Framedragger: ok this is ridiculous, i'm done ☟︎
Framedragger: but that's the last time i brought this up. i wanted to clarify that nobody's hammering it.
Framedragger: i'm running wget *by hand*. wtf. you expose a href on the site. i try to get it. it fails. ?
Framedragger: after it gets a 504, it tries again. sequential.
Framedragger: that's wget, it *retries*.
Framedragger: i'm trying to request a copy of sadmods.
Framedragger: asciilifeform: i'm not hammering it. check your logs.
Framedragger: (so not exactly an 'insist to bring it down')
Framedragger: http://btcbase.org/log/2017-04-10#1641384 << not to rain on your parade but -- without any currently active crawl process, i've tried to wget /sadmods by hand just now, just to have a single copy to serve on the cached site. so far two 504 in a row ☝︎
Framedragger: aha ok.
Framedragger: oh but like, *active* requests? the use of the word "zombie" implied to me that the web requests themselves may have already died. okok.
Framedragger: COPY (SELECT pid, client_addr, query_start, query FROM pg_stat_activity WHERE state <> 'active' ORDER BY client_addr ASC, query_start ASC) TO '/tmp/pg-zombies.txt' WITH CSV DELIMITER ' ';
Framedragger: the following should output stale queries:
Framedragger: ok
Framedragger: asciilifeform: does the new-factor/key-adder write to db under a different db user than the db reader which reads data for the web backend?
Framedragger: (there's a `pg_terminate_backend(process_id)` which can be fed rows from `pg_stat_activity`, just fyi)
Framedragger: have you checked if maybe google army is attacking you now that you've changed the robots policy?..
Framedragger: ok.
Framedragger: that's why i preluded with "if backend connects over tcp"
Framedragger: huh, queries should be cancelled upon a failed http request.. if backend connects to db over tcp socket perhaps check https://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-TCP-KEEPALIVES-IDLE
Framedragger: prolly needs flask restart.
Framedragger: asciilifeform: just fyi i attempted a single wget (single http request) of sadmods, got 500, phuctor main page now 500's :/