Results 1 ... 76 found in all logged channels for 'ironclad'
(pest) phf[asciilifeform]: cool. i'll take a look at it also, because i've been considering doing an ffi to openssl. perhaps not a permanent solution, but a stop gap before i extract and optimize relevant code from ironclad
(pest) phf[asciilifeform]: http://logs.bitdash.io/pest/2022-07-26#1010433 << main problem with ironclad is that it's garbage happy. there's for example no way to make red packet check cheap, an accidental or intentional flood of red packets will generate a lot of garbage. sbcl is clever about cleaning up short lived garbage, but there are no guarant
(pest) bitbot[asciilifeform]: Logged on 2022-07-27 12:58:55 phf[awt]: further re ironclad, i'll probably end up extracting relevant bits sooner rather than later, because i want to see if i can get pest going on a genera :D
(pest) bitbot[asciilifeform]: Logged on 2022-07-27 12:42:36 phf[awt]: http://logs.bitdash.io/pest/2022-07-26#1010433 << ironclad, historically ironclad not being all there is the result of my investigations, so i'm not too worried
(pest) phf[asciilifeform]: further re ironclad, i'll probably end up extracting relevant bits sooner rather than later, because i want to see if i can get pest going on a genera :D
(pest) phf[asciilifeform]: besides serpent one would also need to write sha512, sha256 and hmac. i figured eventually someone might do such a thing, and then we can all drop in replace. otherwise ironclad is good enough™
(pest) bitbot[asciilifeform]: Logged on 2022-07-26 07:00:13 crtdaydreams[jonsykkel|awt|signpost]: phf: what are you using for crypto might I ask? did you write your own impl. of serpent or are you using ironclad? or some other lib unbeknownst to me
(pest) phf[asciilifeform]: http://logs.bitdash.io/pest/2022-07-26#1010433 << ironclad, historically ironclad not being all there is the result of my investigations, so i'm not too worried
(pest) crtdaydreams[asciilifeform]: it's evident that historically ironclad "isn't all there" in some parts, but I can't comment in depth, haven't __read__ it yet
(pest) crtdaydreams[asciilifeform]: phf: what are you using for crypto might I ask? did you write your own impl. of serpent or are you using ironclad? or some other lib unbeknownst to me
(asciilifeform) phf: another one of those "nice to have" projects is to do a key verify with ironclad, but man it's such a dull project
(asciilifeform) adlai: it may be a fool's low-hanging fruit, although I found a bug in the Ironclad library when poaching their SHA2 implementation.
(asciilifeform) adlai: they are pretty much adlaifications of the ironclad originals.
(trilema) mircea_popescu: some things were lost once the great man-o-wars made way for the not nearly as great clunkers called ironclads. and once people figured out wtf a sears-haack body is, planes suddenly became "flying coke bottles'
(trilema) mp_en_viaje: large part of why move to ironclads. "dood... cedar's gone"
(trilema) mircea_popescu: oodles upon oodles of discussions of "antisemitism", a term very substantially like phologiston : its mere inclusion in a text constitutes an ironclad guarantee that nothing intelligent, useful or interesting will be found there.
(trilema) mircea_popescu: asciilifeform it's my considered oppinion that had napoleon switched the fleet to ironclads and had the french state not been permitted to operate any railroads, they'd have rebounded.
(trilema) mircea_popescu: had the french had the sense to ironclad in 1799 and to private railroad in 1820, likely us rail system would have started from st louis and new orleans rather than new york and philadelphia, and as a result the 1860 dispute would have been a case of "tiny english east being shaken off humongous french colonial empire".
(trilema) ben_vulpes: lest i ironclad myself
(trilema) mircea_popescu: still, ironclad argument that current grep is broken : looks for PART OF the header it should.
(trilema) ben_vulpes: also ironclad rsa padding is notquiteright, trinque i believe knows a bit more
(trilema) phf: maybe, but only as "presented as found". froydnj said in a few places, that he doesn't think ironclad is there yet as far as being used for production crypto. and we had a thread (with ben_vulpes) where we discovered that sha512 (!!!) had a bug
(trilema) asciilifeform: if 'ironclad' is a worthy thing , it oughta be genesised
(trilema) phf: asciilifeform: no! you keep saying that, ironclad is 0 ffi
(trilema) ben_vulpes: ironclad needs a 'libressl'ing imho
(trilema) asciilifeform: phf: iirc the sha256 in 'ironclad' is simply a c wrapper around turdssl
(trilema) whaack: asciilifeform: okay I plan to use ironclad to do the actual hashing in the cl implementation unless there is a better recommendation
(trilema) asciilifeform: but i will need an ironclad proof that it worx for ALL possible inputs.
(trilema) mircea_popescu: (and to round off the above : consider that the first metallic aluminum was shaped into a box and offered to the same person as the ironclad drawings were offered. whyssat ? cuz that's how all science flew back when people could control it.)
(trilema) mircea_popescu: there's no particular requirement that the person building an ironclad factory does not own the sailship drydock in town. on the fucking contrary ; the sign of the drydock owner ~being an idiot~ is their not building an ironclad factory right down the shoreline.
(trilema) mircea_popescu: i suppose the period was ironclad to sarcasm...
(trilema) ben_vulpes: ironclad dood wrote the thing in college and then got a job?
(trilema) phf: in related http://www.method-combination.net/blog/archives/2017/03/07/nibbles-and-ironclad-releases.html " I will no longer be maintaining nibbles, ironclad, nor any of my other Common Lisp packages"
(trilema) ben_vulpes: i am trying to figure out how to handle widely-distributed versions of ironclad not working in the way i need them to work for my v to verify hashes on press
(trilema) ben_vulpes: guy lays out in his "how ironclad came to be" that he doesn't really spend much time on it anymore.
(trilema) a111: Logged on 2016-12-26 02:38 phf: ben_vulpes: according to master this is the reason http://glyf.org/tmp/ironclad-sha512.patch unsigned for obvious reasons
(trilema) ben_vulpes: i'm also not really in a mood to make ironclad_genesis.vpatch today
(trilema) ben_vulpes: i don't want to say something like "ensure you have HEAD of the Ironclad library", i think it's more likely and more in line with waht mod6 is doing to shell out to sha512sum
(trilema) ben_vulpes: so here's what i'm thinking re: ironclad
(trilema) a111: Logged on 2016-12-27 16:39 phf: http://btcbase.org/log/2016-12-27#1590876 << i suspect that ironclad is still one of the better platforms to audit and integrate into own ecosystem. short of waiting for p what other options do you have? ffi to openssl? the code is readable, in the past year munchkins have been adding various algos to it, so you know what to cut, but also gives you a nice blueprint of how to extend etc.
(trilema) a111: Logged on 2016-12-27 16:39 phf: http://btcbase.org/log/2016-12-27#1590876 << i suspect that ironclad is still one of the better platforms to audit and integrate into own ecosystem. short of waiting for p what other options do you have? ffi to openssl? the code is readable, in the past year munchkins have been adding various algos to it, so you know what to cut, but also gives you a nice blueprint of how to extend etc.
(trilema) phf: http://btcbase.org/log/2016-12-27#1590876 << i suspect that ironclad is still one of the better platforms to audit and integrate into own ecosystem. short of waiting for p what other options do you have? ffi to openssl? the code is readable, in the past year munchkins have been adding various algos to it, so you know what to cut, but also gives you a nice blueprint of how to extend etc.
(trilema) a111: Logged on 2016-12-27 03:51 ben_vulpes: http://btcbase.org/log/2016-12-26#1590731 << i think maybe back away slowly from ironclad lest it blow up in my face then
(trilema) a111: Logged on 2016-12-26 03:54 phf: asciilifeform: http://www.method-combination.net/blog/archives/2014/12/29/ironclads-history.html in case you were wondering "how the fuck"
(trilema) ben_vulpes: http://btcbase.org/log/2016-12-26#1590731 << i think maybe back away slowly from ironclad lest it blow up in my face then
(trilema) phf: (i remember there being a standalone sha256 (?) version for sbcl, but i can't find it now. everything crypto that's coming up re lisp is ironclad.)
(trilema) asciilifeform: ben_vulpes above found catastrophic ?!?? in ironclad's sha512 tho.
(trilema) phf: ben_vulpes: according to master this is the reason http://glyf.org/tmp/ironclad-sha512.patch unsigned for obvious reasons
(trilema) phf: asciilifeform: for the record there's not a single line of ffi in ironclad. we've had this conversation before
(trilema) ben_vulpes: ('it' == ironclad ?)
(trilema) a111: Logged on 2016-12-25 22:27 ben_vulpes: http://btcbase.org/log/2016-12-24#1590190 << ironclad claims to have a "pure lisp" implementation of rsa but i have not confirmed this for myself
(trilema) ben_vulpes: http://btcbase.org/log/2016-12-24#1590190 << ironclad claims to have a "pure lisp" implementation of rsa but i have not confirmed this for myself
(trilema) mircea_popescu: let's approach this from a more hospitable angle. dutch makes the charge (unsourced, but it's sheer anglicanism) that the reason the greeks didn't build ironclads is that they (like the chinese, natch) despised manual labour.
(trilema) asciilifeform: i suspect that the folks for whom 'the defense is ironclad' they simply nailgun.
(trilema) mircea_popescu: the defense is still ironclad. that they stick him in jail anyway is entirely their problem.
(trilema) mircea_popescu: if they did or if they didn't, the "i had nothing to do with it" defense is ironclad as far as that goes.
(trilema) phf: well, then you have a hitler diddled copy, ironclad's tagline always has been "entirely in common lisp"
(trilema) phf: no wai, ironclad is pure lisp
(trilema) asciilifeform: wtf is even ~in~ ironclad, i thought it called out to openssl in c ffi, or similar horror
(trilema) phf: hmm, it's all ironclad's sha256. doing it with a dummy #(0 ...) digest drops it to 4.6mb
(trilema) phf: http://paste.lisp.org/display/327488 lamport parachute PoC in common lisp (it has soft dependency on ironclad for sha256, but otherwise follows the design in that own function can be substituted)
(trilema) phf: i'm curious if there's enough machinery in ironclad to give me support to do a pgp verify rewrite
(trilema) phf: hah, recent pull requests to ironclad is from this guy https://github.com/glv2 (i.e. https://github.com/froydnj/ironclad/pull/62), who has a bunch of peercoin related projects like https://github.com/glv2/peercoin-blockchain-parser
(trilema) phf: adlai: "veh" doesn't use diff or ironclad, calls out to external utilities instead. fwiw froyd explicitly disclaimers ironclad use in production anyway..
(trilema) adlai finds it asset-backwards to jump headfirst into v.cl before auditing https://github.com/froydnj/diff (and ironclad, but that's a little outside my pay grade)
(trilema) mircea_popescu: So, right there, VW diesel owners have a pretty ironclad case for what boils down to speculative financial compensation: the difference between what the cars 'would have been worth' if this flaw hadn't been exposed and what they *are* worth -- which is zero, if only because no one in their right mind would buy one (and in many cases reale may now be forbidden by law) << what ?
(trilema) mircea_popescu: it's ironclad, sure. but a tank has not very good fuel economy.
(trilema) Adlai will lift from ironclad when the time comes
(trilema) mircea_popescu: cazalla fwiw, the state has an ironclad case for rejecting the proposed testimony.
(trilema) mircea_popescu: you know, for an ironclad case the prosecution claims, and for an independence from the state the judge pretends,
(trilema) mircea_popescu: so it's a safe if not ironclad assumption
(trilema) asciilifeform: almost ironclad rule.
Download hourly DB snapshot | Get Source Code