@tylerl ... I'm torn on whether I agree with your last two sentences - I agree they should be able to disable it, but I'm kind of more comfortable with people being dos'd out of their systems than it being easy to bruteforce the systems by default. Trusting people to pick a good password for cpanel isn't something I'm super comfortable about
@TerryChia oh - I knew I was just reading the OTP stuff from above (about whether OTP can be used large scale) and as edge case was wondering whether you can actually keep OTP 'going' after some initial state is securely established. Punchline turned out not to be surprising
so both parties end up with a 'new' pad of the reminaining length... actually no nevermind. This one never works since if your new pad being transmitted is intercepted its moot.
ok so yes, as I poposed the question it looks very unlikely. I won't edit the question to be asking it slightly differently, but can it be used to 'update' one-time pads? Say (for some silly reason) you believe you've leaked a copy of your onetime pads, can you use a chunk (say a few hundred bytes) to tell the other party that the remaining amount of pad left after that you're going to use to transmit a new pad, in an attempt to 'close' the leak if you think you're not being intercepted yet?
little far for me to try and reach by radio, without getting lucky on rare phenomenon. I'm probably a lot closer to MH370, unless it turns out to be in Afghanistan again
interesting. I would guess it's a lack of advertising really... you need a certain critical mass to retain users because there's activity, and if you don't get that critical mass because people are on existing arms forums and don't know about SE...
