← | Results 17501 ... 17750 found in all logged channels for 'f:diana' | →
(trilema) diana_coman: I used that at the udp tester to create file only if it does not exist
(trilema) diana_coman: hm, opening file for append however raises an exception if file does not exist
(trilema) diana_coman: ave1, thanks, confirmed fine, I'll sign and mirror it on my shelf in a minute; (re s.mg lines - not a worry either way really)
(trilema) diana_coman: ave1, please update so I can sign the patch
(trilema) diana_coman: this code is meant for touching, heh
(trilema) diana_coman: ave1, the .ads in your .vpatch still has the original comments saying that it's a lookup-based implementation, lol
(trilema) diana_coman: btw I think this is a very good description indeed: http://btcbase.org/log/2018-10-15#1862713
(trilema) diana_coman: there isn't any question that I see remaining there; I think what happened was that I was thinking a bit out loud in the logs yesterday and I got to same conclusion basically but then you started answering to the first part and some things were not unclear at a distance too and so the whole thing
(trilema) diana_coman: makes perfect sense, yes
(trilema) diana_coman: in the more general case it can branch for all sorts of reasons and continue on those branches for as long as needed, of course
(trilema) diana_coman: I read and re-read and I get the impression that this sort of delayed conversation doesn't work very well so I'll leave it for now
(trilema) diana_coman: http://btcbase.org/log/2018-10-15#1862722 -> hm, multi for the sake of it would anyway be taken care of via who signs and who doesn't sign the various patches or trees; but anyway - do you mean you think there should be explicit multi-tree dependencies? this is what I was talking about there: tree A effectively links to patch B.3 in tree B so if B's maintainer regrinds then A's maintainer has to go on a shouting spree (as per "talk to peop
(trilema) diana_coman: http://btcbase.org/log/2018-10-15#1862726 -> right, dependent is the right word there
(trilema) diana_coman: that actually makes sense
(trilema) diana_coman: I think the difference might be at whether it is "practical" or not :)
(trilema) diana_coman: I can see the history is preserved angle, certainly; and a nice thing for sure; but there is a cost for it and I'm not sure the benefits make up for it
(trilema) diana_coman: once you bring it into your tree, you don't care about the original tree so ...how stuck?
(trilema) diana_coman: and then you are stuck maintaining those multiple trees - what's the benefit in that?
(trilema) diana_coman: maybe I didn't understand then what you mean by "patch that pulls in specific state from a parallel tree"
(trilema) diana_coman: basically you introduce tree dependencies?
(trilema) diana_coman: asciilifeform, trouble is - what do you do then when/if that tree gets reground?
(trilema) diana_coman: ave1, thanks, it verifies fine now!
(trilema) diana_coman: to my mind that's pretty much the reason, yes
(trilema) diana_coman: or keccak or whatever, basically making 5 tiny trees out of eucrypt tree
(trilema) diana_coman: I honestly don't quite see the point of taking crc32 out for instance
(trilema) diana_coman: yes, the way I currently see it now is pretty much that: trunk (main line) goes along the production versions of all stuff (crc32 or keccak or whatever else) and otherwise at the respective points there can be additional branches /leaves with the reference implementations
(trilema) diana_coman: ah, you mean that the only way to do this is to take crc32 out of eucrypt tree?
(trilema) diana_coman: but other than this, I don't see any need or point for reground
(trilema) diana_coman: hm, perhaps being a reference implementation it makes sense to remain as branch there and otherwise the tree continues along the main line (not reference)
(trilema) diana_coman: i.e. can one effectively branch the v tree to provide an alternative .vpatch i.e. this or that stand at this place in the pressed line?
(trilema) diana_coman: asciilifeform, perhaps I'm missing something obvious re ^ ?
(trilema) diana_coman: though I don't yet see how would one bring them together afterwards without requiring BOTH of them
(trilema) diana_coman: as it is, it will be a .vpatch after the lookup implementation - so linear sequence rather than alternative; you might want to branch the tree instead from *before* the lookup implementation so that your div version is effectively alternative branch
(trilema) diana_coman: ave1, typos: "opation" "to determin" "here a short list" "therefor" "registor" "zero's" "implentation" "not if statements"
(trilema) diana_coman: fwiw gpg also complains that it's bad signature
(trilema) diana_coman: ave1, now the sig doesn't verify??
(trilema) diana_coman: ave1, it seems I still get the old .vpatch? I took it with curl from http://ave1.org/code/eucrypt/eucrypt_crc32_div.vpatch ; is this the right place?
(trilema) diana_coman: ave1, thanks for the update, I'll look at it in a minute
(trilema) diana_coman: bvt, get yourself a pizarro shared account and start your blog there precisely with those pastes, what's keeping you?
(trilema) diana_coman: http://btcbase.org/log/2018-10-14#1862203 -> the point as I see it is precisely that physically there actually is only ONE type anyway so any different types/sizes is in fact a higher level filtering no matter what (i.e. having 2 different processes each with its own size doesn't mean that each will actually get only the size it wants)
(trilema) diana_coman: in fact the 3rd option that is the one actually to use is having different sizes on the two processes (i.e. different constant simply)
(trilema) diana_coman: http://btcbase.org/log/2018-10-14#1862213 -> it's more than just one if statement (although unnecessary branches in themselves are not great anyway); basically it's the udp code itself that has to be messed up to accommodate this particular thing - either using generic or otherwise using the largest of the two and then filtering one level higher
(trilema) diana_coman: packets even, right
(trilema) diana_coman: the tester does not pack them in rsa or serpent proper so it's the "package" there rather than protocol message, I guess that might be confusing, I'll update
(trilema) diana_coman: strictly from an implementation perspective I'd certainly prefer to have only ONE size of message to deal with - even if it means potentially that one has to check wtf it is; still, I'll wait for mircea_popescu to weigh in on this
(trilema) diana_coman: the port/separate is not an issue at all; at any rate rsa will be processed separately by design (and with lower priority) - but all this part is of no direct concern here
(trilema) diana_coman: asciilifeform, hmm, there is certainly a case for same size precisely because way simpler code
(trilema) diana_coman: http://btcbase.org/log/2018-10-13#1862137 -> this triggered image of labyrinth, lol; "that's just what the Minotaur said - when sated"
(trilema) diana_coman: trinque, please drop the diana_away
(trilema) diana_coman: mircea_popescu, I know, hence ox; ("at most calves" if BingoBoingo considers that they really are just boys)
(trilema) diana_coman: kind of doubt even that; cows on one side really makes for oxes or at most calves on the other, nothing more
(trilema) diana_coman: BingoBoingo, there are no men to start with, in the situation you describe
(trilema) diana_coman: anyways, will add to pile of weird for now and maybe later I get to look at it more
(trilema) diana_coman: seems to be some address in the US and "corporate" fwiw
(trilema) diana_coman: possibly; that would be my guess, some sort of magic packet
(trilema) diana_coman: apparently I'll have to get all those unexpected messages in some readable format and post them, myeah
(trilema) diana_coman: possibly, no idea really; but what, they just send random udp stuff on all ports?
(trilema) diana_coman: asciilifeform, no, weird, single UDP message received from it by the UY node during tests
(trilema) diana_coman: does anyone recognise 173.198.225.102?
(trilema) diana_coman: ave1, that sounds good
(trilema) diana_coman: so I guess I'll wait then on ave1's updated .vpatch then
(trilema) diana_coman: well yes, I can't quite see the point of blanking the manifest without regenesis since that's basically what it means
(trilema) diana_coman: and it fits perfectly the original idea of alternative, proper
(trilema) diana_coman: makes sense, yes
(trilema) diana_coman: ah, alternative line in manifest too, I see it
(trilema) diana_coman: http://btcbase.org/log/2018-10-12#1860960 -> hm, doesn't the manifest impose a single line rather than a tree?
(trilema) diana_coman: ave1, thank you, I'll look through it in more detail a bit later today
(trilema) diana_coman: asciilifeform, hm, the bit version blows up buffers even more because it uses *internally* arrays of bits as per http://www.dianacoman.com/2018/02/01/eucrypt-chapter-8-bit-level-keccak-sponge/#selection-51.100-51.594
(trilema) diana_coman: you might want perhaps to add a call + check to it in the tests too?
(trilema) diana_coman: typo in manifest "emplementation" -> implementation ; but one can live with that
(trilema) diana_coman: nice, thanks!
(trilema) diana_coman: keeping it separate certainly makes sense (so that it's not a mandatory piece in there) but if it's code it's still basically under V that it belongs
(trilema) diana_coman: there is also the bit-keccak in eucrypt and that is the same really - reference code rather than production code
(trilema) diana_coman: well yes, but where should reference code be?
(trilema) diana_coman: if you make it a .vpatch, I'll sign it
(trilema) diana_coman: ave1, at any rate, <pre> tags added, looks good
(trilema) diana_coman: ave1, why not add it as a .vpatch on the eucrypt tree?
(trilema) diana_coman: ahaha, so I should have introduced you to some lebanese/kuweitis here, at least they speak arabic!
(trilema) diana_coman: how's talking to locals going?
(trilema) diana_coman: it does look as if it's from some old picture book, lol
(trilema) diana_coman: was it the time of day/light that made that "my view" picture so sandy-looking?
(trilema) diana_coman: nice pics Mocky !
(trilema) diana_coman: asciilifeform, thanks!
(trilema) diana_coman: so hot water yes in qatar but coffee not before 7-8am, weird
(trilema) diana_coman: asciilifeform, in some places they do but it wasn't the norm or everywhere/by default
(trilema) diana_coman: in costa rica I know they don't
(trilema) diana_coman: hm, speaking of costa rica style...do they actually have hot water at the taps in costa rica (i.e. not shower only)?
(trilema) diana_coman: ahaha, costa rica style
(trilema) diana_coman: Mocky, ah, phew; still: sorry about it
(trilema) diana_coman: (so perhaps there ...is somewhere, well hidden?)
(trilema) diana_coman: granted, I did not search for this but still
(trilema) diana_coman: asciilifeform, it's not as much those particular slides themselves - it's simply that I haven't seen anything *other that that* in *any* "academia" material/discussion anywhere
(trilema) diana_coman: Mocky, btw sorry for the mess up with your public key; did it actually create a problem other than the wrong wot.deedbot graph?
(trilema) diana_coman: asciilifeform, for ~1k bux you can probably fly to Ro and back and have the dentist treatment included too?
(trilema) diana_coman: http://btcbase.org/log/2018-10-09#1859786 -> I tend to agree; given how easily I could tell the poor lecturer what was in his inherited slides *before I even saw them*, I guess they literally have (echo of an echo)^n and it was anyway just some hearsay to start with
(trilema) diana_coman: !!reputation diana_away
(trilema) diana_coman: the !!reputation thing is correct there though; so it might be only the visualizer
(trilema) diana_coman: !!reputation Mocky
(trilema) diana_coman: but hm, does this mean that basically anyone can register the public keys and mess up the http://wot.deedbot.org/ ?
(trilema) diana_coman: sorry about the mess there trinque
(trilema) diana_coman: mircea_popescu, yes
(trilema) diana_coman: mircea_popescu, o.O apparently I ...did; and I found out how, as well: the crappy lappy on which I had the away account had imported a few public keys, first of which Mocky's
(trilema) diana_coman: at least they have internet!
(trilema) diana_coman: oh hey, how's Qatar, Mocky ?
(trilema) diana_coman: lol! who's jimmy hoffa?
(trilema) diana_coman: I'll have to sit down and sketch for myself some clear options so that I know what I want from this; then I can serve it to them "take it or leave it" and that is that
(trilema) diana_coman: before talking of "blockchain technologies" I'd much rather talk of the whole non-technology part that is anyway more important
(trilema) diana_coman: aha, hence my "chance to hear" rather than anything else
(trilema) diana_coman: I see so many things to say, lol!
(trilema) diana_coman: it's more a matter of wtf to do to get through to them in the least seeing how they are so ...far away on all dimensions to any reality
(trilema) diana_coman: the inherited slides are the usual mixture of "blockchain new techhxxx" + "ethereum!!!"
(trilema) diana_coman: from my pov the whole gain if I'm doing this is precisely in giving at least students the *chance* to hear something other than the regurgitated bullshit
(trilema) diana_coman: ftr the above comes after I pretty much demolished (at a kids' party of all places) the "content" the poor new lecturer had inherited
(trilema) diana_coman: in other possible interesting things: I got invited to give a talk to students at local uni (Reading, UK) on "bitcoin and blockchain"; personally I'm not all that keen on it but given the recent ideas regarding reach out and all that, I am at least considering this; any input on this is welcome
(trilema) diana_coman: neah, he wanted to visit the town
(trilema) diana_coman: yes, I would honestly simply stay a few days in that town then at least, but what can I say
(trilema) diana_coman: from costa rica, lol
(trilema) diana_coman: on my way back to costa rica I had this connecting flight in Madrid, a few hours gap, had something to eat, no problem
(trilema) diana_coman: but yes, apparently 30 hours gap great thing
(trilema) diana_coman: and in which direction, lol
(trilema) diana_coman: honestly, this is how it sounded! kind of reason why I asked him what airline was that because it's the first time I hear such a thing
(trilema) diana_coman: anyways, he'll surely be able to give details when he gets online
(trilema) diana_coman: back from wherever they got but surely not from london, lol! I understood it was the type of "took off, flew a bit, something wrong, going back because can't risk attempting to cross the atlantic"
(trilema) diana_coman: he's a very nice fellow!
(trilema) diana_coman: the great american airlines managed to repair the plane on their own - this time
(trilema) diana_coman: mircea_popescu, in London; though he did have a weird flight - went back to New York, repaired plane, went back
(trilema) diana_coman: !!v E1E5979C4064C1E73632B9D559C847A41914992CC4CC57DED30C0FE73DC3E1A8
(trilema) diana_coman: and it's the one running the proto-cuntoo; I think it's needed at least until we can migrate to cuntoo+gnat
(trilema) diana_coman: mircea_popescu, yes; atm it's anyway used for the udp
(trilema) diana_coman: is uy3 the test s.mg server?
(trilema) diana_coman: in that case the "starter" is using cuntoo, sure
(trilema) diana_coman: my understanding was that the starter would be just that, fixed minimal thing to get started, I don't see the need to change it and/or keep in sync
(trilema) diana_coman: the part I don't get is: what does "pressed manually with gnupatch" earn you vs "manually verify sig on this archive here"? (I assume the archive won't be 100MB of shit, ofc)
(trilema) diana_coman: well, if it's "give" then it will have to be signed tar as far as I can tell, I still don't see why one would basically import gnu patch just in order to "give n00b" anything; the options are always either "take what exists i.e. on trust " (in which case archive) or "go and make your own" in which case what's the problem
(trilema) diana_coman: phf, I've uploaded the updated keccak .vpatches for EuCrypt, let me know if there's any trouble: http://ossasepia.com/reference-code-shelf/#selection-39.0-41.16
(trilema) diana_coman: perhaps; I'm not sure though that current theorist/linguist/semiologist/gnoseologist/etc necessarily knows what they are supposed to know
(trilema) diana_coman: oh, was it supposed to be coherent and not self-contradictory? I missed that part,lol
(trilema) diana_coman: more like they don't have a notion of "working indefinitely" or even of more than tomorrow
(trilema) diana_coman: I'll soon do the regrind of eucrypt to move it on to keccak hashes; my plan is to keep the patches precisely as they are otherwise (i.e. including NO manifest until I actually added it at the end); the way I see it, it's just a swap-in-place of one hash for another; if anyone sees this sort of thing differently - since I'm hmmm,first to regrind a big project? - yell now !
(trilema) diana_coman: I must say that I am ...blissfully unaware of it
(trilema) diana_coman: http://btcbase.org/log/2018-10-05#1858557 -> heh; kind of why I tend to do the replies all at the end rather than as I read them though it's less convenient
(trilema) diana_coman: http://btcbase.org/log/2018-10-05#1858549 -> precisely why I kept scratching my head at encountering it as a sort of "preferred"/standard stuff in GNAT; honestly I think it was a ...fashion, everything all of a sudden had to be a stream at some point
(trilema) diana_coman: so yes, lifting it
(trilema) diana_coman: I'm actually thinking whether to add a simple crc32(array of octets) -> unsigned_32 to EuCrypt; presumably it will be of larger utility anyway;
(trilema) diana_coman: asciilifeform, yes, that's where I went after ave1 pointed out that the gnat.crc32 is just a stream-wrapper
(trilema) diana_coman: thank you ave1
(trilema) diana_coman: right you are, yay!
(trilema) diana_coman: ave1, ah, the gnat.crc32 is just the stream on top of system.crc32?
(trilema) diana_coman: as one might tell, I'm looking into using CRC in smg.comms as per latest spec
(trilema) diana_coman: aaand if I get it right, GNAT.CRC32 uses Ada.Streams.Stream_Element and it expects a String as input so overall it really sounds like back to GNAT.Sockets style, ugh
(trilema) diana_coman: asciilifeform, cheers!
(trilema) diana_coman: I'm going through the data right now, I plan to publish it + write-up by tomorrow
(trilema) diana_coman: ave1, good to know, thanks! and yes, it seems that there are few errors under those conditions really: over 1 full week I got less than 0.2% lost
(trilema) diana_coman: well...qatar
(trilema) diana_coman: I suppose if not Russia proper, at any rate, Moldova, Ukr, Belarus
(trilema) diana_coman: having one in the uk is...easy I'd say, but I'm not all that sure it's worth much, lol
(trilema) diana_coman: o.O what, you mean you can't just rent a machine there?
(trilema) diana_coman: as for ideas, dunno what/how you ruled out i.e...new zealand?
(trilema) diana_coman: for all I know he might have it there too? I did not coordinate/ask
(trilema) diana_coman: http://btcbase.org/log/2018-10-02#1857518 -> my public node is in Singapore if that's any help
(trilema) diana_coman: such are the perils of literal reading of logs, since yes http://btcbase.org/log/2018-09-29#1855541
(trilema) diana_coman: http://bimbo.club/?p=39 -> ahaha, "Mod6 finished trb"
(trilema) diana_coman: anyways, I'll let you know if tcpdump sniffs any/ can tell which one it is, but this paste there is the bird in hand atm
(trilema) diana_coman: asciilifeform, well, it IS all of it in there although you'd need to reconstitute it basically: look there, *all* the payload was different, so all of it IS reported; first bytes are reported anyway (sizesent and timesent)
(trilema) diana_coman: asciilifeform, see the paste; that one is part of the live capture basically - the error log simply logs all bytes that have a different value than expected
(trilema) diana_coman: but then who/wtf sends udp on port 7000 ? and meanwhile I left tcpdump sniffing and ...nothing so far
(trilema) diana_coman: that time sent is too small really
(trilema) diana_coman: onth it's hard to *really* tell if it is indeed chopped off part or just other garbage, hmm
(trilema) diana_coman: suspected old frag perhaps? no idea
(trilema) diana_coman: it certainly does look like some chopped off part of one of the messages sent around
(trilema) diana_coman: asciilifeform, if it help, here's an example of those packets from the switch - it's from the error log - I can pass you the whole file if it's of any use : http://p.bvulpes.com/pastes/ToYHc/?raw=true
(trilema) diana_coman: will see to it later
(trilema) diana_coman: I can certainly try and leave a tcpdump going to see what /if it gets anything
(trilema) diana_coman: no, but at least gives some idea more than I had on this, lol
(trilema) diana_coman: ahhh, that can be, dhcp, ugh
(trilema) diana_coman: uhm, but somehow packages were received with the switch as source ?? and actually it IS extra packages as it were, since adding them does result in more than were sent...
(trilema) diana_coman: but yes, I think it's just someone around here playing with the tester?
(trilema) diana_coman: asciilifeform, I can tell at least some of them, yes, because they got reported as "errors" because not what expected
(trilema) diana_coman: anyways, at a quick look, no errors on either direction between the 2 concerned nodes, ~99.80% made it to the other side ; will get to do a proper write-up with more details by the end of this week
(trilema) diana_coman: looking at the udp tester data, it seems my uy end got also some packets from 161.0.121.254, lol
(trilema) diana_coman: come to think about it, I can see the case for calling them "messages" since it's not the network level there, indeed
(trilema) diana_coman: www is up, date is set, everything so far looks fine; I'll give it a more thorough checkup in ~2 hours and get back to you
(trilema) diana_coman: asciilifeform, confirmed, thank you!
(trilema) diana_coman: ahhh, nm, I got confused with the later tell msg
(trilema) diana_coman: hm, that is...wrong line!
(trilema) diana_coman: http://btcbase.org/log/2018-10-03#1857574 -> uhm, mainly because I think of network package basically; technically speaking I suppose I should call them..datagrams, uhm
(trilema) diana_coman: the eucrypt keccak implementation uses an out parameter for output and so it will fill whatever the caller provides
(trilema) diana_coman: re collision yes, it's clearly not collision-resistant
(trilema) diana_coman: asciilifeform, int8 is indeed meant to be on 8 bits so no idea what that thing there is ; fwiw I added it to my comment on the article with ref to your q here in the logs too because I'm puzzled by it too
(trilema) diana_coman: http://btcbase.org/log/2018-10-02#1857391 -> lol, they are also just... not prime
(trilema) diana_coman: specifically, bit-level version gives bit-level precision so one can ask for as many bits as they want; workhorse byte-level keccak implementation works at byte-level so it will spit out as many *bytes* as you ask for (see http://www.dianacoman.com/2018/02/08/eucrypt-chapter-9-byte-order-and-bit-disorder-in-keccak/#selection-193.1-197.51 )
(trilema) diana_coman: asciilifeform, keccak can spit out as many or as few bits as you want it to, not sure what is you q there re keccak
(trilema) diana_coman: mircea_popescu, 1872 useful bits in 3920-bit rsa, confirmed
(trilema) diana_coman: yes; anyway it's basically a knob to turn, not a big issue in itself
(trilema) diana_coman: from a practical point of view it does mean that Eulora doesn't use directly TMSR RSA keys though
(trilema) diana_coman: eulora-sized rsa, hm
(trilema) diana_coman: so basically what, for as long as attacker can keep flooding , presumably no new accounts although there might still be some that make it through?
(trilema) diana_coman: precisely; I think that in principle there is a possibility of that "attack" but I fail to see that it's worth much really
(trilema) diana_coman: mircea_popescu, uhm, they made it through - presumably fragged though?
(trilema) diana_coman: but honestly I don't see that to be such a huge problem
(trilema) diana_coman: so will get presumably fragged
(trilema) diana_coman: he is talking of the new rsa packets that are biggest
(trilema) diana_coman: Mocky, if I get this right you argue that it's better to do frag internally because can't trust externally to not fuck up the line entirely as attack vector?
(trilema) diana_coman: asciilifeform, but what's the problem with that? client sends and waits (for as long as it wants) for a reply; whenever it has enough of waiting...sends again; until it makes it
(trilema) diana_coman: so then hooray
(trilema) diana_coman: asciilifeform, the above wasn't clear until now, it's clarified ...now
(trilema) diana_coman: asciilifeform, serpent payloads really; rsa is meant for single use when registering with server pretty much
(trilema) diana_coman: anyways, will wait to see the updates
(trilema) diana_coman: asciilifeform, it certainly makes the code simpler! if only I could always choose by this criteria though...
(trilema) diana_coman: mircea_popescu, cool; well, it's been 4 months being digested hopefully by everyone around so evolution makes sense!
(trilema) diana_coman: but it's variable lengths..
(trilema) diana_coman: there IS some padding, i.e. it's not entirely arbitrary lengths, no
(trilema) diana_coman: every time they simply ask for an object you force them to send over 2048 bytes, ugh
(trilema) diana_coman: but if you force it to pad everything to maxlen it's a bit iffy
(trilema) diana_coman: it's not the isp, lol; it's eulora-internal because client can choose how much traffic it generates
(trilema) diana_coman: asciilifeform, clients pay for traffic though so dunno
(trilema) diana_coman: http://btcbase.org/log/2018-09-27#1855101 -> it turns out Eulora actually needs precisely this since its communication protocol specifies different lengths of messages, hm
(trilema) diana_coman: I suspect there might be more to find out from dissection of the thing
(trilema) diana_coman: the thing is though that at any rate, it won't get the same type of use as it did as main disk so I don't know whether much can be found out from that really
← | →
Download hourly DB snapshot | Get Source Code