> Albert, > 33 minutes to compute the key??? Show me the code. I think > there may be > other issues.
Hay Tony In a separte mail I will send te code. Probally its less ten optimal But nut a lot! The crypto code is that of openssl. (which I asumme isn't that bad). The same programe (even without a recompile) works very wel on a modern system (AMD Duron(tm) Processor (952.16-MHz 686-class CPU) with 256M RAM). There it takes 1 to 4 second to compute the key. And only 3 milli second to compute (or verify) the signature. The 33 minutes was on my 386 CPU with 40Mhz and only 16Mbyte RAM. It also was the but 1 slowest run. Which occuers when I was also ssh-2 connected. I have done 10 more runs. With execution times between 9 and 44 minites. And an avagare of 20 minutes. Probally the code is less then optimal. But there is a huge performance differance between those 2 systems! On a modern system: 3 second on avarage. On a old/small system never better the 9 minutes. This is a gap of 177 times! Which, I asume will not change with better code!. But I will send the code --ALbert sent mail to [EMAIL PROTECTED], to address me personal. sent mail to [EMAIL PROTECTED], to address me for businesses
