[Etoys] Key generation

[Scott Wallace]

Whatever else we do about this, that progress-bar which reports  
runaway figures such as "580% completed" has to be tamed; even it we  
retain its nowadays-faulty heuristic for estimating how long the key- 
generation *should* take, we obviously need to cap the completion  
percentage we report at 99%...  (I'll do that.)

Anyway... it appears that disabling the #automaticKeyGeneration  
preference keeps the key-generation from happening at start-up, yet  
still allows publishing and loading projects, and still uses MySqueak  
as the default directory.  Maybe that's all that's needed.

Or perhaps, for this build, would it make sense simply to include a  
pre-built squeak.keys file alongside the image, and not otherwise  
tamper with the security settings?

Cheers,

   -- Scott


On Oct 19, 2006, at 9:02 AM, Yoshiki Ohshima wrote:

>   Bert,
>
>> I'm not sure if project saving will break. Can someone try, and
>> publish a CS turning of the pref if it works?
>
>   I don't mind to take on this, but Scott, what do you think?
>
> -- Yoshiki
>

> We certainly don't need the key for this build ...
>
> Cheers,
>
> Alan
>
>
> 	From: 	  bert at freudenbergs.de
> 	Subject: 	Re: [Etoys] Key generation
> 	Date: 	October 19, 2006 6:54:39 AM PDT
> 	To: 	  etoys at laptop.org
>
>
> At 06:13 AM 10/19/2006, Bert Freudenberg wrote:
>
>> When starting etoys for the very first time, a crypto key is
>> generated. This takes about a minute on the laptop. It's
>> particularily frustrating because the counter does not stop at 100%
>> but goes well beyond, everyone would think it does not finish at all.
>>
>> Could we postpone key generation to the time it is actually needed,
>> rather than first start? I guess the reason to do it this way is
>> because of the sandbox? Can we do something to avoid that delay? Do
>> we need the key at all?
>>
>> - Bert -
>>
>> _______________________________________________
>> Etoys mailing list