1800+ entries in 0.384s
PeterL: would be better than just reusing the one
otp over a bunch of times?
mircea_popescu: basic cryptoquestion i do not expect an answer to : is there a way to evaluate strength loss by hash pass in a scheme where
otp is hashed and the hash used as next pass
otp, for N passes of this ?
mircea_popescu: currently the "what happens past key generation" and "there's an
otp" part is left pretty loophole-y
a111: Logged on 2016-07-17 22:00 mircea_popescu: it is not clear that
otp actually works ; it is almost certain nothing else in the "pfs" gargle does.
mircea_popescu: it is not clear that
otp actually works ; it is almost certain nothing else in the "pfs" gargle does.
☟︎ trinque: I crap out an encrypted
OTP mircea_popescu: at the USER end. if you want to
otp the stuff you put through cs/rsa, by all means.
mircea_popescu: asciilifeform the problems with
otp aren't exactly bandwidth like that.
trinque: obviously using the cramer shoup link is higher risk than the
otp one
trinque: what does me moving a cramer shoup key over an
otp link reveal about the
otp link
trinque: asciilifeform: not really. if you wanted to move more data, could exchange pubkeys over the
otp link.
vc: how do I do this fancy
OTP thing
davout: also looks like there's an extra white space at the end of the GPG decrypted
OTP davout: trinque: looks like deedbot still chokes on trailing whitespace when $v'ing one's
otp mircea_popescu: but anyway - you can self-voice for an indefinite period by pm-ing deedbot $up and then $v the
otp it gives you
ben_vulpes: shat out an
otp, successful decryption of which set a session on the user's browser.
davout: ;;later tell trinque deedbot still chokes on trailing whitespace in OTPs, and from what i see the
OTP comes with this trailing space when decrypted