Discussion related to cado-nfs

[Emmanuel Thomé <Emmanuel.Thome@inria.fr>]

Hi,

Thanks for your report.

cado-nfs uses by an RSA key for the server, so that the clients can
authenticate the commands that the servers asks them to run.  (even if
you don't explicitly run a client-server computation, this is how it runs
in all cases).

cado-nfs-2.3.0 used 1024-bit keys. This setting has changed to 2048-bit
keys in the master branch.

I suppose that your SSL library does not allow 1024-bit keys. (which is a
good policy, IMHO).

To fix this on 2.3.0, you could try to change the "bits=1024" line in
scripts/cadofactor/wuserver.py, around line 825, and see if things work
better.

> I've also tried the version "cado-nfs-master" from https://gitlab.inria.fr/.
> So far it works fine, but I notice that someone is still working on it. So
> I wonder whether it's fine to use this version, or it may probably go wrong.

Yes, please use cado-nfs master branch. Not only does it fix your
problem, but it's also a lot more efficient in many aspects. Sure, it's a
development branch, so it breaks every once in a while (normally not too
often, since the stuff that really breaks things goes in merge requests
first).

Best regards,

E.

On Thu, Sep 23, 2021 at 12:12:55AM +0800, Xiangru Zhong wrote:
> I tried to install cado-nfs-2.3.0 on the wsl on my computer. Currently I am
> using an Ubuntu 20.04.3. It was compiled successfully, but when I tried
> running a factorization, it didn't work and kept showing the information:
> "Critical:HTTP server: Socket error while setting up server on None:0 :
> [SSL: EE_KEY_TOO_SMALL] ee key too small (_ssl.c:4046)".
> It will be very helpful if there's any solution to this problem.
> 
> P.S.
> I've also tried the version "cado-nfs-master" from https://gitlab.inria.fr/.
> So far it works fine, but I notice that someone is still working on it. So
> I wonder whether it's fine to use this version, or it may probably go wrong.