log☇︎
452200+ entries in 0.289s
mats: port as to be found on 'pypi'
mod6: ~ how big is the file?
mats: jurov: and this behavior is the same across c pgpdump and python port?
mircea_popescu: so far this has been an exercise in ridiculous.
mircea_popescu: mod6 i think i will try rsync yeah
mircea_popescu: i dun think php is in any way involved.
jurov: (obv such tasks should bypass PHP completely)
jurov: maybe there's some dummy PHP script on server that chokes when hit 2G mem limit
jurov: what's on the other end?
mircea_popescu: i tried that with -C but no dice.
jurov: alternatively, maybe curl can be asked to download ranges (if server supports it)
mircea_popescu: asciilifeform srsly, split takes 10 minutes for a 1 gb. upload takes 1 minute.
jurov: yes, apparently they balked at decnsing "pkcs1" stuff
mircea_popescu: srsly, two octets should be enough for everyone ? this is how it is ?
mircea_popescu: jurov motherfucker! WHO DOES THESE THINGS
felipelalli: trinque: if I add the option --charset=utf-8 when signing, helps something?
mircea_popescu: it's slower to split than to upload o.O
jurov: mats, ascii_field pursuant to http://tools.ietf.org/html/rfc4880#section-5.2.2 ,the pgpdump lib stops parsing right on the "Two-octet field holding left 16 bits of signed hash value" and does not go further to decode the signature
mircea_popescu: atm i suspect it's doing something windows-retarded like "load whole file in memory, split it as a php array, write the result through type conversion"
trinque: felipelalli: ascii was good enough for the lord and it's good enough for me!
ascii_field: yeah at some point ~new~ phuctor will run over all the weirdos with non-latinate chars in namestring of key
trinque: gpg likes your doc just fine, and python has your doc as a string identical to what was provided
felipelalli: GPG is a little tricky with charsets.
trinque: this is just about past my shoot-in-head threshold
felipelalli: Ah! The problem is the "ã" char!! hahahah
trinque: just python string nonsense; I should've written this part in bash
mats: er, trinque is the maintainer
ascii_field: vaguely recall the drm thing
mircea_popescu: because that's how you hoodwink investors, that's why!
mircea_popescu: you read that story about the guy developing a drm thing for the palm pilot ?
ascii_field: the one part i'm unclear on is why the scam needed programmers at all
mircea_popescu: so yeah, why do you people believe me that in fact miller & elaine whatever actually ran an unapproved scam on u of maryland dime ?!?!?
mircea_popescu: chicklet's the sister of one/wife of the other or viceversa.
ascii_field looks for hat to eat
mircea_popescu: anyway, ascii_field, apparently the dean is asking some questions eh ? ☟︎
mircea_popescu: i guess im back to slicing archives. ima call them .rar too, in memory of the old days
jurov: mats as the .sig file verifies, the hash must be therein
ielo: its really sad that this is your life
mircea_popescu: what the fucking hell already nothing works!
mircea_popescu: motherfucker. and ~confirmed~ that the problem does not exist for files under 2gb.
ielo: mircea_popescu, you are the fuckface what the fuck have you done for bitcoin? you literally called an asian woman a gookface, what the fuck kind of person are you? ☟︎
mats: i am using pgpdump for a project and this is relevant
mats: trying to figure out if its the library or the thing you're wrenching is at fault
mircea_popescu: ielo would this be the conference where tyhat fucktard nefario told everyone about how mpex is going to be going to jale two weeks before going to jale ?
mircea_popescu: seriously, taaki ?
ielo: mircea_popescu, you literally dedicate your life to gossiping about shit you know nothing about
mircea_popescu: maybe if your friends would stop scamming / being retarded pieces of shit i wouldn't have to care about their otherwise meaningless existences ?
mats: oh, those are scammers.
jurov: mats the data structure i get does include "hash_algorithm" but ntohing resembling actual hash
mircea_popescu: they have the southern system here.
ielo: amir taak, andrew miller 2 main ones
trinque: if only we had the nordic system, somebody would help poor mircea_popescu
ascii_field: anybody got a vivisection table open for the monkey ?
mats: ielo: which people? name them.
ielo: mircea_popescu, i think you need mental help
jurov: anyway, looks pgpdump monkeys never bothered to pull actual hash out :/
ielo: sorry i think you need to stop
ielo: mircea_popescu, i'm just sick of your shit you've independently claimed like 3 people i know are scammers and your life is literally gossiping on the internet ☟︎
mircea_popescu: the thing will burst ~3mb, then stop. then burst again then stop.
mircea_popescu: get a load of that.
ielo: mircea_popescu, < why does this retard gossip like a 12 year old and you guys believe it?
ascii_field: mircea_popescu: never saw this!
mircea_popescu: bah. from the wunderbar world of undocumented linux gotchas : if you're transferring a file over 2gb, either curl or wget will go into "download one burst, rest for 30 seconds" mode and that's that.
mod6: ok, i think this thing installed, but i can't figure out how to get it to run lol.
felipelalli: the bot is in a bad mood today.
trinque goes to slap deedbot- around in private
ascii_field: jurov is right though, the one for which i gave the args is the c proggy
mod6: it's the one you linked above though 'H?
ascii_field: (yes, there are two proggies by same name)
jurov: app-crypt/pgpdump indeed does not show the hash (and it's not python but binary)
trinque: it's not the site though, I'm allowing any
mod6: ascii_field: hey, i'm having a tough time getting the hash itself out of a sig file of mine with that python version of pgpdump. which flag should i be using; i've tried 'em all
mircea_popescu: ascii_field they're merely trying to survive and perpetuate, them mediocrities.a
assbot: Logged on 26-06-2015 20:43:32; trinque: I'm not at all impressed with the fact that when I asked for an education in CS, I was not presented with this.
ascii_field: http://log.bitcoin-assets.com/?date=26-06-2015#1178148 << will add to this. in every single field i dive into, i find these 'lisps' - i.e., the ~actual~ state-of-the-art buried under piles of shit strategically crapped out by one, two, more generations of mediocrities ☝︎☟︎
mircea_popescu: ED5CDE14 that's the right key...
assbot: Trust relationship from user assbot to user felipelalli: Level 1: 0, Level 2: 2 via 2 connections. |http://www.btcalpha.com/wot/trust/?from=assbot&to=felipelalli | http://www.btcalpha.com/wot/user/felipelalli/
jurov: you could tell earlier there's a way to get hash from signature
jurov: iirc i have searched for something liek that but did not found it
jurov: there is lubrary for this?
ascii_field: notice that you don't even need the patch file for this
jurov: if not by ID, then people must meticulously keep adhering to original name
jurov: there must be a way to refer to original submission
mircea_popescu: ascii_field idea was to have one file multiple sigs
mod6: so after review you just expect or perhaps exepect to just see a .sig file attached alone without the patch itself?
jurov: ascii_field: it was intended to allow other people to send singatures for patches ater they revviewed them
jurov: match it to original submission
jurov: and user is unwilling to work with patch ID the system must somehow heuristically
ascii_field: why would these ever come apart ?
ascii_field: that is the correct place for it
ascii_field: mod6: it's in the sig!
mod6: anyway, i like the idea of a checksum for the patches. if we can somehow hvae that without it being in the name of the patch, that would be neat.
assbot: Logged on 26-06-2015 19:00:30; mircea_popescu: who was the other accidental windfall victim who actually WAS into bitcoin ?
ascii_field: but for those discussions to make sense, the patch had to be out there
mod6: i think the nomenclature is pretty straightforward. easy to use. you specify which base your coming off of, the patch name, and a number for any that are required to come before it.
jurov: well, where is the context what is "portatronic" ought to be?
ascii_field: some can - must - only make sense in thread context
ascii_field: jurov: also ought to remember, not all patches are meant as 'canonical' (that is, for eventual inclusion in the tree)
mod6: why are they the worst?
jurov: ok ascii_field not turd , but this leaves things to be desired, too: http://therealbitcoin.org/ml/btc-dev/2015-January/000033.html ☟︎