438 entries in 1.025s
hdbuck: i look up from pool.
sks-keyservers.net directly using the 0x… keys from the script
ascii_butugychag: jurov: you can trivially do it right now, just walk all of
sks, if the pubkey is - well - public, you can determine that someone rsa'd to it
assbot: Logged on 23-01-2016 14:31:04; mircea_popescu: well yes. 39 is the old ak/
sks russian thing. nato has a bigger one.
mircea_popescu: well yes. 39 is the old ak/
sks russian thing. nato has a bigger one.
☟︎ mod6: and additionally, this cuts out
SKS.
ben_vulpes: re
sks thread signed bundles of keys on everyone's websites is probably the best way to go
ben_vulpes: since
sks is on the chopping block next, i imagine !register will eventually eat plaintext pubkeys.
phf: what i meant is something like this
http://paste.lisp.org/display/304383. of course each execution of script creates a fresh gnupg keys folder, imports the wot, import from
sks if we're going that way, does the operation, kills the gnupg folder
phf: i understand all that, and i was explaining that there's no conceptual integrity to it, as it stands. we have a .wot folder which is supposed to be a manually curated folder of <nick>.asc files. there were a few threads where mp and ascii argued that the folder should not be generated automatically (no
sks or pre packaged tar files). so if one wants to build a rotor they need a .wot folder with pubkeys of all the foundation
mircea_popescu:
sks is going away. has been, slowly like an avalanche of frozen sewage, but for years now.
pete_dushenski:
http://log.bitcoin-assets.com//?date=13-10-2015#1298016 << update: adam_obrien and i played golf this afternoon and chatted about pgp key-signing. in his excitement at discovering the command line tools, he tried out everything he could find (he's an enthusiastic kid!) and yes, signed my key. he was quite surprised to learn that this changed the key block on the
sks etc servers.. fwiw
☝︎ ascii_field: (that anyone can take an arbitrarily-massive shit into
sks)
ascii_field: it won't surprise me if this brings down
sks as a thing.
phf: how does assbot handle key expirations? does it periodically download new key from
sks or it downloads it if you try and use an expired key?
punkman: trinque: but assbot gets them from
SKS trinque: I can sync them from assbot only if they're on
SKS, and that one didn't appear to be, unless I'm coffee-deficient at the moment
ascii_field: also would be nice to NOT ignore the 5% or so of
sks keys that have utf8-isms in'em
kakobrekla: Varia_Varietatis it takes some time for key to be visible on
sks, apart from that i think you might be hopping the wrong bot
assbot: Logged on 21-04-2015 11:41:31; mircea_popescu: and then $ gpg --keyserver
sks-keyservers.net --send-key <KEYID> and $ gpg --keyserver pgp.mit.edu --send-key <KEYID> where keyid you just copy from the line above.
ascii_field: what is this nonsense with
sks using ssl anyway
mircea_popescu: ;;later tell n6 : can you extract and publish your public key as it resides on your machine, as opposed to whatever's on
sks servers.
decimation: because the
sks server will keep your revoked key forever
mircea_popescu: asciilifeform suppose one day
sks servers list a random key for you too ?
BingoBoingo: ben_vulpes: pgp.mit.edu was a gold mine for academic keys they may not have made the transition to
sks. I retrieved manually though by schoool.
mod6: run this to pull ascii's key: `gpg --keyserver pool.
sks-keyservers.net --recv-keys 0xB98228A001ABFFC7`
ascii_field: and readily admitted to having uploaded it himself, to
sks fluffypony: my company doesn't have a public key in
SKS fromphuctor: I'm pretty sure I uploaded it to
sks years ago
ascii_field: fromphuctor: did you upload your key to
sks? or did it live under your pillow, and you are telling us that someone stole it and uploaded it ?
fluffypony:
SKS doesn't mandate that you remove data to keep in sync
ascii_field: fromphuctor: realize that anyone can submit anything to
sks ascii_field: fromphuctor: afaik nothing has ever disappeared from
sks.
fromphuctor: if my info disappeared from
sks, would it be removed from nosuchlabs
ascii_field: aha, virtually all of the pubkeys in phuctor come from
sks.
trinque: fromphuctor:
sks is the system which distributes public keys
jurov: fromphuctor: did you remove the info from
SKS keyserver, too?
punkman: would be interesting to diff 2004
sks dump with 2015
ascii_field: punkman: it appears to be in the
sks data set
assbot: Logged on 06-05-2015 22:20:53; ascii_field: ;;later tell mircea_popescu ERROR: certificate common name “keys.mattrude.com” doesn’t match requested host name “keyserver.mattrude.com” << when fetching fresh
sks from dulap
assbot: Issue 7241 - go - /openpgp/armor: armored output differs from gpg or
sks armored output - The Go Programming Language - Google Project Hosting ... (
http://bit.ly/1GvmVpz )
mircea_popescu: fromphuctor well atm it's working through a lengthy list of keys already extant on the
sks servers.
decimation: asciilifeform: are you saying google is gonna buy
sks servers and slowly fade them away?
assbot: Logged on 02-06-2015 22:27:24; ascii_field: at this point it probably makes sense to churn the entire
sks db for tuples of keys having same userid and date, and diff all said tuples.
alphonse23_: oh, so if you want to store your pgp some where, so anyone can verify it's you, you upload it to
sks ascii_field: at this point it probably makes sense to churn the entire
sks db for tuples of keys having same userid and date, and diff all said tuples.
☟︎ ascii_field: and it looks like somebody's ddosing
sks ?
jurov: like EDDF63E ... and looks like it was submitted to phuctor directly, i can't find it on
sks keyserver