#trilema | 2018-03-01

spyked: hey phf! I get the "stale page" error when trying to comment on http://barksinthewind.com/2018/vtools-keccak/ ; I also tried leaving a "fresh" comment, but I get the same error ( http://btcbase.org/log/2018-02-18#1784931 should fix it?)

a111: Logged on 2018-02-18 23:23 hanbot: <mircea_popescu> "Looks like you tried to comment off a stale page. Reload the article, count to three and try again." << for future reference, mp-wp comment fix is in the edit here: http://thewhet.net/2017/10/a-compendium-of-possibly-helpful-stuffs-for-erecting-mircea-popescus-wordpress-with-nearly-free-speech-hosting/ , and will be a patch once that project can move again.

spyked: anyway, comment was that I managed to compile and run vdiff with small mods; error: http://p.bvulpes.com/pastes/BiBTI/?raw=true and fix patch: http://p.bvulpes.com/pastes/9mOiz/?raw=true (tested this with the generated vdiff); I can try to link this reply later in a comment to test.

shinohai: ben_vulpes:

shinohai: !~ticker --martket all

jhvh1: shinohai: (ticker [--bid|--ask|--last|--high|--low|--avg|--vol] [--currency XXX] [--market <market>|all]) -- Return pretty-printed ticker. Default market is Bitfinex. If one of the result options is given, returns only that numeric result (useful for nesting in calculations). If '--currency XXX' option is given, returns ticker for that three-letter currency code. It is up to you to make sure the code is a valid currency (1 more message)

shinohai: !~ticker --market all

shinohai: duh

jhvh1: shinohai: Bitstamp BTCUSD last: 10770.0, vol: 8502.77353360 | Bitfinex BTCUSD last: 10784.68294217, vol: 31154.47218217 | Kraken BTCUSD last: 10786.0, vol: 7708.78240515 | Volume-weighted last average: 10782.261527

deedbot: http://qntra.net/2018/03/ssl-certificate-reseller-leaks-private-keys/ << Qntra - SSL Certificate Reseller Leaks Private Keys

deedbot: http://qntra.net/2018/03/very-cold-britain-running-out-of-natural-gas/ << Qntra - Very Cold Britain Running Out Of Natural Gas

ben_vulpes: shinohai: is this an "it works now" or "you did it wrong" sort of thing. fwiw i expect the former in the form of "it was broken because of X, i did Y to fix it, and Z to prevent it from happening again" not that you're my direct report or anything

BingoBoingo: ben_vulpes: It was the former, you did !!, bot listens to !~

ben_vulpes: BingoBoingo: ah thanks

ben_vulpes: if my meatware differ didn't catch it coming out of my fingers the first time it likely won't catch it when presented with the correct version

BingoBoingo: That is a hazard

ben_vulpes: mircea_popescu diana_coman: my mistake, the box is not raid5 compatible, it can do raid1 and raid10. is this okay and do you have a preference between the two?

shinohai: sorry if i offend ben_vulpes i meant the "Duh" towards myself, because i flagged help instead of of tcker

ben_vulpes: having worked to memorize the bot keycombos for some time now, i would particularly like it if they would respond to their names. this approach autocompletes for one and is far more easily visually diffed, for another.

shinohai: jhvh1: ticker

shinohai: hmm

ben_vulpes: gotta point out that this is out-of-spec behavior as is

ben_vulpes: !~ticker --market all

jhvh1: ben_vulpes: Bitstamp BTCUSD last: 10845.0, vol: 9025.34975079 | Bitfinex BTCUSD last: 10864.0, vol: 31700.14010236 | Kraken BTCUSD last: 10845.2, vol: 7760.80742628 | Volume-weighted last average: 10857.4541336

ben_vulpes: !~later tell mircea_popescu may i buy one of the power supplies out of the S.NSA inventory asciilifeform's posession? i'll pay you .0047 btc for it

jhvh1: ben_vulpes: The operation succeeded.

phf: http://btcbase.org/log/2018-03-01#1786598 << amusingly the fix is on my own blog http://barksinthewind.com/2016/wp-content-for-a/#update1 but i must've lost the changes when i was updating the theme

a111: Logged on 2018-03-01 13:45 spyked: hey phf! I get the "stale page" error when trying to comment on http://barksinthewind.com/2018/vtools-keccak/ ; I also tried leaving a "fresh" comment, but I get the same error ( http://btcbase.org/log/2018-02-18#1784931 should fix it?)

phf: http://btcbase.org/log/2018-03-01#1786600 << which os/compiler is that? i suspect that i'll have to put all the annotations into system.h defines and let specific systems pass whatever in a makefile.

a111: Logged on 2018-03-01 13:52 spyked: anyway, comment was that I managed to compile and run vdiff with small mods; error: http://p.bvulpes.com/pastes/BiBTI/?raw=true and fix patch: http://p.bvulpes.com/pastes/9mOiz/?raw=true (tested this with the generated vdiff); I can try to link this reply later in a comment to test.

