log☇︎
1600+ entries in 0.148s
asciilifeform: iirc somebody had a defang patch for it
diana_coman: asciilifeform, hm, I should get my '80s cobra then? centos 6 is not even recent tbh; but otherwise yes, I believe re no need to patch
asciilifeform: diana_coman: naive orc asciilifeform picked rs232, 1960s-era protocol, because he actually thought 'no one! will have to patch kernel', can you believe.
diana_coman: asciilifeform, one can patch the kernel to work with both pl2303 AND pl2303x; but otherwise yes, obv is obv, either actual serial port or otherwise finding a combo that works
mod6: <+mircea_popescu> also, ima jungle today, might not have the patience to cut up patch for sat dish. << cool!
mircea_popescu: also, ima jungle today, might not have the patience to cut up patch for sat dish.
asciilifeform: BingoBoingo: see my measurements patch, and output, on the ml.
mircea_popescu: which is what exact breach in the glorious blue pantsuit the above item is trying to patch
asciilifeform: losure deadline was around the end of August. As a compromise, I allowed them to silently patch the vulnerability. In hindsight this was a bad decision, since others might rediscover the vulnerability by inspecting their silent patch. To avoid this problem in the future, OpenBSD will now receive vulnerability notifications closer to the end of an embargo.'
a111: Logged on 2017-09-14 05:30 trinque: in the process, realized I oughta publically denounce something in the funkenstein importprivkey/dumpprivkey patch
trinque: asciilifeform: there's no hot wallet here; I'm marching my ass over to another box and making signed tx, then popping into a trb with polarbeard patch for sendrawtransaction
asciilifeform: ( pro tip: when you patch and dun say why, there is a staff of 15,000+ people who do nuffin but to see exactly why )
asciilifeform: as typical, he 1) patched 2) withheld the implications of the patch from all but usg
asciilifeform: ( btw i always found it interesting that the unix authors never saw it fit to include a binary equivalent for diff/patch . but iirc we had this thread. )
asciilifeform: ^ which does mean that i'ma have to a) audit the binary when ffa built for use in the field b) patch gcc/gnat not to emit DIV ☟︎
trinque put this in what'll end up a patch for some key tool binaries.
trinque: in the process, realized I oughta publically denounce something in the funkenstein importprivkey/dumpprivkey patch ☟︎
mircea_popescu: http://btcbase.org/log/2017-09-08#1711512 << run instrumented always while preparing a patch/v-root ; never when compiling from an existing v-tree. simple rule, no reason not to follow. ☝︎
trinque: http://btcbase.org/log/2017-09-04#1710704 << hm, don't think I've modified that for deedbot; how'd I be getting around it? that said, stripping the nonsense if present sounds like a sane patch. ☝︎
trinque: used to do all kinds of "patch this file in that dir with leethax.exe" when I was in teens
mircea_popescu: incidentally, the deahtspital would be a very useful addition to the clinical system. open for ppl over 60, they give you a list of things. "hello mr smith. you're 68, and we can tell you that your kidneys will kill you in a decade, except your heart will get you before you're 75, and then there's this patch of skin cancer that needs like 20 years at your age. stay out of car crashes and sudden falls."
ben_vulpes: null patch is best patch/steal from the best
ben_vulpes: bringing a trb node up on whatever gentoo image scaleway has; 'pthread: command not found', log notes indicate patch necessary to cmake CheckIncludeFiles.cmake, investigation of which shows...no cmake on this box
asciilifeform: pete_dushenski: as i understand it's a couplea line patch to trb
asciilifeform: !~later tell ben_vulpes was it you who had a trb patch abolishing the idiotic truncation of block and tx hashes in debug.log ? where did it go ?
mircea_popescu fully expects something on the level of "oh, if you want patch you have to say explicitly" sorta nonsense.\
mod6: my V doesn't use diff anyway, only patch, gpg, sha512sum, and wget -- and otherwise just standard shell tools such as echo, mkdir, rm, cat, etc.
mod6: I think it was patch, but yeah, maybe I'm mis-remembering that.
PeterL: didn't sign anything yet, nothing to patch off of
erlehmann: 5. make is unfixable, but we can patch gcc!
erlehmann: 4. yes the effect matters. we can patch make, though
mircea_popescu: well, systems without patch are also retarded.
mircea_popescu was bracing self for "o look, new version of patch, breaks downstream" lulz.
edivad: now just installed patch on the right vps
mircea_popescu: this is bizarre. try the actual line from the .sh that fails ? (prolly the first one to string match "patch") ?
edivad: patch is already the newest version (2.7.5-1).
mircea_popescu: will prolly have to add patch to the pile at the end eh.
mircea_popescu: edivad sudo apt get patch eh.
trinque: no, you're missing the utility patch.
trinque: > patch: not found
a111: Logged on 2017-08-06 15:30 asciilifeform: BingoBoingo et al : to be very specific, the wedged box is running a press of mod6's 0.5.4-release, with the only change being phf's bsd patch linked yesterday.
asciilifeform did go back and verify that in fact it has the locks patch and is indeed mod6's release + phfpatch -- rather than asciilifeform's mistake
asciilifeform: this thing behaves precisely like trb sans locks patch, i think
asciilifeform: BingoBoingo et al : to be very specific, the wedged box is running a press of mod6's 0.5.4-release, with the only change being phf's bsd patch linked yesterday. ☟︎
asciilifeform: went away on linux ( and apparently openbsd ) from locks patch, and that was the end of the thread
phf: until you can actually reproduce the nature of locks patch vs. block (or whatever wedges)
phf: ~you can't reason about locks patch~
asciilifeform: my suspicion is that the bdb locks patch somehow has no effect when bdb built on netbsd ☟︎
asciilifeform: but fixed by mp's patch 2.5y ago. and apparently unfixd by bsd
asciilifeform: ( i have 0 instances of wedged bring up on linux since mircea_popescu's bdb patch, in 30 or so shots on machines in various spots )
mod6: <+phf> that's because you didn't try to simply use the patch to makefile that i posted on the list << i've had a trb openbsd since you posted this yes.
phf: which reminds me that i need to regrind my shiva swank patch, which is broken
phf: that's because you didn't try to simply use the patch to makefile that i posted on the list
mod6: Haven't heard back yet, but instructed to install whatever package contains `patch` and proceed from there.
mod6: <+ben_vulpes> edivad: what kind of system are you building trb on that shipped without `patch`? << this is the same thing I said.
ben_vulpes: edivad: what kind of system are you building trb on that shipped without `patch`?
asciilifeform: they still have sore starfish from 'wannacry' using nsa's beloved 'unpatchable' hole, and pressure building for patch of same
asciilifeform: but i have nfi how much it costs you, you would have to make a profiling patch similar to mine and see.
asciilifeform: ( wires patch currently is just epsilon short of useless, because of the asinine default block sync algo )
trinque: I may have misunderstood the wires patch behavior.
mircea_popescu: hey, there's such paucity of ideas in the fiat world, it's somehow unsurprising when escaped victim goes hog wild in the clover patch.
asciilifeform: ben_vulpes: you have the low-S patch , neh ?
asciilifeform: if you use infected idiots, you're stuck explaining what's to keep'em from reinstalling winblows + patch against whatever door you walked in through.
asciilifeform: ave1: gonna have to patch , then, and cure the retardation.
daffadil: "Friendship" is just a transient software patch that we install on one another.
asciilifeform: a 8192b key, not yet known, because gotta patch it to even allow one
ben_vulpes: "sorry for the inconvenience sir, you have a good day now. you know they keep saying there's a patch coming that'll improve battery life for these things, but i haven't seen it yet." "heh yeah and i don't beliueve that it'll work."
sina: asciilifeform: btw I was going to ask you about your feelings on this https://github.com/cforler/Ada-Crypto-Library ...obviously hasn't been impl for constant time/space but regardless. may be possible to ctgrind it using that valgrind patch I linked in the logs
asciilifeform: want change ? that'll be a new patch, and 1 or more new sigs.
js-of-mp: this shit is addictive btw, anyone noticed ? i had to have them cut out a patch of jungle overnight and there's six confused locals holding up strange religious artefacts, just so i can catch up on logs
trinque: reminds me, I haven't tried your getpeerinfo patch yet
BingoBoingo: And you get weird DMZ border area until next patch
BingoBoingo: It does do well for very dense patches, but hard to make a monoculture lawn out of it, because with the sligtest change in grade or soil, patch ends
mircea_popescu is not very keen for eg on "tsr" insta-kerne-patch-from-userland bs
mircea_popescu: i suppose "driver" in context might mean a kernel patch to feed /random from fg
shinohai: !~later tell pete_dushenski Tested your patch, built fine, running on the dev box as I write this.
phf: http://btcbase.org/log/2017-06-12#1669038 << i had some interop going between v and https://www.mercurial-scm.org/wiki/MqExtension. apparently before cvs but after "copy entire folder to make a version" there were various approaches to maintaining patch sets, that can be applied to v's folder full of patches approach ☝︎
ben_vulpes: "genesis" is argot for root of a patch tree
ben_vulpes: sina, i have a patch sitting in my tree that will paste output as well
mircea_popescu: "oh, but we patch that". sure you do. and who's gonna feed the boy genius that manages all the patchcomplexity ?
asciilifeform: btw there is a dbus-remover patch for chromium, somewhere
erlehmann: reason: i wrote a vintage filter for GNOME 3 when i discovered their screenshot app has a postprocessing step. i submitted patch and one person saw it as the garbage it was intended as, but then others were like WHAT A COOL EASTER EGG MERGE.
asciilifeform: http://btcbase.org/log/2017-06-03#1664879 << v is -- properly considered -- an abstract concept, quite divorceable from the abominations of gnudiff/patch and gpg ☝︎
phf: so hitting http://btcbase.org/patches/funken_prikey_tools/tree/bitcoin/src/init.h runs patch algorithm on a series of vdiffs
phf: it does an equivalent of patch, but without calling out to c programs and without the result (or intermediate steps) touching the file system at any point
erlehmann: well, vdiff would never be possible if diff and patch were definite about their inputs
phf: (fwiw it has complete understanding of patch, so it can also do a press in memory, e.g. http://btcbase.org/patches/funken_prikey_tools/tree/)
phf: for sure, btcbase is probably the most aggressive, because there's a very restricted state machine for parsing, but there's still some ambiguity in recognition that's an artifact of diff/patch being dodgy
phf: erlehmann: so the arrow from nowhere basically means that the patch is broken, because it requires an antecedent that's missing
erlehmann: phf your patch visualizer linked here http://cascadianhacker.com/07_v-tronics-101-a-gentle-introduction-to-the-most-serene-republic-of-bitcoins-cryptographically-backed-version-control-system is apparently gone
ben_vulpes: CluelessNoob: please to paste results of using gpg to verify patch in question against signature in question
BingoBoingo: Patch with trowel
mircea_popescu: no. the "wires patch does little more than spam the log" conclusion was had about a week into the wires experiment.
mircea_popescu: wires patch is not different ; still same trb.
asciilifeform: no, speaking here of 'wires' patch
mod6: re: http://thebitcoin.foundation/tickets/trb_tickets.html#1 << this one seems to be resolved with the use of -lows. I hesitate to remove the ticket, but a link to the patch might be worthwhile here.
asciilifeform: the idiotic 'looping' cannot (afaik) be switched off. (yes i could patch the src but the result will be a nonstandard tester )
danielpbarron: yeah it's all good. once i removed those headers from all the patch files it pressed fine
asciilifeform: btw seems like they also twiddled the ecc params in that patch
asciilifeform: '2017-02-21: The patch is surreptitiously snuck into the Monero codebase in pull request #1744. It is kept secret to prevent it being used to attack other CryptoNote coins.' ☟︎