NODE 24ca5017Re: SSL CHALLENGE: ALERT! probable misallocation of keys?
aba@dcs.exeter.ac.ukThu, 24 Aug 95 14:14:54 PDT
Peter Trei <trei@process.com> writes on cpunks:
> My suspicion - and let me apologize in advance if I'm wrong - is
> that Mr. Thomas thinks he's allocated himself 50,000 keys, whereas
> he's actually got 838,860,800,000.
A quite plausible theory, hadn't thought of that.
> You've reserved 3/4 of the keyspace, and you're going to screw up the
> search unless you have an NSA-sized data center.
>
> I suggest we assume this is an error, and remove the block from the
> reserved list so that it can be re-allocated.
Piete's server is more reslient than that!
What happens is that when it reaches FFFF, it'll start doling out yet
unacked keys on the assumption that they were mistakes, or that they
were slow machines, or WWW doled ones which the user forgot to ack.
This is better for speed reasons also, as it means everybody gets
something to do right up to the end, there'll be a mad scrabble at the
end where multiple people are working on the same keyspace, as it
wraps around the remaining unacked bits of key, but the 1st person to
ack gets credited for it, and that way it gets done as quickly as
possible.
Adam
NODE f4071eb3Re: SSL CHALLENGE: ALERT! probable misallocation of keys?
Jyri Kaljundi <jk@digit.ee>Thu, 24 Aug 95 14:43:54 PDT
On Thu, 24 Aug 1995 aba@atlas.ex.ac.uk wrote:
> What happens is that when it reaches FFFF, it'll start doling out yet
> unacked keys on the assumption that they were mistakes, or that they
> were slow machines, or WWW doled ones which the user forgot to ack.
Just a dumb question: when brutessl-brclient-brloop will find the key,
will it report it to the keyserver right away? What I mean is can I just
start the brloops on my machines and log out, and not have to look at the
display all the time?
BTW how can I log brloop's output into a file and not to the screen?
Juri
<o Jri Kaljundi e-mail: jk@digit.ee o<
>o tel: +372 6308994 o>
<o DigiTurg http://www.digit.ee/ o<
NODE 53aa407bRe: SSL CHALLENGE: ALERT! probable misallocation of keys?
Piete Brooks <Piete.Brooks@cl.cam.ac.uk>Thu, 24 Aug 95 15:11:49 PDT
> Just a dumb question: when brutessl-brclient-brloop will find the key,
> will it report it to the keyserver right away?
IF it manages to get a word in edgeways, yes.
However, I fear some ACKS are being lost :-(
> What I mean is can I just start the brloops on my machines and log out,
> and not have to look at the display all the time?
Indeed -- it's meant to run unattended.
HOWEVER, due to the problems with loosing ACKs, it would be useful to send
the output to a log file, and then check that all the scanned segments made it
to the server [[ NB: stats updates are currently manual !! ]]
> BTW how can I log brloop's output into a file and not to the screen?
sh: brloop >> logfile 2>&1 &
csh brloop >>& logfile & (I think)
Aliter: "nohup brloop &" might do it
NODE 492eb7d3Re: SSL CHALLENGE: ALERT! probable misallocation of keys?
Christian Wettergren <cwe@Csli.Stanford.EDU>Thu, 24 Aug 95 15:16:45 PDT
| BTW how can I log brloop's output into a file and not to the screen?
#!/bin/sh
brloop > /tmp/worklog.ssl 2>&1 &
is what I did.
/Christian