Yafu

[bchaffin]

Originally Posted by bsquared

1.20.1 is linked with GMP-ECM 6.3, which itself was built with GMP-5.0.1. 1.20 on the other hand was built with GMP-ECM 6.2.3 and GMP-4.2.3. That's the only difference I can see. Both yafu versions were statically linked to libecm.a. All of the above were built on a RH Enterprise Linux 5 box with gcc version 4.1.2.

[edit]
I see that there are different versions of libgmp.so.*, which appear in the gmp/lib/ folder, between the different versions of GMP. So even though libecm is linked statically to yafu, the libecm library in turn probably depends on different dynamic libgmp libraries. I could provide you with the GMP-5.0.1 libgmp.so.10 and libgmp.so.10.0.1 files if you like.

Thanks. I've already built gmp 5.0.1, it's just not what's installed on my system (which I don't administrate). After a little googling I found the patchelf utility and managed to hack the binary to look in the right place so I don't have to muck with the lib paths in a zillion shells.

In other words, problem solved. :)

[bsquared]

Originally Posted by bchaffin

In other words, problem solved. :)

Great! Glad I could help

[bsquared]

bchaffin kindly pointed out a bug in version 1.20.1. For some reason, I commented out a block of code which I shouldn't have sometime between version 1.20 and 1.20.1. I can't for the life of me remember what I was doing. The fix is available here.

Sorry for the inconvenience.

[bsquared]

Originally Posted by Tyra

Advice please! Which startup options YAFU?
C155
how to use multiCPU?
Turn off the electricity. How to resume work from Stop?
THANK YOU.

The only thing YAFU could be useful for on a C155 is for running ECM. Running the following command will cause YAFU to start running auto-increasing curves indefinitely:

yafu "factor(c155)"

But that's unlikely to be helpful for your (probable) RSA-512 key. Instead, start here.

[Brian Gladman]

Ben, I wonder if you realise that the YAFU source code you are publishing still contains bugs that I reported some weeks ago?

Brian

[bsquared]

Originally Posted by Brian Gladman

Ben, I wonder if you realise that the YAFU source code you are publishing still contains bugs that I reported some weeks ago?

Brian

Can you remind me what bugs you reported? I haven't updated the public source code since the full 1.20 release, which was several weeks ago, but I want to be sure I'm addressing everything. Stuff tends to pile up.

[jasonp]

Maybe a project on sourceforge or Google code would make it easier to keep up with the user community? (Brian can then make the changes himself :)

[bsquared]

That's a great idea. Is it hard to get everything set up on sourceforge?

[Brian Gladman]

Hi Ben,

I don't remember exactly when, but I provided a revised version of ecm.c to solve x64 exceptions that were being reported here.

Brian

[bsquared]

Originally Posted by Brian Gladman

Hi Ben,

I don't remember exactly when, but I provided a revised version of ecm.c to solve x64 exceptions that were being reported here.

Brian

Ok, that's what I thought you might be referring to. Version 1.20.1 (and .2) both use a revised ecm.c. After reviewing your revisions I implemented a threadpool threading architecture for ecm, similar to siqs and the sieve of Eratosthenes code in YAFU. The x64 ecm crashes are fixed in the .1 and .2 versions with these changes, but I haven't released the source code yet.

[Brian Gladman]

Ah, I now understand. But does this mean that the binaries packaged as a part of the YAFU 1.20.1 distribution don't correspond with the source code that is in this package?

Brian