log☇︎
2100+ entries in 0.533s
asciilifeform: and he doesn't like paper otp !
asciilifeform: sigsally was the first electronic otp, american, used vocoder (in '40s!) but used ordinary vinyl record
asciilifeform: the weak link of ancient otp was always the rng.
mircea_popescu: "if thge best you can come up with is otp - give me back the cpu and take this mechanical gearbox instead" ☟︎
mircea_popescu: the punishment for otp is "you may not use computer anymore"
asciilifeform: good otp is easier now than ever.
asciilifeform: otp.
asciilifeform: in correct otp, you ~never~ get a situation where same block -> same output
mircea_popescu: otp has block size = message size by definition.
asciilifeform: otp has no block size
mircea_popescu: otp is... not chained
ascii_butugychag: (cipher in the non-otp sense)
ascii_butugychag: that is, vernam (otp) and that's IT
copypaste: kakobrekla: I'd like to make a request if you have a moment. When I get my OTP from assbot, it sends the header `Content-Type: application/json; charset=utf-8` ... This causes my browser to incorrectly interpret GnuPG documents as JSON, so it spews annoying errors which prevent me from just doing Ctrl-A Ctrl-C...to wit, "There was an error parsing the JSON document. The document may not be
assbot: Request successful, get your OTP: http://w.b-a.link/otp/d26d0b8b2603e53d
ascii_butugychag: may as well otp then
ascii_butugychag: this is trivial for, e.g., otp, but - i suspect provably - a no-go for anything else, esp. anything asymmetric.
assbot: Request successful, get your OTP: http://w.b-a.link/otp/e0b87e28121f253c
assbot: Request successful, get your OTP: http://w.b-a.link/otp/98b3014b9613d9dd
assbot: Request successful, get your OTP: http://w.b-a.link/otp/5b4786450aa1d5d9
assbot: Request successful, get your OTP: http://w.b-a.link/otp/c146a772e789a4bb
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a253b0cd1e7a868c
gribble: Request successful for user mircea_popescu, hostmask mircea_popescu!~Mircea@pdpc/supporter/silver/mircea-popescu. Get your encrypted OTP from http://bitcoin-otc.com/otps/8A736F0E2FB7B452
pete_dushenski: now you can /msg assbot !up then decrypt the otp then !v it
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a5114aaf160eb22d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/8522aded55a732a2
assbot: Request successful, get your OTP: http://w.b-a.link/otp/e90b93be43ae09f0
assbot: Request successful, get your OTP: http://w.b-a.link/otp/022dafc3c5d7eabb
assbot: Request successful, get your OTP: http://w.b-a.link/otp/58dc0bb375decb96
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a51dd4d25310674e
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a51bc4c939860f84
ascii_butugychag: (for n00bz: lamport signature is to signing approx. what otp is to encipherment)
assbot: Request successful, get your OTP: http://w.b-a.link/otp/d632fb127a3c8539
assbot: Request successful, get your OTP: http://w.b-a.link/otp/41e67c2b09f60f52
assbot: Request successful, get your OTP: http://w.b-a.link/otp/19b3c59e78307eaf
assbot: Request successful, get your OTP: http://w.b-a.link/otp/3e626c77d8bc9993
assbot: Request successful, get your OTP: http://w.b-a.link/otp/49feb75b92cbe172
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a26deac33f7f53eb
assbot: Request successful, get your OTP: http://w.b-a.link/otp/6919df6602129ae4
assbot: Request successful, get your OTP: http://w.b-a.link/otp/2dd7a8aade305961
assbot: Request successful, get your OTP: http://w.b-a.link/otp/76f7be33cbc7e2c5
assbot: Request successful, get your OTP: http://w.b-a.link/otp/d96104fc0ebce28f
assbot: Request successful, get your OTP: http://w.b-a.link/otp/f85504a26e483a8c
assbot: Request successful, get your OTP: http://w.b-a.link/otp/c07a32caa47b77e8
assbot: Logged on 25-12-2015 20:38:47; ben_vulpes: punkman, mircea_popescu, asciilifeform: destestable though they may be for injecting state into the stateless protocol, would a single "signin" page with an assbot-style decryption of OTP that results in a session key authenticating the user to the perlwad be an improvement, and are there better solutions i'm not considering? anonymous drive-by pasting is not a better solution imho.
ben_vulpes: punkman, mircea_popescu, asciilifeform: destestable though they may be for injecting state into the stateless protocol, would a single "signin" page with an assbot-style decryption of OTP that results in a session key authenticating the user to the perlwad be an improvement, and are there better solutions i'm not considering? anonymous drive-by pasting is not a better solution imho. ☟︎
asciilifeform: http://log.bitcoin-assets.com/?date=24-12-2015#1351837 << mega-b00k describes a kgb legend: the first man who explained to beria how otp is provably 'perfect'-secure, was allowed to leave lubyanka - but at the door they took his employee pass ☝︎
assbot: Request successful, get your OTP: http://w.b-a.link/otp/8e26369d5447b582
assbot: Request successful, get your OTP: http://w.b-a.link/otp/cba0cee9558c0bb4
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a284b5fb194c89ae
assbot: Request successful, get your OTP: http://w.b-a.link/otp/5a57b534b1e4c6ff
assbot: Request successful, get your OTP: http://w.b-a.link/otp/000c9bca048d0d2d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/af2795bc98831c9c
trinque: CoraCrisT: decrypt your otp there and provide with !v
assbot: Request successful, get your OTP: http://w.b-a.link/otp/6e69a4cb9d87138b
assbot: Request successful, get your OTP: http://w.b-a.link/otp/13843bbff8c05cdb
assbot: Request successful, get your OTP: http://w.b-a.link/otp/de3077e0b2eb9325
assbot: Request successful, get your OTP: http://w.b-a.link/otp/04cc996ebe31d5bf
assbot: Request successful, get your OTP: http://w.b-a.link/otp/7096629248af140f
gribble: Request successful for user mircea_popescu, hostmask mircea_popescu!~Mircea@pdpc/supporter/silver/mircea-popescu. Get your encrypted OTP from http://bitcoin-otc.com/otps/8A736F0E2FB7B452
assbot: Request successful, get your OTP: http://w.b-a.link/otp/c0eca0ff96891b90
assbot: Request successful, get your OTP: http://w.b-a.link/otp/48186f880d4bcfc0
assbot: Request successful, get your OTP: http://w.b-a.link/otp/253aae5928c59d57
assbot: Request successful, get your OTP: http://w.b-a.link/otp/786bebe599d1f35c
asciilifeform: with anything like genuine otp, the 'prior after the fact' is really 'after the fact' plain and simple,
mircea_popescu: PeterL the only way otp works is with prior agreement. as alf says, there's no known alternative ot this.
assbot: Request successful, get your OTP: http://w.b-a.link/otp/27814f0bdea07cec
ascii_field: ('serious' crypto was strictly otp in su lands, as it is today. field crypto was, often, 19th c.-style transposition derpery, relying largely on the very short useful life of the message to avoid being broken)
ascii_field: jurov: su state of the art re: crypto, as far as i can tell, was ~deadly boring~ - good ol' vernam otp
assbot: Request successful, get your OTP: http://w.b-a.link/otp/7b8f9e6d5332347d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/6bbebe53765e72ab
assbot: Request successful, get your OTP: http://w.b-a.link/otp/2f19abe490e2006f
assbot: Request successful, get your OTP: http://w.b-a.link/otp/9bf5f068a67164ac
assbot: Request successful, get your OTP: http://w.b-a.link/otp/f0b05dc6d9d753ad
assbot: Request successful, get your OTP: http://w.b-a.link/otp/aa69a198c8a4975d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/10cf6aac5f28ab4a
assbot: Request successful, get your OTP: http://w.b-a.link/otp/fe5f523b72c474cf
assbot: Request successful, get your OTP: http://w.b-a.link/otp/875068be73f4e7b5
assbot: Request successful, get your OTP: http://w.b-a.link/otp/a41e9d86653f1a83
assbot: Request successful, get your OTP: http://w.b-a.link/otp/957f843dcb960bd0
assbot: Request successful, get your OTP: http://w.b-a.link/otp/78502f4b735138c3
assbot: Request successful, get your OTP: http://w.b-a.link/otp/dd3db40d4ca5a3d9
assbot: Request successful, get your OTP: http://w.b-a.link/otp/6420dbc17c2d2ea8
assbot: Request successful, get your OTP: http://w.b-a.link/otp/d0168800fd8ddd2f
assbot: Request successful, get your OTP: http://w.b-a.link/otp/4b7654c23dc1649d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/50a106d5d903481a
assbot: Request successful, get your OTP: http://w.b-a.link/otp/e640e322e22d0201
assbot: Request successful, get your OTP: http://w.b-a.link/otp/08b00c0783c0d8b4
ascii_field: so he modifies assbot so that the next time mircea_popescu is given otp token, it is actually carrying the rsa-enciphered symmetric key from $message
assbot: Request successful, get your OTP: http://w.b-a.link/otp/296b3becab046f29
assbot: Request successful, get your OTP: http://w.b-a.link/otp/4338999a2ee26579
assbot: Request successful, get your OTP: http://w.b-a.link/otp/d12edc46517d91c0
assbot: Request successful, get your OTP: http://w.b-a.link/otp/185914ec8e8cbb9d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/09ca5a90c8a1ffba
assbot: Request successful, get your OTP: http://w.b-a.link/otp/0c3e5e073ec4f06d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/8f74a0ec10668141
assbot: Request successful, get your OTP: http://w.b-a.link/otp/b93c8571f17cfee7
assbot: Request successful, get your OTP: http://w.b-a.link/otp/c95e2aa0fc9ba218
assbot: Request successful, get your OTP: http://w.b-a.link/otp/795fb07ddbaaa665
assbot: Request successful, get your OTP: http://w.b-a.link/otp/af7e9ebcf40eb27e