asciilifeform: mircea_popescu: if it's for cipher keys -- imho terrible idea to have ~all~ the key bits as physical switched in parallel, third party has no biznis being able to see the key simply by getting a peek at a keyed box with eyes

asciilifeform: mircea_popescu: what sorta switches are you thinking of ? if it's ye olde DIPs, nobody cancelled'em, they're maybe a dime for a block of 8, and look today exactly as you remember then from yer 286

asciilifeform: |\n: if it was shown to you as 'omfg exploit!111', you've been duped.

asciilifeform: evidently sumbody passed it off to |\n as an 0day

asciilifeform: 'As explained in Section 7.2, we use ASM.JS code in Firefox 50 to trigger the implemented x86 div Trojan. It is shown in Listing 9.'

asciilifeform: mircea_popescu: i view block ciphertrons as a 'slightly better than nuffin' kind of tech -- would slightly rather lose a serpented disk to enemy than naked one; but that's about it

asciilifeform: is the actual parallelism of the algo. the rotator would likewise win from having 32 physical instances, as obvious from http://ossasepia.com/2018/02/22/eucrypt-chapter-11-serpent/#selection-87.15048-87.17527

asciilifeform: mircea_popescu: as in, whether it actually sboxates at the stated 25MHz ? notyet, gotta write a serial i/o thing for it, to do this. possibly later today.

asciilifeform: diana_coman: until you wrote the recent piece, i actually forgot that mpi ~didnt~ shit out ordinary octet arrays as-supplied

asciilifeform: the front end aint gonna change, so potentially could, as i understand

asciilifeform: i suspect , was same enamel as on actual rockets..

asciilifeform: re those oaken tables, good as new 200+ yrs into their duty cycle.

asciilifeform: BingoBoingo: the cloned brix were amazing, survived all kindsa mechanical abuse without so much as a scratch, much less brea

asciilifeform: BingoBoingo: keep in mind that the lego you had as a boy, hasn't existed in decade+ , afaik, per http://btcbase.org/log/2017-09-02#1710146 ☝︎

asciilifeform not a great luvvver of symmetricipherism in general, as amply illustrated in the l0gz, for this and other reasons -- there is no known approach to bake symmetricism from any sort of rational angle

