mersenneforum.org Independent factorization of large numbers
 Register FAQ Search Today's Posts Mark Forums Read

2022-01-30, 03:20   #45
LaurV
Romulan Interpreter

"name field"
Jun 2011
Thailand

236228 Posts

Quote:
 Originally Posted by frmky I don't understand all of this interest in the number. Lessiv has clearly stated that they do not wish to reveal the number. They did the work to factor it themselves. They owe us no explanation, and we as a community should respect their wishes.
+1.
Well said. I can imagine a hundred reasons why the number be not said in public, and yet be nothing illegal. To avoid any arguments, the OP could just generate a rsa(154) with yafu, which has a function to do exactly that, and post it here, letting the others to scratch their head. However he was honest and said he can't disclose it.

End of story. Let it go.

 2022-04-24, 07:19 #46 Lessiv   Jan 2022 1316 Posts Good afternoon dear experts! Need help again. Asked me to factorize another number, the search ended and the processing began and at that moment I turned off the computer (computer overheating). If I run the "Factmsieve.py example" command, data processing no longer happens. What kind of team I need to write to continue the processing process "spairs.save.gz"?
 2022-04-24, 13:57 #47 VBCurtis     "Curtis" Feb 2005 Riverside, CA 172×19 Posts If you barely started the job when you turned off the computer, best to just start the job over anew. Erase the work-in-progress files and fire up factmsieve.
2022-04-24, 15:06   #48
Lessiv

Jan 2022

1316 Posts

Quote:
 Originally Posted by VBCurtis If you barely started the job when you turned off the computer, best to just start the job over anew. Erase the work-in-progress files and fire up factmsieve.
The final stage has already begun, after a week of searching, and 100% of the numbers have already been processed. And the process began:
Sun Apr 24 09:07:16 2022 commencing linear algebra
Sun Apr 24 09:07:16 2022 read 4098748 cycles
Sun Apr 24 09:07:20 2022 cycles contain 11569154 unique relations
Sun Apr 24 09:07:55 2022 read 11569154 relations
Sun Apr 24 09:08:05 2022 using 20 quadratic characters above 4294917295
Sun Apr 24 09:08:45 2022 building initial matrix
Sun Apr 24 09:10:03 2022 memory use: 1590.2 MB
Sun Apr 24 09:10:06 2022 read 4098748 cycles
Sun Apr 24 09:10:07 2022 matrix is ​​4098569 x 4098748 (1241.2 MB) with weight 390701857 (95.32/col)
Sun Apr 24 09:10:07 2022 sparse part has weight 276196077 (67.39/col)
Sun Apr 24 09:10:25 2022 filtering completed in 2 passes
Sun Apr 24 09:10:26 2022 matrix is ​​4097843 x 4098022 (1241.2 MB) with weight 390677271 (95.33/col)
Sun Apr 24 09:10:26 2022 sparse part has weight 276190614 (67.40/col)
Sun Apr 24 09:10:32 2022 matrix starts at (0, 0)
Sun Apr 24 09:10:33 2022 matrix is ​​4097843 x 4098022 (1241.2 MB) with weight 390677271 (95.33/col)
Sun Apr 24 09:10:33 2022 sparse part has weight 276190614 (67.40/col)
Sun Apr 24 09:10:33 2022 saving the first 48 matrix rows for later
Sun Apr 24 09:10:33 2022 matrix includes 64 packed rows
Sun Apr 24 09:10:34 2022 matrix is ​​4097795 x 4098022 (1199.3 MB) with weight 311380058 (75.98/col)
Sun Apr 24 09:10:34 2022 sparse part has weight 273415510 (66.72/col)
Sun Apr 24 09:10:34 2022 using block size 8192 and superblock size 1572864 for processor cache size 16384 kB
Sun Apr 24 09:10:45 2022 commencing Lanczos iteration (16 threads)
Sun Apr 24 09:10:45 2022 memory use: 963.3 MB
Sun Apr 24 09:10:49 2022 linear algebra at 0.0%, ETA 3h 0m

And at that moment my computer turned off.

 2022-04-24, 15:17 #49 Lessiv   Jan 2022 100112 Posts When re-running "factmsieve.py example" I am getting the following message: See attached screenshot. Attached Thumbnails
 2022-04-24, 15:46 #50 chris2be8     Sep 2009 45308 Posts It looks as if you had just finished sieving and started LA (linear algebra) when the system overheated. So you are most of the way there. I suggest: 1: Back up everything in the working folder, preferably to another computer. Or to another folder if you can't do that. 2: Check why the computer overheated. Try blowing dust and fluff out of it. Check for stuck or faulty fans, fix or replace them if so. And make sure it was heat, not running out of memory that caused the crash. 3: Try to restart the job. You may need to run msieve outside the script, passing it -ncr -nc3 as extra parameters. Run msieve -h to get a list of parameters msieve will accept. And possibly reducing the number of threads to stop the computer getting so hot. 4: If you are stuck post output from dir in the working folder. I don't use factmsieve.py myself, or Windows (I use factMsieve.pl on Linux) so I can't be more specific. Last fiddled with by chris2be8 on 2022-04-24 at 15:50
 2022-04-24, 16:51 #52 Lessiv   Jan 2022 19 Posts The question is: how to properly unpack the "spairs.save.gz" archive so that later you can run "msieve" with the necessary parameters? And how is the "example.dat" file created?
 2022-04-24, 18:14 #53 frmky     Jul 2003 So Cal 1001101100102 Posts Make sure you have everything backed up elsewhere first. spairs.save.gz should be just a gzipped copy of example.dat. You can just leave it compressed and copy it to msieve.dat.gz and it should work. Since you are replacing the dat file, I would restart with filtering. With msieve, msieve.dat.gz, example.ini, and example.fb in the same directory, Code: msieve -i example.ini -nf example.fb -nc1 -nc2 -nc3 -t 16 -v
2022-04-25, 08:28   #54
Lessiv

Jan 2022

19 Posts

Quote:
 Originally Posted by frmky Make sure you have everything backed up elsewhere first. spairs.save.gz should be just a gzipped copy of example.dat. You can just leave it compressed and copy it to msieve.dat.gz and it should work. Since you are replacing the dat file, I would restart with filtering. With msieve, msieve.dat.gz, example.ini, and example.fb in the same directory, Code: msieve -i example.ini -nf example.fb -nc1 -nc2 -nc3 -t 16 -v
Many thanks!
Everything worked out.

 2022-04-25, 12:28 #55 orever   Oct 2019 5 Posts On this github there is code that says it factors in a matter of hours. A number of 512-bit RSA keys. https://github.com/eniac/faas And so, anyone can factor a 512 very quickly. If you use this number for business, you better rethink. And he didn't even need to prove it was a vulnerability. "Since 2015, NIST has recommended a minimum of 2048-bit keys for RSA,[14] an update to the widely accepted recommendation of a minimum of 1024 bits since at least 2002.[15]" So if they changed it to a number of 1024, a number of 2048 is better. https://en.wikipedia.org/wiki/Key_size

 Similar Threads Thread Thread Starter Forum Replies Last Post jpcu1237 Tales From the Crypt(o) 18 2020-07-16 22:23 CRGreathouse Factoring 55 2014-04-11 15:05 HellGauss Math 5 2012-04-12 14:01 ET_ Factoring 15 2008-03-12 21:24 Bundu Software 5 2004-08-26 01:56

All times are UTC. The time now is 11:26.

Wed Oct 5 11:26:12 UTC 2022 up 48 days, 8:54, 0 users, load averages: 0.91, 0.96, 1.00