ben_vulpes: !~later tell mircea_popescu disregard

jhvh1: ben_vulpes: The operation succeeded.

phf: comments are fixed

deedbot: http://www.thedrinkingrecord.com/2018/03/01/back-to-the-fat-accountancy-discussion/ << Bingo Blog - Back To The Fat Accountancy Discussion

ave1: diana_coman: this, http://btcbase.org/log/2018-02-28#1786496, triggered a short dive into the whole array sending mechanism in Ada. Will write it up and post tomorrow, yes it is possible but you'll need to make some internal structure that Ada uses. Also I doubt it is much better than sending the pointer with a separate length parameter.

a111: Logged on 2018-02-28 15:07 diana_coman: ave1 have you ever passed a char * from c to ada in such a way that ada actually sees the correct length for it? there is something I don't quite understand there as To_C seems to use Target'Length so the length should be set

ave1: mircea_popescu, http://btcbase.org/log/2018-02-28#1786498, which parts of gpg (I can image plain text signing, encryption and decryption).?

a111: Logged on 2018-02-28 15:57 mircea_popescu: ave1 you should ; also read through the eucrypt thing, ima (for instance) need someone to package it into a cmd line gpg replacement as soon as next wek.

ave1: Also does this have to follow the gpg format? or simply hex encoded numbers?

diana_coman: ave1, my current solution is to pass the length as a separate parameter indeed and in addition to actually copy octet by octet; To_C and To_Ada still fail me on occasion so I can't really rely on them - this might be of course because I don't fully understand them yet; in any case, please write it up, pretty please

diana_coman: no requirement re format, it's really: pass this here char * to Ada safely and recover this String from Ada via an "out String" parameter (char * on C side)

diana_coman: calling from C something that might look like this in ada: procedure getstring(input: in Interfaces.C.char_array; Output out Interfaces.C.char_array)

ave1: I will, I will, it seems these write-ups explode in depth when doing them!

diana_coman is still toiling on writing this monster chapter 12 eucrypt...

diana_coman: so yes, I totally hear you, ave1

phf: diana_coman: take a look at my recent code for ada/c interop. i've not read your C code closely, but i think you might be missing Trim_Nul => False/Append_Nul => False on your to_c to to_ada, which would trigger sporadic exceptions in the interface code

phf: http://btcbase.org/patches/eucrypt_ch10_oaep_tmsr/tree/eucrypt/smg_keccak/smg_oaep.adb#L29 http://btcbase.org/patches/vdiff_keccak/tree/vtools/src/keccak_c.adb#L63

diana_coman: phf, hm, I *did* use those; the trouble is that in principle the rsa stuff is *not* null terminated as such and I couldn't get them to work properly in such case (or is it not even possible, regardless of passing the length?)

phf: well, so you want them disable, by default they are enabled

diana_coman: yes, I disable them

diana_coman: and it sometimes stops too soon, basically it fails to copy everything ( this is To_Ada but To_C was even more hairy)

diana_coman: obviously, I could also null-terminate specifically for this but overall I'm not convinced anymore it's worth the mess

phf: interesting

phf: it's hard to say what might be failing without seeing the code, but i couldn't get your Hash working out of the box (it was giving me bounadry errors out of the box), i've not gotten back to it though

diana_coman: phf, yes, meanwhile I changed that Hash too, to use same method so that it works out of the box basically

diana_coman: that Hash was the very first attempt, taking To_C and To_Ada at face value

phf: i see

diana_coman: anyways, I'll publish a bit later today chapter 12 and it has the updated Hash too

phf: i'll try my implementation against arbitrary binary data, because right now i'm still passing in C strings essentially. (i've discovered the null trim issue because one of the buffers ran short, and had stale data in it, so ada was getting a character, where null was expected, but the data itself didn't have anything umseemly about it)

phf: diana_coman: i was also getting some boundary issues with different bitrate issues, i couldn't figure out if it can take any natural value, or there's some specifica subranges that i have to stick to. when i spot checked with values like 1200 (or whatever), it would fail deep inside absorbblock. i'll test it again not that i have a bit of free time and see if i can reproduce

phf: *bitrate values

diana_coman: phf, the bitrate has to be less than the total capacity (it should fail however earlier since the Keccak_Rate type is limited correctly)

phf: so anything in 1-1233 should work?

diana_coman: Keccak_Rate is a subrange itself

diana_coman: what did you call exactly?

diana_coman: the default bitrate is 1344 actually; the subrange is between 1 and width of state

phf: Sponge, presumably it should take any length bitstreams for input/output, and some value of bitrate between 1-width. i was calling it with some 10-1000 bitstreams, and a value of bitrate somewhere around 1200

phf: i'm trying to establish if i was seeing a bug, and if it sounds like i might've been i'll try and track it down again

diana_coman: myeah, from what you say alone it does sound like some error but it's not clear without the concrete case

diana_coman: fwiw the bit-level one is meant for any bit numbers stuff; the word-level was in principle set for octet-multiples

