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
mircea_popescu: ok. and
this does not actually correspond
to
the numeric format as used by gpg's bignum because mpi reasons.
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.
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: 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
mircea_popescu: <asciilifeform> ought
to be log_hexdump("\nYieldPrime: \n", ptest, nbits/8.); <<
mod6: i can do 2.0.30 with
this ^ if
that helps
mircea_popescu: "to make sure safety is met, we ductape some met
to
the safety"
mod6: oh, i did
the same. "asdf" iirc.
mircea_popescu: atm i can't
takle
the aggravation of bulding anything.
mircea_popescu: WARNING:
The following packages cannot be authenticated!
mircea_popescu: asciilifeform what were you cutting
these up with again ?
mircea_popescu: this is weird... so
this
thing when
told
to dump priv key dumps
THE SAME BLOCK irrespective of which user is indicated.
mircea_popescu: asciilifeform
trivial for me
to dump
these i just generated, let's see
mircea_popescu: in other lulz : when generating a new key, name NEEDS
to be at least 5 chars long. password however - can be 4.