asciilifeform: after the gossified one is up

asciilifeform: but it'd be a not-altogether-terrible way to kill the rangers' net

asciilifeform: and the possibility of it existing is a bug

asciilifeform: imho rather than a useful thing, it is actually a molasses-attack vector on the btc net

asciilifeform: !s pseudonode

asciilifeform: https://github.com/basil00/PseudoNode

asciilifeform: (it's a 50kb c proggy)

asciilifeform: everybody knows where to get it.

asciilifeform: which exists.

asciilifeform: that'd there be pseudonode.

asciilifeform: aws storage is, iirc, costly. this was one of the motivations for the enemy 'spv' crud etc

asciilifeform: at any rate, whoever wants to do this, knows how, it is not a mega-pr0j3ct

asciilifeform: fleet aha

asciilifeform is familiar but not in trbfoundation

asciilifeform: mircea_popescu: yeah but questionable gain

asciilifeform: watch'em piss pants

asciilifeform: and yet if we had 10,001 of these it would make for some mild lulz

asciilifeform: but this is only mildly interesting and i will probably forget to watch very soon.

asciilifeform: BingoBoingo: part of the motivation for my experiment is to see how long it will be before they start 'accidentally' censoring it

asciilifeform: aha, exactly this

asciilifeform: without recompiling.

asciilifeform: and incidentally BingoBoingo, should he make use of this patch, can easily set another

asciilifeform: otherwise it simply happens to be the version string used by my nodez.

asciilifeform: BingoBoingo: if the latest patch is ratified by the latter, then yes

asciilifeform: BingoBoingo: my patches do not represent the official papal view of therealbitcoinfoundation

asciilifeform: not even speaking of these.

asciilifeform: thinkaboutit

asciilifeform: (an unsynced trb node is not good for much! because it rejects most tx)

asciilifeform: BingoBoingo: aha but now it is synced

asciilifeform: zoolag is also running same, as of last night.

asciilifeform: this is a press of the programmable-versionstring patch and down.

asciilifeform: and kudos to mircea_popescu for providing a very spiffy box, on which phuctor will also very soon return

asciilifeform: with the frozen deps

asciilifeform: (rotor, if anyone forgets, is a static build from a locally-built gcc toolchain)

asciilifeform: incidentally, gentlemen, please welcome (back) dulap! 46.166.165.30:8333 (nosuchlabs.com), a trb node running bleedingedge-asciilifeform+rotor(musl) ☟︎

asciilifeform: what we have now, takes the vpatch's word for it.

asciilifeform: mod6: ideally a vtron would follow along as the patches are applied and actually verify the hashes, yes

asciilifeform: http://log.bitcoin-assets.com/?date=19-12-2015#1348061 << what, precisely, is 'not bad' about it? it's 100% braindamage by weight and by volume ☝︎

asciilifeform: http://log.bitcoin-assets.com/?date=19-12-2015#1348050 << you know what's great? rat poison STILL WORKS even if you don't explain to the rats exactly ~how~ ! ☝︎☟︎☟︎☟︎

asciilifeform: (as far as peter w is concerned, apparently)

asciilifeform: but somehow it Never Happened !11111 (tm)

asciilifeform: http://log.bitcoin-assets.com/?date=19-12-2015#1348027 << this cost a good number of chumps their coin, aha ☝︎

asciilifeform: because mine, as everybody knows i think, did not.

asciilifeform: http://log.bitcoin-assets.com/?date=19-12-2015#1348022 << there is no other way to do it! what i was asking was whether anybody's 'v' actually verifies that patching in the given sequence actually yields files having specified hashes. ☝︎

asciilifeform: (and 'rng with whitening' which IS a prng)

asciilifeform: for exactly same reason as prng !

asciilifeform: whether you and i can demonstrate how, or not.

asciilifeform: punkman: precisely what i was speaking of, except that i conjecture that ANY deterministic signing process is kleptographic

asciilifeform rather surprised anybody still has one of these for sale

asciilifeform: http://www.retrogames.co.uk/040022/Sega/Sega-Dreamcast-Development-Console << example of item used then

asciilifeform: but this is elementarily obvious.

asciilifeform: the up-side of slow and finicky comps was that there was a lower limit to the dev iq and a hard upper limit to code bloat.

asciilifeform: sure did.

asciilifeform: BUT nothing 'curl'ed during compile, no.

asciilifeform: docs were hastily-written and inaccurate, vendor support - spotty, compilers - buggy, architectures - quite 'turkish' and requiring serious asm massage just for acceptable performance.

asciilifeform: (my brother did this, still has some of the very peculiar hardware)

asciilifeform: anyway ipnohe devs think they have a terrible time, but try being a '90s game dev for consoles

asciilifeform: quite the zoo.

asciilifeform: (iirc this is nontrivial)

asciilifeform: ben_vulpes: do you test on an actual physical ipnohe ?

asciilifeform does not recall any such atrocity when he did ipnohe

asciilifeform: cannot compile on airplane?

asciilifeform digs futilely for thread

asciilifeform: i had this reason ~2y ago l0l

asciilifeform: 'only usg knows how to open this box therefore nobody'

asciilifeform: this is quite like the 'rng whitening'.

asciilifeform: which is ~exactly~ what we get in that rfc.

asciilifeform: but you ALSO get same if the same mathematical relationship can be derived from deterministic k.

asciilifeform: you get the leak in a straightforward way if k is REUSED

asciilifeform: deterministic --> moar breakable !111 omfg

asciilifeform: Since the k is deterministically generated from the data you are signing (and the private key), these concerns about the PRNG are no longer as relevant, as you will always produce the same signature for the same piece of data. This also makes writing ECDSA unit tests easier.'

asciilifeform: 'Also note that one of the key benefits of using this construction is that you need not worry about a weakness in your PRNG being exploited in the signing process. For example, signing different pieces of data with the same k value instantly leaks your private key. A similar attack can also be exploited if the PRNG is weak enough to determine the relationship between different k values used when signing the same piece of data.

asciilifeform: http://bitcoin.stackexchange.com/a/36142 << i am unable to grasp how the claims could possibly be true

asciilifeform: mircea_popescu: aha. you can go and read the gcc (or even clang) front end and see how.

asciilifeform: punkman: i am still hard pressed to see how it is anything other than a disastrously bad idea

asciilifeform: this thing with 1 or moar spaces on each side.

asciilifeform: aha because we can agree on what a word is

asciilifeform: because in cpp a 'function' is a complicated notion

asciilifeform: mircea_popescu: EXACTLY as hard as the graph

asciilifeform: https://bitcointalk.org/index.php?topic=285142.0 << lulzy

asciilifeform: see the callgraph thread!

asciilifeform: mircea_popescu: even THIS is hard

asciilifeform: aha but gotta tokenize

asciilifeform: i'll wait.

asciilifeform: go, tokenize cpp.

asciilifeform: because (as we learned in the callgraph escapade) this is hard.

asciilifeform: mircea_popescu: ah that case. github doesn't parse languages

asciilifeform: needs graphical wwwtron yes

asciilifeform: ^

asciilifeform: btw that is the ONLY supported nonce gen fuct ~despite~ a carefully crafted appearance to the contrary

asciilifeform: can anybody tell me WHY ?

asciilifeform: https://github.com/bitcoin/secp256k1/blob/master/src/secp256k1.c#L314 << lulzy

asciilifeform: but idiots will tell you that shit is the new food

asciilifeform: PeterL: you don't

asciilifeform: each of the latter individually enclosing a totally nonportable turd

asciilifeform: 'portable' on my planet means PORTABLE and not a gaggle of #ifdef's ☟︎

asciilifeform: i must disagree

asciilifeform: which is READABLY light.

asciilifeform: but if we're gonna terraform existing item, i'd much prefer the nano ecc thing.

asciilifeform: sure