1400+ entries in 0.466s
assbot: Searching
pgp.mit.edu for key with fingerprint: 551516687E08CB0D60CA4A56D9AEA7019BAAD3FE. This may take a few moments.
phf: mircea_popescu: you know it was just b-a of the 1800s. << i think of b-a as more of a stonemasone guild, then a fraternity. maybe in a couple of hundred years when b-a has hereditary wot ratings and ceremonial
pgp keys that are not otherwise used for anything. the way i read that joke is that one has the trappings and the other has a trowel that is used for its direct purpose.
assbot: Logged on 06-08-2015 22:09:02; mircea_popescu:
http://log.bitcoin-assets.com/?date=06-08-2015#1228030 << to expound on this for the log readership : it is not trivial but definitely feasible to cause any running implementation of asymmetric cryptography to leak key bits if it is possible to direct encrypted matter at it in an automatic fashion and have live access to the results somehow. this theoretical fact is practically verified for
pgp, and
mircea_popescu: if you are going to put something, put
pgp. not pki, and in no case
http for a stateful machine.
assbot: Searching
pgp.mit.edu for key with fingerprint: 4A0363951AFA090B6C221787E2F23DB84A63EC22. This may take a few moments.
mircea_popescu: asciilifeform making a key server for a basically defunct implementation of
pgp not really much of a priority
brg444: yea. looking into that now but tbf this is sorta new to me. using this stupid gui and it doesn't seem to want to connect to
pgp.mit.edu for some obscure reason.
assbot: No valid OpenPGP data found on
pgp.mit.edu.
assbot: Searching
pgp.mit.edu for key with fingerprint: 4A0363951AFA090B6C221787E2F23DB84A63EC22. This may take a few moments.
assbot: Searching
pgp.mit.edu for key with fingerprint: 16C81597E76E86E6C01EF037AA4B3330F162C410. This may take a few moments.
cazalla: punkman, ya think as much as a single person uses that facebook
pgp?
assbot: Logged on 20-09-2015 23:09:19; adlai:
pgp is just silly
adlai: there's no
pgp key block, it's quoted :P
assbot: Logged on 18-09-2015 22:15:20; punkman: mats: punkman: if it was not clear, i am handrolling the
pgp packet parser in python (watta mouthful). and not having a good time of it. << I think you might have to come up << you should probably throw out a bunch of idiocies contained in the canonical rfc
punkman: mats: punkman: if it was not clear, i am handrolling the
pgp packet parser in python (watta mouthful). and not having a good time of it. << I think you might have to come up << you should probably throw out a bunch of idiocies contained in the canonical rfc
☟︎ mats: punkman: if it was not clear, i am handrolling the
pgp packet parser in python (watta mouthful). and not having a good time of it.
assbot: Logged on 16-09-2015 13:29:47; punkman: "very interested to see what details (if any) emerge from @cryptomeorg regarding its supposed key compromise." Answer: "Suspects: Truecrypt, SCS in DC,
PGP flaw, all the other usuals."
punkman: mircea_popescu: I'm sure meta-JY doesn't even use
PGP for windows
punkman: "very interested to see what details (if any) emerge from @cryptomeorg regarding its supposed key compromise." Answer: "Suspects: Truecrypt, SCS in DC,
PGP flaw, all the other usuals."
☟︎ assbot: Logged on 15-09-2015 20:25:14; anton_osika: mircea_popescu: you wrote the contract - the "long party" is the payer of the invoice". Nowhere does it state that the "long party" will need a
PGP signature for payment. This is solely interpretation - and you are NOT paying for a future delivery contract. Do you have any rationale for this?
anton_osika: mircea_popescu: you wrote the contract - the "long party" is the payer of the invoice". Nowhere does it state that the "long party" will need a
PGP signature for payment. This is solely interpretation - and you are NOT paying for a future delivery contract. Do you have any rationale for this?
anton_osika: mircea_popescu: you wrote the contract - the "long party" is the payer of the invoice". Nowhere does it state that the "long party" will need a
PGP signature for payment. This is solely interpretation - and you are NOT paying for a future delivery contract. Do you have any rationale for this?
☟︎ anton_osika: There is a Kraken
PGP key here that a lot of people that hold their trust (even in forms of assets) dearly to it . Those people would forever lose some of the trust for you.
mircea_popescu: <mats> otherwise it'd be meatfacebook << lol. it's either
pgp or meat, baby.
shinohai: When you PM'd me and said you had your "
PGP keys unprobabilistically stolen" I was left scratching my head.
mircea_popescu: anton_osika i don't understand what you think
pgp sigs have to do with phuctor ?
anton_osika: In some chain of events however unlikely any of you would lose your
PGP identities.
nubbins`: or would you like for contracts signed with your
pgp key to only be resolved via that same key?
mod6: just busted into your place? did they get a copy of your
PGP key?
mod6: bring ur
pgp key next time! :]
ascii_field: surely mircea_popescu knows that usg (esp. .mil) makes heavy use of an internal tard
pgp by microshit
BingoBoingo: <gabriel_laddel> trinque: I have a listing of programs associated with my
PGP identity, you can make references to them, and people will be able to see them (or not) based on my trust relationship with them... << It is essential for WoT to exist that I can safely point at the enemy's words and bury them in sulfur
gabriel_laddel: trinque: I have a listing of programs associated with my
PGP identity, you can make references to them, and people will be able to see them (or not) based on my trust relationship with them. Your "references" can be any arbitary computation, buut probably some standards will evolve (e.g., we don't check sexprs who pass some test of being a plist of the structure (:name ... :version ...)).
ascii_field: 1) did you ungzip it 2) did you verify my
pgp sig
pete_dushenski: mats: but how comes the
pgp keyserver ? will it also be zany ?
ascii_field: ^ from my reading, this had a very real chance of destroying the non-
pgp contract as even a theatrical production
ascii_field: see the discussion of
pgp key timestamps some months back
assbot: Searching
pgp.mit.edu for key with fingerprint: D1702BB1EE057FAA3ED134AA922837F6B1FC09A3. This may take a few moments.
mats: the rfc defining
pgp packets makes my brain hurt
assbot: Searching
pgp.mit.edu for key with fingerprint: 6310C4E0B0E97287A3CFEBAD8515F76EADCFD13C. This may take a few moments.
punkman: "If you are part of the
PGP strong set or your
PGP key is on bitcoin-otc you now have a timestamp. Take your
PGP fingerprint and convert that into a Bitcoin address and you'll find a 1 satoshi payment to it"
mircea_popescu: you can tell by all the breadcrumbs the use of
pgp is so insecure it's outright spurious.
mircea_popescu: also hanbot has it : idempotence IS fundamental to bitcoin. but unlike shit like sybil attack, or
pgp, which were scarcely used or thought about before we came around,
mike_c: sure, generally. but if you're building a
pgp interface.. obviously assbot has done so
williamdunne: mircea_popescu: you probably own one of the most valuable
pgp/email lists going..
mircea_popescu: hopefully we get a
pgp implementation that's usable sometime this side of the decade.
mike_c: hand-coded
PGP impelementation in PHP and javascript
mircea_popescu: should be fun once
pgp is implemented properly as full rsa.
mircea_popescu: mike_c another premature thing is a
pgp implementation that's proper.
assbot: Logged on 23-08-2015 00:42:58; mircea_popescu: incidentally asciilifeform and whoever else is privately thinking of reimplementing
pgp : one thing i'd dearly love would be the ability to encrypt not to X, but to "l1".
assbot: Logged on 23-08-2015 21:42:47; mircea_popescu: point was agreed to before i think. which is how the discussion re what
pgp implementation must be like got started.
mircea_popescu: point was agreed to before i think. which is how the discussion re what
pgp implementation must be like got started.
☟︎ mircea_popescu: incidentally asciilifeform and whoever else is privately thinking of reimplementing
pgp : one thing i'd dearly love would be the ability to encrypt not to X, but to "l1".
☟︎