log☇︎
269200+ entries in 0.185s
mircea_popescu: so when feeding the prime generator, it doesn't just feed ap ointer, but unwraps the thing through mpi-something
asciilifeform: which is to see what happens to p2,q2 when you make 4096+ bit moduli.
asciilifeform: at any rate, it is now possible to do the thing i ACTUALLY SET OUT to do
asciilifeform: i hesitate to use word 'correct' in relation to something gpg does...
mircea_popescu: that gpg reads the correct number
mircea_popescu: is this a matter of fact ?
asciilifeform: as crappable into, e.g., python, to arithmetize on.
asciilifeform: pgpdump -i displays the actual int.
asciilifeform: which, fortunately, we do not need to care about
mircea_popescu: ok. and this does not actually correspond to the numeric format as used by gpg's bignum because mpi reasons.
asciilifeform: and so it allocates chunks on the heap
asciilifeform: mircea_popescu: mpi was written by braindamaged folk who believed that bigint ought to be able to 'grow infinitely'
asciilifeform: which transforms to an actual sequence of meaningful bits of the bignum via a gnarly process.
mircea_popescu: i thought it's a memory dump
asciilifeform: mircea_popescu: not stack. the raw mpi turd.
mircea_popescu: so basically, log_hexdump just reads off the stack, and it mostly reads garbage ?
mod6: <+asciilifeform> ^ the corrected patch. << I've got these changes in now.
asciilifeform: i'ma never live this down, will i.
asciilifeform: ^ the corrected patch.
asciilifeform: mpidump shows the thing you end up seeing in pgpdump -i.
asciilifeform: and padding at the end of each chunk.
asciilifeform: that does not correspond to an integer, as such, it has pieces of it, chunks, each having a header
asciilifeform: mircea_popescu this is still a raw mpi hexdump
asciilifeform: ( aaaaaanyway my ORIGINAL aim when i wrote the tester, was to look at what happens at 4096 and above. which i haven't even done yet ..! )
asciilifeform: 2 ain't 32 tho.
asciilifeform: but we knew this 20yrs ago.
mircea_popescu: asciilifeform you recall the comment about "setting the two high order bits" ?
mircea_popescu: that "move the mouse and utilize the disk" thing at the top is so fucking lulzy...
mircea_popescu: mod6 check out all teh zerofields...
mircea_popescu: the FF FF endings are the concern.
asciilifeform: and probably ought to go to bed
mircea_popescu: you're having entirely too much fun.
asciilifeform: ok turns out that nobody can count x2.
asciilifeform: mircea_popescu: and what did the p and q in the privkey look like ?
asciilifeform: the output of 'YieldPrime', per my model, ought to end up in http://btcbase.org/log/2016-08-18#1524021 ☝︎
mircea_popescu: open source means the code is readable!
asciilifeform: so far i am at a loss as to how one becomes the other.
mircea_popescu put them through a binarytron
mircea_popescu: no, the p and q from http://wotpaste.cascadianhacker.com/pastes/ababdff0-7902-42b8-9d39-732e1a701116/?raw=true
mircea_popescu: i dunno but the p an q in your example share nothing useful.
mod6: <+asciilifeform> anyway the patch ^ shown above is the ticket. << recompiling for gpg2
asciilifeform: how the fuck these turn into the sane-looking p's and q's.
asciilifeform: now for the $64k question:
asciilifeform: which is why i post the actual in and out, instead of contents of my head.
asciilifeform: anyway the patch ^ shown above is the ticket.
asciilifeform: did i push that button??
mircea_popescu: <asciilifeform> ought to be log_hexdump("\nYieldPrime: \n", ptest, nbits/8.); <<
asciilifeform: and what did mircea_popescu use for a compiler, that ate this.
asciilifeform: dafuq would an unintegral number of bits refer to ??
asciilifeform: i'ma let one of you fellers tell me when i wake up why 11 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 also didn't happen
asciilifeform: see folks, this is why i didn't qntra this yet, dun wanna pons&fleischmann it.
mod6: i can do 2.0.30 with this ^ if that helps
asciilifeform: ought to be log_hexdump("\nYieldPrime: \n", ptest, nbits/8.);
asciilifeform: not one of us, it turns out, can count
asciilifeform: let's try a small variation on the theme.
asciilifeform: dun forget to glue a saf to an ety first.
mircea_popescu: "to make sure safety is met, we ductape some met to the safety"
asciilifeform: which brings us to here and now.
mircea_popescu: ah, that explains the weird leading.
asciilifeform: AAAAAND this is where we dump the buffer.
asciilifeform: (apologies for l0g bloat, but this has to be done..)
asciilifeform: the requested keysize we set the 2 high order bits */
asciilifeform: doing that for RSA, to make sure that the modulus does have
asciilifeform: /* Set high order bit to 1, set low order bit to 0.
asciilifeform: which then gets, for good shitgnomatic measure,
asciilifeform: i'll walk through here:
asciilifeform: thing is, nextprime cannot walk all that far
asciilifeform: ... it looks as if there is an extra layer of shuffle not accounted for by the dump?
mod6: i can regen tho
mod6: oh, i did the same. "asdf" iirc.
asciilifeform: mircea_popescu: this is useless
mircea_popescu: atm i can't takle the aggravation of bulding anything.
mircea_popescu: Install these packages without verification [y/N]?
mircea_popescu: WARNING: The following packages cannot be authenticated!
mircea_popescu: asciilifeform what were you cutting these up with again ?
mircea_popescu: anyway, http://wotpaste.cascadianhacker.com/pastes/9a20f5a7-7afd-4a74-ad78-b8217288c5e6/?raw=true << the two just generated keys.
mircea_popescu: including if you try -r
mircea_popescu: this is weird... so this thing when told to dump priv key dumps THE SAME BLOCK irrespective of which user is indicated.
asciilifeform: so this thing parallelizes 'embarrasingly'.
asciilifeform: note that this is an upper bound, it applies regardless of what kind of magic is used.
asciilifeform: is this obvious or do i need to draw picture.
asciilifeform: if we know B - k shared topmost bits, then the work required to break in comparison with work W, supposing we knew B bits, is at most W*(2^k).
asciilifeform: btw, here is a handy elementary proof of a certain thing,
asciilifeform: not necessarily top, or bottom of prime.
asciilifeform: the other thing,
mircea_popescu: asciilifeform trivial for me to dump these i just generated, let's see
mircea_popescu: http://wotpaste.cascadianhacker.com/pastes/55bf0b65-8784-49f0-895b-e3eb0793afc7/?raw=true << further 1.4. the ff's went away, 0s came in...
asciilifeform: and all of p1,q1,p2,q2 share at least top 20 bit.
asciilifeform: but chances are that p1 and q1 share top 32 bit
mircea_popescu: so then what'd be surprising or wut ?
asciilifeform: nothing odd, of course, to the naked aye.
mircea_popescu: you mean, they start with same 4 bits ?
asciilifeform: http://wotpaste.cascadianhacker.com/pastes/f6355da8-4a82-40d2-a6a0-d1217232dbac/?raw=true << this, for instance, is mircea_popescu's pub.
mircea_popescu: to the lulz mine ?
asciilifeform: does mircea_popescu fully apprehend where this train is going ?
asciilifeform: this is promising to be a very awkward occasion.
asciilifeform: the diddled rng being the first.
asciilifeform: soooo the subkey idiocy is apparently the 2nd half of a bipartite poison.
mircea_popescu: in other lulz : when generating a new key, name NEEDS to be at least 5 chars long. password however - can be 4.
mircea_popescu: and look at all the bonus zero fields