asciilifeform: mircea_popescu: classical serpent eats 256bit key. but ( as illustrated in http://ossasepia.com/2018/02/22/eucrypt-chapter-11-serpent/ ) eats/shits 16 byte payload blox as it goes; a 4096 byte flash sector would need 8 of these, plus i suspect a 9th for the block # ( see earlier re 'known plaintext'ism etc )

asciilifeform: the native one the korean nands give you is usually 4096 as it is

asciilifeform: approx same 'by byte' as ordinary 2.5" samsungs

asciilifeform: mircea_popescu: nope, as in fact noted in the head of thread, http://btcbase.org/log/2018-10-26#1866343 ☝︎

asciilifeform: and will point out, errybody who transmitted rsa-over-serpent in the 20yrs prior to $breakthrough is just as hosed as the folx who were using pocket iron serpentrons

asciilifeform: so long as it sits down in 8k gates

asciilifeform as errybody knows, never actually throws out iron!111 so haha!, still has mouse! was rhetorical device

asciilifeform: they didn't line up to buy FG.. ( it dun scratch any heathen itches ) whereas this item potentially does scratch, as i understand

asciilifeform: it is a kind of 'escherian', as mircea_popescu likes to describe, object.

asciilifeform: as in, with 4096b ( really you want double of this, given how modexp works ) arithmetizer block in the fabric ?

asciilifeform: you have a box, that presents as e.g. usb drive on 'red' end, and eats a e.g. sd card on 'black' end, with a thing between the two that serpents and unserpents (how to key it, is a separate conversation, but it can be keyed sanely so long as it is done not from pc end )

asciilifeform: presents as ordinary disk when connected/keyed.

asciilifeform: to continue in these lulz : ada std has a 'bounded string' type, that superficially is defined as exactly how i wanted to do 'path' type earlier. but! but! if actually invoked, it -- for no logical reason afaik -- prevents the invoking package from being declared stateless ( i.e. pragma Pure ), and this propagates ad infinitum , to caller.

asciilifeform: i'd almost go so far as to specifically disrecommend study of the stock standardlib, it is actively bad for health

asciilifeform: just as started udp thing by going 'hm wai not fix gnatsockets' and... ~lost~ month

asciilifeform: and errything else i've written worked a++ as them.

asciilifeform: my only remaining notion here is that possibly gotta implement a 'paths' lib ! i.e. would represent paths as arrays of permanently fixed length , 255 octets, iirc this is the max permitted on unixlikes. ☟︎

asciilifeform: meanwhile, in gnat bugs : apparently ( and this is documented or mentioned nowhere ) : it is impossible to have a Ada.Finalization.Limited_Controlled type ANYWHERE inside a static library, unless it is generic all the way down (i.e. if the lib package is generic, any sub-packages must also be instantiated as generics ) ☟︎☟︎☟︎☟︎☟︎☟︎☟︎

asciilifeform: disk, in so far as i can tell, is alive ( no eggogs in dmesg )

asciilifeform: at the risk of repeating ancient thread -- 'the best machine is no machine', it weighs nuffin, needs no maintenance. and the best proggy, is no proggy at all, if a problem can be solved without writing proggy, it ought to be. erry line of coad can be rightfully pictured as an act of intellectual littering. y'know, like throwing cig butt or bottle on the ground in the park. ☟︎☟︎

asciilifeform: for so long as we're stuck on a linux box, i'd rather spackle over the c-ism with 600 ln, than with 6000 .

asciilifeform: bvt: suspected as much

asciilifeform: as by asciilifeform -- the pill which weighs the least, is the Right Thing, per http://btcbase.org/log/2018-10-25#1866148 , an absolute minimum , line for line, of os-specific liquishit, is the ticket. ☝︎

asciilifeform: bvt: i do not know for a fact whether it eats same struct as the userland call, or different

asciilifeform: i'ma genesisate it as soon as i figure out a workaround

asciilifeform: cuz may as well; if we ever tear off unix , will have to replace those mechanisms anyway

asciilifeform: bvt: they differ for same reason as tit sizes -- nobody ever standardized, so naturally varies

asciilifeform: so any particular proggy can call e.g. open() with correct flaggisms, because it aint as if the gnat on the $box does not already know what os/iron it sits on.

asciilifeform: i would've naively imagined that massive 'contrabass' like this would may as well include the uv lamp. but apparently didn't.

asciilifeform: ( and can have almost anyffing as the core, even vacuum, all transformers saturate )

asciilifeform: btw -- and iirc we had the thread -- there are even deeper crackpotteries potentially in the mix : it is possible to have strictly magnetic logic, without semiconductor. if can simply etch fine metal mask, interleaved with insulator, potentially can have a kind of slow 'z80' from miniature toroid logic (as seen in '60s su)

asciilifeform: you want an end product that conducts thermally as well as electrically, or you get a lighter.

asciilifeform: mircea_popescu: re 'ion pump' upstack , in olden days when asciilifeform worked as academi-grunt in a bio lab, did many long hours of snore at electrophoretic 'blots', where chromatographic rubbish moves along a gel. and thought 'why not bake ic this day, what if you give it 2nd axis to steer the current' etc

asciilifeform: mircea_popescu: regularly there's word from some d00d who actually bought surplus gear ( see e.g. linked thread ) and 'omfg, i made a diode!' , typically as far as they get ( and it wasn't even because usg.dhs came for his flourine , afaik it did not )

asciilifeform: at some point he gives up guarding it, as it costs sumthing, and the gypsies move in, i suppose this can be seen as a form of 'sell'

asciilifeform: the actual physical procedure of baking the ic is not as standardized as i previously (to last thread) thought.

asciilifeform: it is not available as off-the-shelf service anywhere, afaik, nope.

asciilifeform: i wouldn't go so far as 'can't', but we're talking 'lease $B plant for 6mo.' sort of figure.

asciilifeform: as i currently understand, that means vertical integration, i.e. building the plant.

asciilifeform: mircea_popescu: the sad bit is that conventional asic process , as available today in cn , tw, etc, is also like this. you are forced to use 'standard cells' supplied by vendor.

asciilifeform: to use as bus

asciilifeform: buncha gates, as many as can fit, and a programmable switching matrix, a la old telco , look up tables made of 4-6 bits of sram that turn a given unit into 'and' , 'or', 'xor', half-adder, straight wire, whichever is necessary. i dun know how to more rigorously define, it is one of the simplest devices, straight homogeneous grid of sram cells plus a couple hundred (thousand, in larger devices) 'express lanes' made of straight metal,

asciilifeform: ( i omit to mention ~large~ fabs, given as if you aint representing a large and known $$$ concern, they dun even return calls )

asciilifeform: ( how ran into this : sneak preview of mmap demo : http://p.bvulpes.com/pastes/VDYWv/?raw=true << path is set cleanly, as part of the generic invocation. but turns out this dun work (unless secondarystackism is enabled) , as somewhere internally it tries to ~return~ the string ☟︎

asciilifeform: previously , from last 2+yrs of reading docs, i laboured under the impression that the only process that demands secondary stack, is ~returning~ variably-lengthed objects. rather than simply passing'em forward as 'in' param. which in erry context OTHER than generic, worx . ☟︎

asciilifeform: meanwhile, in today's gnat retardations : apparently it is impossible to use ( but can define!!!11 just fine ! ) a generic that takes a String as 'in', without secondary stack.

asciilifeform: ( the problem of ciphering a block device in such a way as to avoid the penguin ( http://btcbase.org/log/2016-12-24#1590007 ) is tricky but not insurmountable ) ☝︎

asciilifeform: http://btcbase.org/log/2018-10-24#1865708 << if pc iron had its shit together, there would not even need to be such a thing as 'red' disk -- only (temporarily) 'red' sram, and buncha freely backed up 'black' disk. ☝︎

asciilifeform: speaking moar generally of replays -- because of the idjit method shitoshi used for block-gettin', where 1 peer can ~monopolize connection for just about as long as he wants -- a stock trb node , syncing from empty, is in fact in a position to be fed just about arbitrarily long replay chain. which is why my interest in sane checkpoint variant.

asciilifeform: mod6: i think there's also an ordinary (as they go) prb noad mixed into that pcap