2000+ entries in 0.212s
ben_vulpes: let's rewind: what does trinque miss when v finds a seal for a vpatch for which it doesn't find a key and proceeds merrily, provided it does find *a* seal for the
patch that corresponds to a key in .wot?
mod6: <+ben_vulpes> no, that's death() ing on a
patch for which the system had valid seals, yours and mine. << this i dont agree with -- from a technical perspective. it looks to me that girl had "ascii and mod6" in .wot, and when it came across Mr. P.'s genesis .sig, it honked.
ben_vulpes: no, that's death() ing on a
patch for which the system had valid seals, yours and mine.
ben_vulpes: and yes, this implies an o(n^2) worst case process in (or (map 'boolean (lambda (sig) (verify 'some_patch.vpatch' sig)))
mircea_popescu: ben_vulpes> so long as there is at least one signature for a
patch, for which signature v can import a corresponding key, on the basis of the wot, that
patch should press. << ftfy.
ben_vulpes: so long as there is at least one signature for which v can import a corresponding key, that
patch should press.
ben_vulpes: imho v should not barf when
patch and seal exist but key does not in wot
mircea_popescu: mod6 the idea is that you should be able to alter the end product by altering .wot rather than by altering .wot AND .
patch or .seal
mircea_popescu: well he can run his v any way he pleases ; but yes it should prolly just drop the bad
patch and move on
mircea_popescu: it should probably stop if it finds valid
patch that can't be applied (mismatched hashes) - because by then your state is broken.
mircea_popescu: mod6 if it simply skips over the patches it can't find acceptable sigs for, it delivers asciilifeform 's thing above where you don't have to keep fucking around with the
patch set.
mod6: <+mircea_popescu> im not sure it has to die when it encounters malformed
patch (be it not signed or whatever), but anyway. << i was thinking this was simple because of this:
mod6: <+asciilifeform>
http://btcbase.org/log/2016-12-22#1587685 << the simplest way to implement this is to iterate over the ~seals~, finding corresponding patches << <+mircea_popescu> not particularily correct ; should iterate over patches, check sealness ; act accordingly. << 'validate_seals' does this; iterates over patches, finds seals for
patch, verifies or fails if bad ;; now dies if there are none.
☝︎ mircea_popescu: for every
patch, check if
patch sig by approved names is present. this isn't any sort of N^2 ; it's O(N*M) where N is the count of patches and M the count of approved signers.
mircea_popescu: im not sure it has to die when it encounters malformed
patch (be it not signed or whatever), but anyway.
trinque: or we're afraid of
patch? if we want an actual
patch utility that only deals in single byte characters and hashes, I will write it.
mod6: how does WILD have anything to to do with
patch?
trinque: why have that code path present at all? fix
patch, apply test patches by hand
a111: Logged on 2016-12-21 20:50 trinque: the reason you do not use
patch by hand is that it does not respect the hash
trinque: you are expanding the definition of "v" the word to accomodate deficiencies in the definition of another word,
patch trinque: that is a problem with
patch trinque: the reason you do not use
patch by hand is that it does not respect the hash
☟︎ ben_vulpes: might be interesting to
patch trb to dump relevant connection's self-identification string
a111: Logged on 2015-06-24 18:31 mod6: ascii_field: re: checkpoints: the
patch worked fine to remove checkpoints, but it was tabled for the time being. the main discussion around this was that it could be helpful to hvae checkpoints in there to prevent spamming of blocks from timestamps before a checkpoint.
phf: it's the equivalent of diff's @@ -0,0 +1,437 @@. i just dump whatever's being stored in
patch's fields, without any special formatting
mircea_popescu wanders off to add danielpbarron eu
patch and see what happens.
phf: so vpatches all have preludes, by virtue of how diff/
patch works (that's how you can just cat mail.mbox >
patch). i was thinking of using that prelude for readme, but you can put base64 binary files there, and verbally communicate additional required steps. it's ugly, but it's without mutilating core concept. prelude is reveserved for whatever ugly special case hacks, etc.
adlai: re:space, i realize the space is the separator in the
patch syntax; the awk script is not looking for it though
mod6: So I've created a
patch that so far puts in the ability to view 'listunspent' UXTOs in the wallet.
mod6: And I've created a reground
patch for that.
phf: i have a
patch that i'm working on that might help towards that goal
a111: Logged on 2016-12-07 21:46 ben_vulpes:
http://btcbase.org/log/2016-12-07#1579050 << "image" as in "lisp image"? the reason i ask is because reindenting blocks of code for a multiple-value-bind makes unnecessary
patch noise.
phf: ben_vulpes: yeah, lisp image. fwiw if you're trying to ignore whitespace (since you're going to lose that information in a sexp, unless you preserve that information, in which case you will have to
patch it same way), then diff already does it: it's called ignore whitespace (-b or -w or -B depending on usecase)
a111: Logged on 2016-12-07 05:28 ben_vulpes: asciilifeform: is there an argument for vetoing out-of-hand a v/
patch implementation that diffs at the sexpr level rather than the line level?
a111: Logged on 2016-12-07 05:28 ben_vulpes: asciilifeform: is there an argument for vetoing out-of-hand a v/
patch implementation that diffs at the sexpr level rather than the line level?
jurov: "vetoing out-of-hand a v/
patch implementation that diffs at the sexpr level rather than the line level"
ben_vulpes: asciilifeform: is there an argument for vetoing out-of-hand a v/
patch implementation that diffs at the sexpr level rather than the line level?
☟︎☟︎ diana_coman: fwiw I kept trying to digest asciilifeform's proposed categories, but I must confess I would still have trouble deciding on one or another; basically my clear categories would really be binary: I'm USING this or I WILL NOT USE this; the rest I would rather expect to be sorted by competence meaning that one who wants to write a
patch for eulora would better get a "I'm using this" from someone involved with eulora, not from his t
pete_dushenski:
http://archive.is/vT63P << other other from same : "Microsoft is working on a
patch for a bug or feature in Windows 10 that allowed access to the command line and, using a live Linux .ISO, made it possible steal BitLocker keys during OS updates. The command line interface bypasses BitLocker and permits access to local drives simply by tapping the Shift and F10 keys."
mircea_popescu: btw since
http://www.loper-os.org/?p=1545 was mentioned again, it must be said : "Not only are there times when one would like to seal a payload with a caveat of one kind or another, but presently we have no means of conveying disapproval – other than by refraining from sealing. The latter act conveys very little useful information, and no permanent sealed record remains of the effort taken to actually understand the
patch.
phf: i think bsd
patch might predate v
trinque: phf: where's that
patch at btw?
a111: Logged on 2016-12-01 01:52 mod6: shinohai: well, at one point the one
patch we had made that possible, but with buildroot now in the mix, im not sure. would have to be dug into.
shinohai: No worries mod6 ..... the new
patch did fine, nice work getting that out so quickly
mod6: shinohai: well, at one point the one
patch we had made that possible, but with buildroot now in the mix, im not sure. would have to be dug into.
☟︎ gabriel_laddel: jurov:
patch it and share with WOT. If it cannot be fixed, make a note of it and distribute.
trinque: pretty close to a genesis V
patch by now
ben_vulpes: failed to land a
patch, was summarily executed by handlers
mircea_popescu: supply is fine (works on diff identical item). all clues point to "was fed magic packet,
patch broken, unit failed to come back"
shinohai: working on a regrind of funkensteins privkey
patch mircea_popescu: Framedragger technically yes you can - make a V root for it, like properly sane people, then he'll just import that /
patch it himself when he's ready.
gabriel_laddel: ^
patch the lastest CL-FTP with that ftp.lisp and it'll work
Framedragger: mircea_popescu: yep raspbian, though that should have been after
patch, but - who knows
Framedragger: the whole "
patch a DNS server and run alternative root" effort sounds interesting and useful, but, as you said, eventually the underlying layer would need to swapped for gossipd anyway. in gossipd, UDP/TCP as currently used by DNS may not even work. hence there may be a redundancy of effort;
a111: Logged on 2016-10-31 18:14 trinque: I'm irritated he didn't genesis v-
patch the thing
trinque: I'm irritated he didn't genesis v-
patch the thing
☟︎ phf: !~later tell gabriel_laddel have you considered putting ~everything~ masamune into a single tree, prepatched, so that instead of "load X, then load my
patch-foo-for-X" you just have everything under single hierarchy exactly the way you expect it to run in production?