diana_coman: but anyway, if there is a problem there I want to hear about it

phf: kk, i'm using the octet one by the way. i should try and drop in the bit level one into the current codebase just to see how that works

spyked: http://btcbase.org/log/2018-03-01#1786626 <-- I ran it on Debian/Adacore 2016 -- system ld is version 2.29.1, and I expect Adacore uses that instead of its own, otherwise I can't explain the behaviour. I'll also give it a try on a Gentoo with same adacore. static inline should be safe from the pov of linkage, but yeah, there's a more general problem there that might benefit from a config.h/system.h or something similar. that or a

a111: Logged on 2018-03-01 18:41 phf: http://btcbase.org/log/2018-03-01#1786600 << which os/compiler is that? i suspect that i'll have to put all the annotations into system.h defines and let specific systems pass whatever in a makefile.

spyked: buildroot env that pins down all these moving parts...

deedbot: http://www.dianacoman.com/2018/03/01/eucrypt-chapter-12-wrapper-c-ada-for-rsa-oaep/ << Ossasepia - EuCrypt Chapter 12: Wrapper C-Ada for RSA + OAEP

diana_coman: http://btcbase.org/log/2018-02-25#1786083 <- EuCrypt?

a111: Logged on 2018-02-25 21:49 trinque: somebody gimme a better rsatron and I'll use that instead.

ben_vulpes: lol i was waitin for that

mircea_popescu: http://btcbase.org/log/2018-03-01#1786609 << lol you asked deedbot, jhvh1 is !~.

a111: Logged on 2018-03-01 17:56 ben_vulpes: shinohai: is this an "it works now" or "you did it wrong" sort of thing. fwiw i expect the former in the form of "it was broken because of X, i did Y to fix it, and Z to prevent it from happening again" not that you're my direct report or anything

mircea_popescu: uh k.

mircea_popescu: a lol, the very next line. ok!

shinohai: the bickening !!!

mircea_popescu: lol

mircea_popescu: http://btcbase.org/log/2018-03-01#1786614 << raid 10, sure.

a111: Logged on 2018-03-01 17:59 ben_vulpes: mircea_popescu diana_coman: my mistake, the box is not raid5 compatible, it can do raid1 and raid10. is this okay and do you have a preference between the two?

ben_vulpes: mircea_popescu: rgr

mircea_popescu: http://btcbase.org/log/2018-03-01#1786616 << just learn a two keystroke combo wth, you know ctrl-^ / ctrl-k but can't do !~ ? name calling is for people not for bots.

a111: Logged on 2018-03-01 18:01 ben_vulpes: having worked to memorize the bot keycombos for some time now, i would particularly like it if they would respond to their names. this approach autocompletes for one and is far more easily visually diffed, for another.

mircea_popescu: http://btcbase.org/log/2018-03-01#1786634 <<

a111: Logged on 2018-03-01 19:03 ave1: mircea_popescu, http://btcbase.org/log/2018-02-28#1786498, which parts of gpg (I can image plain text signing, encryption and decryption).?

mircea_popescu: http://btcbase.org/log/2018-03-01#1786634 << just about, yes.

a111: Logged on 2018-03-01 19:03 ave1: mircea_popescu, http://btcbase.org/log/2018-02-28#1786498, which parts of gpg (I can image plain text signing, encryption and decryption).?

mircea_popescu: pipe though! i want cat x.txt > rrsa -aer stan > y.txt or some sane equivalent.

mircea_popescu: it doesn't have to follow any format but reason.

mircea_popescu: note though that base-whatever is in fact more compact than hexencode.

mircea_popescu: http://btcbase.org/log/2018-03-01#1786657 << sounds like all the makings of a beautiful race condition.

a111: Logged on 2018-03-01 20:01 phf: diana_coman: i was also getting some boundary issues with different bitrate issues, i couldn't figure out if it can take any natural value, or there's some specifica subranges that i have to stick to. when i spot checked with values like 1200 (or whatever), it would fail deep inside absorbblock. i'll test it again not that i have a bit of free time and see if i can reproduce

ben_vulpes: mircea_popescu: statement amended, questions addressed

ben_vulpes: !~later tell PeterL i've responded to your comment

jhvh1: ben_vulpes: The operation succeeded.

mircea_popescu shall read after lunch

BingoBoingo: Disfruta tu almuerzo

deedbot: http://trilema.com/2018/heres-how-pantsuitism-christianity-ruined-civilisation-in-both-the-ancient-and-the-modern-world/ << Trilema - Here's how pantsuitism / christianity ruined civilisation, in both the Ancient and the Modern world.

BingoBoingo: shinohai: There is plenty of source material to cite. Care to write up for Qntra a summary of February's events in the Republic?

trinque: nobody could have predicted scrolling and searching in weechat at the same time.

mircea_popescu: lol

mircea_popescu: ben_vulpes the saga continues (and also, you have what looks like a stranded > right after the "leave your comment" heading)

← 2018-02-28 | 2018-03-02 → ↑