Need help with a virus tales-from-the-crypt 2.0 - Msieve - Page 5

wombatman · 2015-12-31, 14:30

Ok. Did YAFU find any factors before that? Also, did you follow all of the steps in the post "Teslacrypt 2.0 Factoring"? There are some more files for you to download.

wombatman · 2015-12-31, 14:33

Quote:

Originally Posted by dearnizam

Dear Wombatman,

Please help me, in getting this factors as im trying for this from last few days.

Regards
Nizam

Download the files from here: http://www.mersenneforum.org/showpos...5&postcount=16 and put them in your GGNFS directory. That should fix the error.

Quote:

Originally Posted by Andi_HB

Take a look in the sourcecode from factmsieve.py
looks like you haven`t the correct path to the binaries.
For example in line 60 you need to set the path to your ggnfs binaries.
# Set binary directory paths
GGNFS_PATH = 'D:/programme/faktorisierung/lasieve4_win/lasieve4_westmere/'
MSIEVE_PATH = 'D:/programme/faktorisierung/msieve/'

Regards Andi_HB

Based on the error he's getting, I'm pretty sure he's got it right. There was a fix to the GGNFS binaries to change how it handled some inputs that I forgot to account for.

dearnizam · 2015-12-31, 14:33

Hi Andi,

I have not used GGNFS here, i have just used YAFU

yafu-Win32.exe factor(0x113126C6F0EF0F0CB2AD384303AEAF20019E8C22C157CE5A4E27342A5C0FAED46FE21CA08BD44F7C2A829053993D5514DBE169A56F67E8D31D8D6E73BCF51608) -v -threads 4

dearnizam · 2015-12-31, 14:51

Hi Wombatman,

I downloaded the files and placed in the same directory and now ended up with different error this time.

best poly:
# norm 2.006587e-013 alpha -4.827909 e 1.523e-008 rroots 4
n: 75491079362821263423280531086082120888062596488514812641848477608194575822932
7315552787734885598979
skew: 4246594.61
c0: 3560029111473298465050250987
c1: 4780020887771603525387
c2: -2788831600012765
c3: -704706569
c4: 60
Y0: -1883420694042279440544888
Y1: 16602113381087
nfs: commencing algebraic side lattice sieving over range: 885000 - 890000
nfs: commencing algebraic side lattice sieving over range: 870000 - 875000
nfs: commencing algebraic side lattice sieving over range: 875000 - 880000
nfs: commencing algebraic side lattice sieving over range: 880000 - 885000
'..' is not recognized as an internal or external command,
operable program or batch file.
'..' is not recognized as an internal or external command,
operable program or batch file.
'..' is not recognized as an internal or external command,
operable program or batch file.
'..' is not recognized as an internal or external command,
operable program or batch file.
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
nfs: could not open output file, possibly bad path to siever
fopen error: No such file or directory
could not open rels0.dat for reading

Regards
Nizam

VictordeHolland · 2015-12-31, 16:50

How much are you guys willing to donate to a charity to get the factors of your numbers?

wombatman · 2015-12-31, 18:55

http://factordb.com/index.php?id=1100000000811434013 is fully factored.

Nizam, what does this line in yafu.ini say?

Code:

ggnfs_dir=

You need to change this line to match where you put the GGNFS executables (the ones that start "gnfs-lasieve" with different numbers at the end). If you followed the directions in my how-to post, it would have been C:\GGNFS\.

Googulator · 2015-12-31, 19:02

I'm now struggling with this key:
http://factordb.com/index.php?query=...61887858943865

That C134 appears to be a semiprime; ECM finds nothing in it. When I try to factor it with either GGNFS or YAFU, my computer spontaneously reboots after a few minutes of sieving - same computer that I previously used for successfully factoring a C154 semiprime.

EDIT: This is from an older version of TeslaCrypt, which uses only one key (no distinct Bitcoin and AES keys).

hlopezdp · 2015-12-31, 19:07

I received a computer with all the files encrypted, so I managed to search and get here.

With teslacrack I got this public keys:

Quote:

Software has encountered the following unknown AES keys, please crack them first using msieve:
02C4222BB23D858714A127034ACE67B2FA4E5A0B7ACF2B44A4DA71FA2867D5AF31C5D563D8EFC9D98C3D9FAD65D917F2179386BADAAF33BC6466FDB8B06741B3 found in ./SAM_3558.JPG.vvv
Alternatively, you can crack the following Bitcoin key(s) using msieve, and use them with TeslaDecoder:
03D8DB0E7827DD53F39B5F44C82F9E8AE08577135D7D5229D49981A487AE9D16EA6F6B7623A1073F7E667C87CF6EDCDF169B8763B9ADAF51D9CE7A4545EB7443 found in ./SAM_3558.JPG.vvv

The first one is taking a lot to being factorized. I'm using an AWS instance (8 vCPU, 15 GB RAM, 1 CUDA GPU) to do this. Just got same factors available in factordb => http://www.factordb.com/index.php?id...00000811949725

The Bitcoin key case is different, got factorized in some minutes:

Code:

***factors found***

P1 = 5
P1 = 5
P2 = 11
P2 = 41
P3 = 307
P4 = 1493
P4 = 2671
P5 = 24029
P6 = 145501
P6 = 223757
P33 = 759082218747625708092549791381327
P37 = 3927181788575019346095440315675297017
P55 = 6259126025771703397105968073316207537733930113978073731

And got the Bitcoin key with unfactor-ecdsa:

Code:

Found Bitcoin private key: 3694D0A885FD65C74FCEC6FF68F4EB12DD7A654E8896288BF76A4A00BD7BD05B

But at the moment of trying to decrypt file with TeslaDecoder, it just crashes.

Any ideas?

(Thanks to everybody !)

jux · 2015-12-31, 22:33

Completed factorization

Code:

1147138487723616055341181346721756355830271446832482652766633883866739166038021035608107590424566428820213736507301543954900859575019734082965929533843211
3*3*3*13*37*181*570613*5250935108059*14675107241209127*2436088567842429170231479196017659173606738437575383*4555916599834101604453512679670425006186389728014023751581179

http://factordb.com/index.php?id=1100000000811830938

dearnizam · 2015-12-31, 22:44

Hi Wombatman,

I have made changes as per your note and now im getting below error.

C:\GGNFS>python factmsieve.py my_number
-> ________________________________________________________________
-> | Running factmsieve.py, a Python driver for MSIEVE with GGNFS |
-> | sieving support. It is Copyright, 2010, Brian Gladman and is |
-> | a conversion of factmsieve.pl that is Copyright, 2004, Chris |
-> | Monico. Version 0.76 (Python 2.6 or later) 10th Nov 2010. |
-> |______________________________________________________________|
-> This is client 1 of 1
-> Running on 1 Core with 4 hyper-threads per Core
-> Working with NAME = my_number
-> Warning: evaluated polynomial value polyval is negative or zero.
-> This is at least a little strange.
Traceback (most recent call last):
File "factmsieve.py", line 2050, in <module>
read_parameters(fact_p, poly_p, lats_p)
File "factmsieve.py", line 1230, in read_parameters
if CHECK_POLY and polyval % fact_p['n'] != 0:
TypeError: unsupported operand type(s) for %: 'int' and 'NoneType'

my number in my_number file is "0x15E7189BDB5B01F5F481EC77738F04983F39F10C622E29B0CEA2DD6FDE451CB92044CD0964E8FF1EF07E880ECBC67365CEC8C334BB5D62E659FD663453EB270B"

wombatman · 2015-12-31, 23:05

You need to convert the hexadecimal number to a decimal number. Put

Code:

1147138487723616055341181346721756355830271446832482652766633883866739166038021035608107590424566428820213736507301543954900859575019734082965929533843211

into the my_number file instead.

2015-12-31, 18:55	#50
wombatman I moo ablest echo power! May 2013 29×61 Posts	http://factordb.com/index.php?id=1100000000811434013 is fully factored. Nizam, what does this line in yafu.ini say? Code: ggnfs_dir= You need to change this line to match where you put the GGNFS executables (the ones that start "gnfs-lasieve" with different numbers at the end). If you followed the directions in my how-to post, it would have been C:\GGNFS\.

2015-12-31, 19:02	#51
Googulator Dec 2015 2²×5 Posts	I'm now struggling with this key: http://factordb.com/index.php?query=...61887858943865 That C134 appears to be a semiprime; ECM finds nothing in it. When I try to factor it with either GGNFS or YAFU, my computer spontaneously reboots after a few minutes of sieving - same computer that I previously used for successfully factoring a C154 semiprime. EDIT: This is from an older version of TeslaCrypt, which uses only one key (no distinct Bitcoin and AES keys). Last fiddled with by Googulator on 2015-12-31 at 19:03

2015-12-31, 22:44	#54
dearnizam Dec 2015 2·5 Posts	Hi Wombatman, I have made changes as per your note and now im getting below error. C:\GGNFS>python factmsieve.py my_number -> ________________________________________________________________ -> \| Running factmsieve.py, a Python driver for MSIEVE with GGNFS \| -> \| sieving support. It is Copyright, 2010, Brian Gladman and is \| -> \| a conversion of factmsieve.pl that is Copyright, 2004, Chris \| -> \| Monico. Version 0.76 (Python 2.6 or later) 10th Nov 2010. \| -> \|______________________________________________________________\| -> This is client 1 of 1 -> Running on 1 Core with 4 hyper-threads per Core -> Working with NAME = my_number -> Warning: evaluated polynomial value polyval is negative or zero. -> This is at least a little strange. Traceback (most recent call last): File "factmsieve.py", line 2050, in <module> read_parameters(fact_p, poly_p, lats_p) File "factmsieve.py", line 1230, in read_parameters if CHECK_POLY and polyval % fact_p['n'] != 0: TypeError: unsupported operand type(s) for %: 'int' and 'NoneType' my number in my_number file is "0x15E7189BDB5B01F5F481EC77738F04983F39F10C622E29B0CEA2DD6FDE451CB92044CD0964E8FF1EF07E880ECBC67365CEC8C334BB5D62E659FD663453EB270B" Last fiddled with by dearnizam on 2015-12-31 at 22:45

2015-12-31, 23:05	#55
wombatman I moo ablest echo power! May 2013 29×61 Posts	You need to convert the hexadecimal number to a decimal number. Put Code: 1147138487723616055341181346721756355830271446832482652766633883866739166038021035608107590424566428820213736507301543954900859575019734082965929533843211 into the my_number file instead.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Using msieve with c	burrobert	Msieve	9	2012-10-26 22:46
Yes: Tales from Typographic Oceans	xilman	Lounge	79	2012-05-26 23:53
msieve help	em99010pepe	Msieve	23	2009-09-27 16:13
95% sure I have a virus, please help	jasong	Hardware	8	2006-11-19 22:57
virus hardware damage?	TTn	Hardware	18	2006-11-04 09:41

2015-12-31, 14:30	#45
wombatman I moo ablest echo power! May 2013 6E9₁₆ Posts	Ok. Did YAFU find any factors before that? Also, did you follow all of the steps in the post "Teslacrypt 2.0 Factoring"? There are some more files for you to download.

2015-12-31, 14:33	#47
dearnizam Dec 2015 2·5 Posts	Hi Andi, I have not used GGNFS here, i have just used YAFU yafu-Win32.exe factor(0x113126C6F0EF0F0CB2AD384303AEAF20019E8C22C157CE5A4E27342A5C0FAED46FE21CA08BD44F7C2A829053993D5514DBE169A56F67E8D31D8D6E73BCF51608) -v -threads 4

2015-12-31, 14:51	#48
dearnizam Dec 2015 2×5 Posts	Hi Wombatman, I downloaded the files and placed in the same directory and now ended up with different error this time. best poly: # norm 2.006587e-013 alpha -4.827909 e 1.523e-008 rroots 4 n: 75491079362821263423280531086082120888062596488514812641848477608194575822932 7315552787734885598979 skew: 4246594.61 c0: 3560029111473298465050250987 c1: 4780020887771603525387 c2: -2788831600012765 c3: -704706569 c4: 60 Y0: -1883420694042279440544888 Y1: 16602113381087 nfs: commencing algebraic side lattice sieving over range: 885000 - 890000 nfs: commencing algebraic side lattice sieving over range: 870000 - 875000 nfs: commencing algebraic side lattice sieving over range: 875000 - 880000 nfs: commencing algebraic side lattice sieving over range: 880000 - 885000 '..' is not recognized as an internal or external command, operable program or batch file. '..' is not recognized as an internal or external command, operable program or batch file. '..' is not recognized as an internal or external command, operable program or batch file. '..' is not recognized as an internal or external command, operable program or batch file. nfs: could not open output file, possibly bad path to siever nfs: could not open output file, possibly bad path to siever nfs: could not open output file, possibly bad path to siever nfs: could not open output file, possibly bad path to siever fopen error: No such file or directory could not open rels0.dat for reading Regards Nizam

2015-12-31, 16:50	#49
VictordeHolland "Victor de Hollander" Aug 2011 the Netherlands 2³·3·7² Posts	How much are you guys willing to donate to a charity to get the factors of your numbers?