log☇︎
120700+ entries in 0.024s
asciilifeform: also exemplary retardation. yeeeeh let's have null-terminated strings!111 we Luuuuuv doing O(N) length calculation, and random breakage !
asciilifeform: pattern and substituted with a list of all filenames that match it.'
asciilifeform: 'If a filename contains whitespace, it undergoes WordSplitting. Assuming we have a file named 01 - Don't Eat the Yellow Snow.mp3 in the current directory, the for loop will iterate over each word in the resulting file name: 01, -, Don't, Eat, etc. If a filename contains glob characters, it undergoes filename expansion ("globbing"). If ls produces any output containing a * character, the word containing it will become recognized as a
asciilifeform: environments in the lisp sense, which resemble c-machine stack frames except not retarded.
asciilifeform: mircea_popescu: the answer is called 'environment' and was a solved problem in lisp circa 1958.
asciilifeform: if 'subshells' were a rare and largely unnecessary thing, that'd be one thing. but shells as a rule offer no clean way of doing 1,001 things other than subbing out to self
asciilifeform: 'correct' in the down's syndrome sense.
asciilifeform: because it has genuinely nfi, apparently, that it is a sub.
asciilifeform: didja know, folks, that you cannot exit-with-return-code the script from a 'subshell' ?
asciilifeform: http://btcbase.org/log/2016-09-29#1550397 << the 'sub-shells' idiocy melted my brain when i was writing http://www.loper-os.org/pub/lam-par/lamport_decode.sh . ☝︎
asciilifeform: ok makes sense
asciilifeform: ( i could even see an argument that, e.g., rawtx eater doesn't belong in trb , and that tx ought to be injected via the ordinary tcp method. but i dun recall having this argument )
asciilifeform: ( or, e.g., http://btcbase.org/patches/polarbeard_add_sendrawtransaction_rpc )
asciilifeform: mod6 et al : was there a particular reason this one -- http://btcbase.org/patches/funken_prikey_tools -- was not considered for the release ? remind me. dun look like this was in the logz...
asciilifeform: whaack: packets sent between btc nodes on the wild net have been known to 'mysteriously' vanish, like in bermuda triangle. the folks who control the backbones dislike bitcoin. the gold standard for syncing a newly-birthed node is to do so with a working node on your lan, or otherwise, if transporting it is impractical, via ssh tunnel to same.
asciilifeform: btw, mircea_popescu , mod6 , et al: might be interesting to have a mempool-less mode (block relay only) for cases like this.
asciilifeform: http://btcbase.org/log/2016-09-29#1550319 << 2g is on the low side. ☝︎
asciilifeform: ^ likewise correct.
asciilifeform: 0000000000000000000000000000000000000000000000000000000000000001
asciilifeform: $ echo "0000000000000000000000000000000000000000000000000000000000000001" | ./lamport_encode.sh privkey.txt | ./lamport_decode.sh sha256sum pubkey.txt
asciilifeform: ^ mircea_popescu, phf , et al. ^
asciilifeform: ^ correct ^
asciilifeform: 0000000000000000000000000000000000000000000000000000000000000000
asciilifeform: $ od -N 32 -An -t x1 -v /dev/zero | tr -d " \n" | ./lamport_encode.sh privkey.txt | ./lamport_decode.sh sha256sum pubkey.txt
asciilifeform: now,
asciilifeform: thing is now... 69 lines.
asciilifeform: article - corrected.
asciilifeform: REGROUND AGAIN.
asciilifeform: whaack: what's in your '--addnode ...' ?
asciilifeform: 'useful'
asciilifeform: BURN
asciilifeform: bc TRUNCATES ZEROES
asciilifeform: MOTHERFUCKER
asciilifeform: 0
asciilifeform: $ od -N 32 -An -t x1 -v /dev/zero | tr -d " \n" | ./lamport_encode.sh privkey.txt | ./lamport_decode.sh sha256sum pubkey.txt
asciilifeform: whaack: and, where are you syncing from ?
asciilifeform: *build
asciilifeform: whaack: describe your built please
asciilifeform: !!up Mariono
asciilifeform: phf et al: http://www.loper-os.org/pub/lam-par/lam-par-genesis.vpatch and http://www.loper-os.org/pub/lam-par/lam-par-genesis.vpatch.asciilifeform.sig have been reground. again.
asciilifeform: -v seems to kill it.
asciilifeform: with flamethrowers.
asciilifeform: burn it all.
asciilifeform: not in the man page, also.
asciilifeform: WHO GAVE YOU PERMISSION TO 'COMPRESS"
asciilifeform: MOTHERFUCKER
asciilifeform: 00000000000000000000000000000000*
asciilifeform: $ od -N 32 -An -t x1 /dev/zero | tr -d " \n"
asciilifeform: but.
asciilifeform: b2c5ca41cc3d8dcbea8b88c549d984191b7839ac3d858bc8fd706cbf85e0927e
asciilifeform: $ od -N 32 -An -t x1 /dev/urandom | tr -d " \n"
asciilifeform: ok, watch this:
asciilifeform: (for the uninitiated, 'busybox' is simply a 'swiss army knife' thing that stuffs simplified versions of ~every~ basic unix util into 1 executable)
asciilifeform: and i realize now that all of my boxes that 'only have sh' are actually busyboxtrons (e.g., pogo)
asciilifeform: aha, it is why you won't find a 'sh' tarball in, e.g., your gentoo's /usr/portage/distfiles.
asciilifeform: http://doc.cat-v.org/bell_labs/utf-8_history << moar lelz
asciilifeform: http://www.loper-os.org/?p=1762&cpage=1#comment-17922 << fwiw.
asciilifeform: also i can't say that i am especially at this point interested in attempts at unix sanitation.
asciilifeform: partly why i have not formally weight in on subj.
asciilifeform: so i can see the angle.
asciilifeform: bash is 'heavy' and somewhat infested (e.g., 'shellshock' circus and sequelae); sh - less.
asciilifeform: http://harmful.cat-v.org << in other lulz
asciilifeform: aha
asciilifeform: aha, i assumed this was their 404.
asciilifeform: mircea_popescu: it 404s.
asciilifeform: bash.
asciilifeform: (bash, that is. not cat-v, who are smart folk and oughta be here)
asciilifeform: mircea_popescu: drepper
asciilifeform: !#s cat-v
asciilifeform: http://www.loper-os.org/?p=1762&cpage=1#comment-17919 << in other noose.
asciilifeform: http://seclists.org/oss-sec/2016/q3/656 << in other lulz, Run Moar IPv6.
asciilifeform: if ssri'd water were economically-feasible, it would probably have been made sop in the '90s.
asciilifeform: the one with the H(S+J) and the multiple timestamps, etc.
asciilifeform: lulzily enough, best as i can tell, 'guy fawkes algo' is actually ~= the scheme i suggested here a few days ago.
asciilifeform: except that it is falsely advertised as 'equivalent to real signatures'
asciilifeform: 'What is actually happening of course is that a middleperson attacking the integrity channel has to participate in it from the start; she cannot join in later' << mighty heavy limba de lemn ...
asciilifeform: since when is 'the onus would be on the objector' ?!
asciilifeform: ntion (such as a digital signature law, or a contract between members of an EDI system) and the validation of even conventional digital signatures involves reference to an online or at least near real-time certificate revocation list.'
asciilifeform: 'So if it is claimed that the Guy Fawkes protocol is not really a signature, then the onus would be on the objector to show how to deal with the many other kinds of signature that use interaction, as well as the importance of context — the framework of certification and revocation services, legal conventions and so on — to the utility of digital signatures. In most applications, the value of signatures ultimately depends on conve
asciilifeform: and holy FUCK, the sheer depth of retardation,
asciilifeform: for BingoBoingo ( or whoever put it there ) >> https://www.reddit.com/r/cryptography/comments/55077h/how_to_make_your_own_lamport_parachute_from/d86tmfi
asciilifeform: think 'pgp but with delegation to slaves'. usg is/was for some reason obsessed with such schemes.
asciilifeform: )
asciilifeform: (in actuality, in 'identity-based' crypto, folks actually encipher to a pubkey that is produced by F(Pc, X) where Pc is the chump's email addr and X is a public key of the great inca; chump (email addr holder) can decipher with his Pk_c private key, and so can the inca. ☟︎
asciilifeform: http://btcbase.org/log/2016-09-29#1550160 << lulzily enough, the fact that it is physically impossible to generate a ~private~ privatekey from a public string... didn't stop usg from trying! see old thread, http://btcbase.org/log/2015-04-02#1084135 ☝︎☝︎
asciilifeform: either these folk never tire, or the rubbish is actually churned out by fresh crop of conscripts every quarter
asciilifeform: 'He was concerned about the team’s communication skills and lack of maturity, which has compromised bitcoin’s ability to attract new protocol developers.' << lel
asciilifeform: ^ further use cases for lamportron.
asciilifeform: adlai: http://www.loper-os.org/?p=1762&cpage=1#comment-17920
asciilifeform: i aim to salvage these. lamportron, for instance, is entirely suited to hand-cranked use in junglr conditions - 0 bignums...
asciilifeform: part of a family of 'lost hand-cranked technologies'.
asciilifeform: *treatment
asciilifeform: vic was historical, and interesting, and the linked trestment is not wholly bad.
asciilifeform: 'The ultimate development along these lines was the VIC cipher, used in the 1950s by Reino Häyhänen. By this time, most Soviet agents were instead using one-time pads. However, despite the theoretical perfection of the one-time pad, in practice they were broken, while VIC was not.'
asciilifeform: if we must pediwikiate, more interesting is https://en.wikipedia.org/wiki/VIC_cipher .
asciilifeform: or weevil. or somebody.
asciilifeform: well, say, an ant.
asciilifeform: noshit.
asciilifeform: also worth noting that , when he finally keeled over at his desk, the replacement was ~same.
asciilifeform: >1.