![]() |
|
|
#1 |
|
Jun 2003
22×61 Posts |
Hey, why not try factoring RSA576. Its only 174 digits :). And theres a 10,000 prize.
|
|
|
|
|
#2 | |
|
Aug 2002
2×101 Posts |
Quote:
|
|
|
|
|
|
#3 | |
|
Aug 2002
5008 Posts |
Quote:
|
|
|
|
|
|
#4 |
|
Jun 2003
22·61 Posts |
exactly what im saying. the current number being factored is about 227 digits. it would be pretty cool to factor an RSA number :)
|
|
|
|
|
#5 |
|
Jun 2003
The Texas Hill Country
44116 Posts |
Sorry to "rain on the parade" but it isn't that easy.....
First you need to understand more about how the NFS method works. We select two polynomials that are related to the number which we are attempting to factor. The sieving phase examines the norm of these polynomials at very many points and collects the "smooth" ones. The simpler the polynomial, the higher the density of acceptable points. We can split the numbers to be factored into two broad groups. First, there are the cofactors which come from "simple" polynomials. For example, the M713 can be expressed as N|(2^713-1) or N|(2^714-2). The latter expression can be re-expressed as (2^119)^6 -2. Thus, we will use the polynomials X^6-2 and Y-2^119. Note that the complexity is about 215 digits (2^714) even though we already know some of the factors and are trying to factor a number that is only 171 digits. This approach is known as Simple NFS. (SNFS) Many numbers cannot be represented by such simple polynomials. For these, we search for a pair of polynomials. The resulting polynomials have large coefficients and therefore have a much lower density of acceptable points. This approach is called the General NFS (GNFS). RSA576 was particularly chosen to be difficult. As you note, it is 174 digits. But since it requires the GNFS, it is as hard as perhaps a 260 digit SNFS number. (I may be off a bit. I'm sure Paul will correct me). Now, the effort to sieve is exponential in the size. RSA576 is perhaps 50 times as difficult as M713. It might take our present pool a couple years to do the sieving. There are additional problems. We are already pushing the limits of 32 bit numbers. The solution of RSA576 will likely require 64 bit machines or many more 32 bit machines to compensate for the lost efficiency in handling the larger numbers. So, the bottom line is that we will not be doing RSA576 any time soon because it is much harder than the numbers that we can presently handle. I'll also comment on the prize money. In my opinion, this is a disincentive. If we won such a prize, what would we do with it? Should we spread it according to effort? A dollar here and ten there would be both unworkable and insignificant. Perhaps we could give it to the largest contributor. Would $10k really mean much to MSFT? Or you could give it to me. :) But that is hardly fair. A charity perhaps... But which one? It's much easier to divide up $0.00. We don't have to discuss it and generate hard feelings. Everyone gets their fair share. |
|
|
|
|
#6 | |
|
Aug 2002
26×5 Posts |
I've actually been studying the NFS for a while, but I never stopped to compute the speed difference between the special and general variant. I didn't realize the special had such a speed up.
This brings me to a question I've been thinking about for a while. Now, it's known that good polynomials can drastically cut-down on the effort spent sieving. Has anyone ever considered distributing the polynomial search phase as well? Different systems can generate different polynomials according to certain rules and give them a "test run" to try out their efficiency. The systems could send the results back to the central server, which would keep track of the most efficient polynomial currently found. It seems to me that a day or two of many computers searching for polynomials would uncover a better one than maybe one or two computers looking for a week. Quote:
|
|
|
|
|
|
#7 | ||||
|
Jun 2003
The Texas Hill Country
32·112 Posts |
Quote:
Quote:
Quote:
|
||||
|
|
|
|
#8 | |
|
Aug 2002
2·101 Posts |
Quote:
Everybody reinvents the wheel when a new DC project gets started. I'd like to see a repository of techniques and methods common to DC projects that could be drawn on by new DC projects. Perhaps a way of sponsoring the server needs of qualifying projects. There's lots of volunteer time floating around, but some resources have to be paid for, especially disk space and bandwidth. I don't think that BOINC or Adam Beberg's V3, or even the DC framework that Scott is working on are going to be a one size fits all answer. That much became obvious to me when I was asked to see if distributed.net could help out with GIMPS. The distributed computing model they used (including V3) didn't account for long running WU that needed status updates without returning results. Nor did they account for the amount of participant freedom that GIMPS runs with. We don't know what kinds of needs future projects will have in terms of technical, political, and operational constraints, both on the client end and server end, so it makes more sense to build a toolbox than a framework. There are also projects that founder only for lack of a server and bandwidth. Resources permitting, it would a good thing to be able to help defray costs for good projects in an organized way. In this way, the prizes could be used to benefit distributed computing as a whole, rather than one particular project that happened to have prize money attached to it. And it removes the prize money as a source of contention. This is rather a more Loungish topic, so if it goes any further, I'd suggest a new thread there. |
|
|
|
|
|
#9 |
|
Mar 2003
32 Posts |
NFS? This is quite funny.
Be a number engineer and find something even further. A even smaller than exponential time series. That's the new age of the encryption factorization challenges. |
|
|
|
|
#10 | ||
|
∂2ω=0
Sep 2002
República de California
103·113 Posts |
Quote:
----------------- [code:1]Another question about SNFS polynomials, which seems especially relevant to the case where the input number has no obvious special form, but is too large for GNFS. (Another example I have in mind is the case where we are factoring a number which *does* have a nice form for SNFS, but which in its raw form is too large for SNFS, and where we have a fairly deep partial factorization, which leaves a cofactor N of feasible size for SNFS but no longer of nice algebraic form, and also too large for GNFS.) Is it feasible to search numerically for some integer X which allows N to be expressed as a polynomial in X of convenient order for SNFS, and with decently small coefficients? For instance, I notice that the C135 cofactor I want to factor (and there the full number is small enough for SNFS, but just by way of example), N = 570262229321929824871858839122891676716126463565895757793607870653597282165957653592803888395593959868233879964970398426621091298635839 has a sixth root that is quite close to integral: N^(1/6) = 28796901966283355693382.98849... Now if I set r=28796901966283355693383, I have N = r^6 - 1362344705796597183482725783805680802732323062427951798203963215024480705425407051176442282546965559515123838930 . The zeroth-order coefficient is still fairly unwieldy, but it is significantly smaller than N, and of course I didn't search very hard. It seems for a given polynomial order O, as O increases there should be a large number of Oth-order polys which = N and have coefficients less than some desired bound, e.g. N^(1/O), of which we only need to find one. If I continue the above brute-force approach, I can write N = r^6 - 1981088772476547848802*r^4 + 5990531477601275988384*r^3 + 11422764268863511805333*r^2 - 8401591645029116675071*r - 4118215695723934696540 . But I'm fairly sure if it were that easy, it would've been done already. Is the problem that coefficients of the same order as N^(1/O) are still much too large for SNFS? -Ernst[/code:1] Quote:
|
||
|
|
|
|
#11 | |
|
Jun 2003
26 Posts |
Quote:
|
|
|
|