600+ entries in 0.079s
mircea_popescu: which makes me believe republican format
otp should actually come as xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx [yyyy] blocks
mircea_popescu: a very useful tool for dropping the workload from ~50 minutes to ~30 minutes /
otp is s/\n/" | sha512sum | cut -c1-2 >> hurr.txt \necho "/ and then comparing the line crcs.
a111: Logged on 2019-05-22 14:05 stjohn_piano_2: 3) there may be an approach to signed comments that does not involve the primary key: examples: a) sign with a subordinate key b) validate your current IP for a time period (e.g. a month / year) by decrypting an
OTP, like deedbot.
stjohn_piano_2: 3) there may be an approach to signed comments that does not involve the primary key: examples: a) sign with a subordinate key b) validate your current IP for a time period (e.g. a month / year) by decrypting an
OTP, like deedbot.
☟︎ a111: Logged on 2019-05-22 12:51 diana_coman: stjohn_piano_2: re ^ , an
OTP challenge is a way to check one's identity; hence, deedbot will not send an
OTP in response to !!register but WILL send an
OTP in response to ~any other command (technically to any command that is a request of *someone* i.e. that requires an identity)
diana_coman: stjohn_piano_2: re ^ , an
OTP challenge is a way to check one's identity; hence, deedbot will not send an
OTP in response to !!register but WILL send an
OTP in response to ~any other command (technically to any command that is a request of *someone* i.e. that requires an identity)
☟︎ a111: Logged on 2019-05-16 17:11 stjohn_piano_2: asciilifeform: gpg --list-packets shows that the key ID is C8EFFF13 in the
OTP file. The key ID of my public key is 5991 52AC. Is this expected? (the fingerprint shown by deedbot in the earlier line is correct, though).
a111: Logged on 2019-05-16 20:10 stjohn_piano_2: by mistake, i was attempting to decrypt the
OTP sent to asciilifeform
stjohn_piano_2: ^ trinque. hope you see the above about
OTP before doing any investigation.
diana_coman: heh, as I was reading the log, I was wondering if you were trying there the right
OTP or someone else's
stjohn_piano_2: in my notes, i had this sequence: 1) join forum, 2) deedbot will present
OTP, 3) decrypt
OTP, 4) use !!v
OTP.
stjohn_piano_2: by mistake, i was attempting to decrypt the
OTP sent to asciilifeform
☟︎ stjohn_piano_2: strange. doing the operation again with the original
OTP still produces the error.
stjohn_piano_2: puzzler: why the key ID in the
otp message is C8EFFF13, while my key's fingerprint is 599152AC. importing the private key into gpg produces (in gpg --list-keys) the correct key ID 599152AC. diffing the key returned by deedbot with my public key shows no difference.
stjohn_piano_2: asciilifeform: gpg --list-packets shows that the key ID is C8EFFF13 in the
OTP file. The key ID of my public key is 5991 52AC. Is this expected? (the fingerprint shown by deedbot in the earlier line is correct, though).
☟︎ stjohn_piano_2: i had some prepared commands, but i'm having some trouble decrypting the
otp.
mircea_popescu: and incidentally, trinque 's
otp way the fuck smarter than gpg's ascii armor format, slavegirl reports. degree of magnitude faster wetware diode if one needn't handle the shift.
a111: Logged on 2018-08-04 22:05 asciilifeform: ben_vulpes: iirc i proposed at one time an intermediate item on the way to proper gossipd ( 'serpent'-ciphered tunneler to connect coupla ircd instances to each other, and ditto for users ( get
otp cookie a la deedbot, get a key that's good for 1 tcp connect ) but so far instead followed mircea_popescu's advice re not wasting sweat on such a thing, but pushing with ffa so as to get with what to gossipd.