596100+ entries in 0.371s
mircea_popescu: ben_vulpes i have no idea, it could be done
that way
too
jurov: can't
they jsut sign independently?
ben_vulpes: forgive my derpitude but why not simply sign
the patch and collect sigs?
mircea_popescu: if you're not willing
to sign
the present signs you;'d better fork.
ben_vulpes: mircea_popescu, asciilifeform: re sig stack is
the implication
that a signs patch, b signs patch and a.sig, c patch and b.sig...
jurov: just cut one bit from
the hash
punkman: hash must be smaller
than 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141
punkman: btw some bundles can't be
turned into bitcoin keys, found out by accident
mircea_popescu: anyway. p and q are primes. p-1 and p-1 being necessarily even, will probably have some factors.
these factors could just as well be 65537
jurov: rsa is only possible because we have probabilistic primality
tests for bignums up
to arbitrary certainty
mircea_popescu: stop
trying
to confuse me just because i have nfi of anything!
mircea_popescu: "pick 32 onbit 64bit random numbers,
test for cd" is a much better approach
mircea_popescu: (and for
that matter, it IS quite fucking possible for
the current, fixed e implementation
to spit out badly coded stuff every once in a blue moon, when
the p q happen
to be a multiple of 65537)
mircea_popescu: the idea is just for (q-1)(p-1) and e
to be relatively prime
mircea_popescu: eh fuck it, usgavin promised us 100% increases each year for
the next 200 years
mircea_popescu: afaik it's only used because easy
to compute,
two 1's merged into a word
mircea_popescu: you
telling me
the rsa e must be a fermat prime ? why ?
mircea_popescu: yeah google, always put wikipedia
the fucking first line, because i'm sure
that's what
the "algorithm" says.
jurov: i
they approve
the patch
mircea_popescu: jurov oh yeah, i wasn't commenting on your implementation, i was just bitching at
the stars.
mircea_popescu: asciilifeform incidentally, know of any rng process
to compute fixed count onbits random numbers ?
jurov: mircea_popescu: other people's signatures will be detached from definition... or do you want
to include
the patch everywhere?
mircea_popescu: i wasn't
talking about
the cardano! i was
talking about
the new pgp
mircea_popescu: also doing away with
the 65537 static and instead using any 64bit integer with exactly 32 on bits would be better.
assbot: cryptanalysis - Definition of
Textbook RSA - Cryptography Stack Exchange
jurov: ha. poor qntra writer deeds will contain clause like "receiver is responsible for identifying any circumstances
that may render
this agreement void and act accordingly"
mircea_popescu: so no, it won't imperil
them, it will just make
the peril obvious
mircea_popescu: so
that means
those
toolchains will have
to change or die ?
mircea_popescu: anyway,
thgis is more an aesthetic consideratyion. ditching symmetric cyphers is
the more substantial
thing, and since a reimplementation happenes, might as well add aesthetics.
mircea_popescu: shit son. if only i knew about
this, we could have made diff design changes on bitcoin core.
Apocalyptic: mircea_popescu, I just found
that line
to fix
the issue, but
thank you
assbot: Logged on 16-10-2014 14:00:51; mircea_popescu: btw, cazalla bingoboingo and everyone else in
the same situation : if
the blob gpg spits out when you sign contains a SHA1 you are using
the older, and perhaps not all
that secure digest algo. you should move on
to sha512 either with --digest-algo SHA512 or else edit gpg.conf
to insert personal-digest-preferences SHA512 SHA384 SHA256
mircea_popescu: and again, armored. nothing but letters and digits in
there. not even +/ etc.
mircea_popescu: proggy gets 65kb file, cuts 16k off its end recursively, spits out 1kb of
text signed by 4 people
mircea_popescu: asciilifeform obviously, since fixed length, it can go back
to
the end of
the file.
Apocalyptic: just noticed
that all deeds processed by deadbot are SHA1-hashed so far
mircea_popescu: much simpler machines
to work it if it knows a straight offset
mircea_popescu: Apocalyptic not considered read, but weak digest. good idea
to upgrade.
mircea_popescu: file is defined as, 256bytes + "#####
The following is signed above :"+message.
bounce: sha1 is on
the way out (don't use for new stuff) but not dead yet (can keep using what you have)
Apocalyptic: by
the way are SHA1 gpg-signed messages considered read ? I read somewhere one might rather use sha256 or higher, don't know if
there's any merit
to
that claim
bounce: that's
the
technology equivalent of "hold my beer and watch
this"
mircea_popescu: add
to
that a fixed-offset clearsigned
thing, all of a sudden
there's good reason
to implement
mircea_popescu: you know,
thinking about
this, i
think i actyally want pgp reimplemented. usgavin's speshul maths about how
things improve make me realise
that having a pure rsa based code rather
than
the current encode a symmetric chypher method is perhaps feasible.
mircea_popescu: clearsigned file, always 16kb long, after which
the signed matter begins
mircea_popescu: asciilifeform: ideally, we'd have a patch and a collection of detached sigs of
the plain ascii of
the patch <<< detached sigs are in fact a reimplementation of
the old punch cards
kakobrekla: just wait for
the google
to parse logs