log☇︎
85100+ entries in 0.029s
asciilifeform: ( this should not horrify, but encourage. the logs are a very handy resource. )
asciilifeform: sina: if you've been reading anything other than the logs, you have a great deal of catching up to do.
asciilifeform: sina: subject is considerably trickier than charlatans (e.g. schneier) let on. in fact, most of what is available on the net, is deliberate disinfo.
asciilifeform: same statistics apply.
asciilifeform: i break ONE - i break whole chain.
asciilifeform: not reusing the keys would do 0
asciilifeform: ( unlike, e.g., gpg, ssl, the rest of the shit soup )
asciilifeform: this means ALL ciphertext is the output of rsa modular exponentiations.
asciilifeform: there is rsa-only crypto.
asciilifeform: for one thing, there IS NO SESSION in gossipd (either my concept or either of mircea_popescu's two essays) ☟︎
asciilifeform: and if you don't understand why, you should not be using rsa
asciilifeform: sina: again no
asciilifeform: even 1, cuts the amount of practical work necessary to break your key, considerably.
asciilifeform: not even necessarily >1.
asciilifeform: sina: not necessarily very many.
asciilifeform: sina: if some % of the time i can determine how long it took you to carry out a secret key op (incl. key generation) i can determine a few bits of key. over time, i get 1/4 of them, and that is == to getting the rest.
asciilifeform: sina: are you familiar with the concept of timing side channel ?
asciilifeform: !#s ffa
asciilifeform: sina: i've been writing one, for some months now.
asciilifeform: sina: one of the things gossipd needs is a constant-time-constant-space rsa. if you don't have one, enemy can derive your privkeys remotely based on timing. ☟︎
asciilifeform: sina: at least a few folx were playing with very similar things even before mircea_popescu wrote his essay
asciilifeform: and... who knwos who else
asciilifeform: and asciilifeform yet other
asciilifeform: and iirc trinque had another
asciilifeform: phf has a very similar gossipd in commonlisp, for instance ☟︎
asciilifeform: sina: but understand that the problem does not resolve to '200 lines of py' or would have been solved years ago and we'd all be using.
asciilifeform: sina: don't be discouraged
asciilifeform pictures pogo stick stake
asciilifeform: because it isn't as if you can get decent chair here.
asciilifeform: but say i also make own chair. then which must i be... shoe maker, or chair maker..?
asciilifeform: 'if yer making shoes, you oughta be a shoemaker'
asciilifeform: i suspect he'd laugh even moar heartily if i were sitting and making own shoes
asciilifeform: still depressing; my emulated mircea_popescu sat on my shoulder invisibly laughing
asciilifeform: because a) can't be arsed to go to town to get new one b) ain't like you can get nonchinese sandal anyway
asciilifeform: *pair of
asciilifeform: for the 3rd time
asciilifeform: epoxying, i shit thee not, a paid of shoes
asciilifeform: heya mod6
asciilifeform: https://archive.is/7bx0V << upstream in same thread << apparently he tried to draw a line, 'stfu with the monolithic unreadable patches'
asciilifeform: meanwhile, 'thief cries thief', https://archive.is/vgrDP << organized pantsuit ouster of linus t. slowly crystallizing...
asciilifeform: and that 'your' horse is somehow still 'your' AFTER you join kolhoz.
asciilifeform: gotta luvv the folx so slow on the uptake, who imagine being in 'a community' while having already been subsumed into usg faceless mass.
asciilifeform: from earlier, lulz, 'In April 2017, an unexpected and disruptive change was made to the MIT network: the sale of historically MIT-allocated IP address ranges to external entities such as Amazon. The sale wasn't announced to the MIT community until after it had taken effect. ' ☟︎☟︎
asciilifeform: ahahaha
asciilifeform: ChanServ [ChanServ@services.] has quit [shutting down] << lolwat
asciilifeform: lol
asciilifeform: and the necessary bits -- reduce to a slightly generalized vtron.
asciilifeform: certainly not in the form offered.
asciilifeform: for fucks sake.
asciilifeform: MY SHELL IS STILL SET TO THE KING'S ENGLISH
asciilifeform: and i say this as an orc, who uses cyrillic
asciilifeform: which SHOULD NOT BE A THING
asciilifeform: and produced differing orderings depending on the 'charset' set on the machine
asciilifeform: gnudiff, i found, in fact DID misbehave, on many a box
asciilifeform: erlehmann: 1) i have nfi what it does on corner cases 2) i have nfi how consistent is it across unixen, and how it misbehaves with, e.g., crapolade turdicode characters in the inputs
asciilifeform: erlehmann: yes
asciilifeform: ( what's a 'misproblem' ? let's say it is a problem that only exists because of misapplied concepts earlier 'up the stack' . see also the immortal prof. kokkarinen's 'alien problem', http://btcbase.org/log/2014-11-26#934852 thread . ) ☝︎
asciilifeform: immutable past is a prerequisite to ~authenticable~ past, and v gives it.
asciilifeform: this is essential to v.
asciilifeform: but outputs of presses to OLD nodes -- will give same output 1000 yrs from now, as today.
asciilifeform: outputs of presses to ~new~ nodes, will, naturally, give unseen-before output.
asciilifeform: nope. outputs of presses to a given node on the flow - will NEVER change.
asciilifeform: not only sensible, but thermonukes away entire, as you see, ~classes~ of misproblem.
asciilifeform: no changing-of-the-past. ☟︎
asciilifeform: want change ? that'll be a new patch, and 1 or more new sigs.
asciilifeform: immutable, motherfuckers, datastructure.
asciilifeform: that's the thing with v : inputs NEVER CHANGE
asciilifeform: why the fuck would it CHANGE ?!
asciilifeform: they don't belong being visible !
asciilifeform: erlehmann: you DON'T TOUCH THE ALREADY CONVERTED ONES omfg
asciilifeform: ( and noshit.jpg, 'entire works of mankind as 1 tree' leads to 'infeasible in terms of time and computing power available' )
asciilifeform: and there are things in it that ought to be separate trees.
asciilifeform: if 'full builds are infeasible', your tree is mis-structured. ☟︎
asciilifeform: what's that got to do with whether a maketron ought to be able to do partial builds ?
asciilifeform: wassat
asciilifeform: whereas small codebases build quickly enough that partial rebuilds are unnecessary.
asciilifeform: because i'm quite certain that the existence of large codebases is NOT justified.
asciilifeform: erlehmann: i'm not sure the existence of partial-builds is even justified.
asciilifeform: he explains it better than i ever did.
asciilifeform: erlehmann: or at least read ben_vulpes's classic article re subj, http://cascadianhacker.com/07_v-tronics-101-a-gentle-introduction-to-the-most-serene-republic-of-bitcoins-cryptographically-backed-version-control-system
asciilifeform: erlehmann: indeed it does. read the source.
asciilifeform: process-input-until-next-MAGICSTRING ( aka in-band signalling ) is inescapably and fundamentally braindamaged.
asciilifeform: noshit.jpg
asciilifeform: ( see also mega-thread , http://btcbase.org/log/2014-10-29#901052 ) ☝︎
asciilifeform: somehow LEAVE MY MOTHERFUCKING BITSTREAM ALONE is not an option if you're transmitting 'ascii text'
asciilifeform: which in fact get mutilated by ~every piece of shit attached to the net
asciilifeform: and you would also have to not-disregard newlines
asciilifeform: see also gpg's '-' idiocy
asciilifeform: so if you wanted to distinguish 'proper' vs 'bug' +++, you would have to make the grammar CONSIDERABLY more complicated, and transform the ENTIRE input text, and then un-transform it BACK, every time
asciilifeform: it is indeed
asciilifeform: erlehmann: the +++ thing was actually a more serious problem than you might walk away thinking on first reading -- because it is physically impossible to fix it without MAKING NEWLINES SIGNIFICANT semantically
asciilifeform: which is a problem.
asciilifeform: maybe it does, maybe it doesn't, but it'd take same, IF NOT GREATER, effort, for asciilifeform to ascertain the truth of this statement, as to rewrite the linked proggy
asciilifeform: erlehmann: http://btcbase.org/log/2016-12-11#1581252 << see thread, for instance. ☝︎
asciilifeform: all in-band signalling is subtly wrong.
asciilifeform: lolk
asciilifeform: erlehmann: that looks a lot like my original vdiff.
asciilifeform: but gotta remember, erlehmann , that one man's 'this is ON EVERY SYSTEM, motherfuckers, not an optional shitlib' is another's optional shitlib.
asciilifeform: nothing wrong with that.
asciilifeform: but with c compiler.