1100+ entries in 0.325s
mircea_popescu: you're not trying to argue that
gpg is to be replaced are you ?
ascii_field: there are 3 separate rng subsystems in
gpg 1.4 - but more on this later)
mircea_popescu: (and yes, cwcd, not possible w/o bitcoin,
gpg, people involved, an actual infrastructure)
mircea_popescu: what are you trying to fix, the atrocious
gpg malleability issues ?
☟︎ mircea_popescu: moreover she didn't want to / understand she has to make a
gpg, and i dun wanna encourage the demuring damsels.
mircea_popescu:
http://log.bitcoin-assets.com/?date=23-10-2015#1306332 << and if you were to be against
gpg, or against signed commits, or against "not everyone is/can be a contriobutor" or for "women in tech" in the sense of lipstick in the optic drive or a bunch of other equally nutty notionms, you could equally say "i don't think i am alone" and more importantly, FIND YOURSELF INCLINED TO SAY IT
☝︎ mircea_popescu: Send code snippets and
GPG signed material in separate
GPG encrypted blocks. This protects them from painful mutilation. < ? !
mircea_popescu: BingoBoingo " The submission may be, usually ought to be
GPG encrypted" no lassitudo. pick one, stick with it.
mircea_popescu: bitcoind is frozen on 0.5.x ;
gpg is frozen on 1.4.x ; eulora is frozen in cs dependencies on X Y Z. guess why ?
mircea_popescu: in fact
gpg has a lot in commnon with bitcoin : an original prototype of a good idea, with a lot of quick and dirty stuff,
☟︎ mircea_popescu: otherwise yes,
gpg is, and remains, slated for replacement.
ascii_field: '
GPG throws a warning [3] that the message could have been modified, but other implementations do not differentiate between SE and SEIP.' << what 'other implementations' ? microshit crypto ?
mircea_popescu: if so inclined, i could just set a box too old to be bitcoin node to generate and register
gpg sigs
mircea_popescu: actually the
gpg specification is so miserable, a code prototype in the way of bitcoind as an intermediate step to rescuing the standard and restating it properly is prolly unavoidable.
mircea_popescu: anton_osika a)
gpg contracts are already defined, cuz that article ; b) we don't agree.
ascii_field struggles to think of even one useful tool that doesn't have a retarded usgized variant - e.g.,
gpg mircea_popescu:
http://log.bitcoin-assets.com/?date=09-09-2015#1267251 << moreover, if
gpg messages were code rather than data i'd have
gpg rewritten to a thing that keeps messages strictly as data. BingoBoingo exactly has it : there is no room nor need for every bit of text to be "really code". i want my nano to be UNABLE to do anything whatsoever with the text. which is why i use nano rather than emacs.
☝︎ mircea_popescu:
gpg: Good signature from "Mircea Popescu (Acest articol are apriori
mircea_popescu:
gpg: Signature made Fri 04 Sep 2015 11:22:04 PM ART using RSA key ID 2FB7B452
mircea_popescu: $
gpg --verify florianweimer.fuckeveryonewhowaseverinvolvedincomputersyouarethereasonthingsuckihopeyougetcanceranddie.asc florianweimer.fuckeveryonewhowaseverinvolvedincomputersyouarethereasonthingsuckihopeyougetcanceranddie
ascii_field: yes, i would ~like~ a gcc library; (and a
gpg library.) but i understand the authors' logic re: how this could easily and catastrophically help the enemy
mircea_popescu: lol. if you're using the stock scheme of logs, they dump like
gpg dumps. only a portion
mircea_popescu: i guess the next top priority in making cardano which was making bitcoin which was making vdiff is now making
gpg.
mircea_popescu: lol buttcoin engaging danielpbarron over
gpg etc was pretty lulzy to read.
ascii_field: btw here's another thing to add to the '
gpg is mega-retarded' list:
gpg sig does not contain a sig of self !!
mircea_popescu: which is a harder proposition than nobody ever used
gpg.
mircea_popescu: so basically diff is, much like
gpg, not actually usable.
mircea_popescu: incidentally : if
gpg had the fucking sense to include MORE information on its information line, we wouldn't have the problem with the dashes.
☟︎