spektormax

Moonlit: You think I'm trusting a link from you? Forget it.

hey guys really apolise about that link being down, when I moved servers I ddint move it with me, its up same like... yeh again sorry about thats thanks to who ever sent me a myspace maessage I couldnt reply cuz for soem off reason I was having issues

the mailpass does

I wrote the ICBM long time ago that srpeads stick to stick to stick bu it wasnt reslised fo fear of use by bot heares

I have seen issues with SATA at school, what linux distro are you using?

you could use a bubble sort to get minnimum, although its very inificent

1 word darren, TOR

sorry about my spelling, yeh thats why anyone that knows me from IRC more personaly knows that I like to skype people instead becasue then I can make alot more sence, as for DES and NTLM, DES IS the base for LM, the upercase portion is LM, as for NTML, version 1 the LM is DES version 2 theres no DES part, the password is stored as MD4, and then HMAC MD5ed with nt time and other stuff (its not fully documented but has been reverse engineered). As for c95c101901924a7e55bb6c68e77b2147 if that is a hash from 1 512 block, then you can possibly assume a A-Za-z0-9 character set and a length of less than or equal to 14, if thats an MD5 of more than one block that was xored, then you cannot asume anything, so since I have no sentex to that hash, the speed increse doesn't exist. Note that any hash function that uses non semi-random padding has these problems, that means that so does MD4, I don't know the MD2 or RIPMD-160 algarithums off the top of my head.

spektormax payload with private ICBM mod

ok. first of all specs back in the house... so heres my idea, for those of you that don't know the MD5 algarithum front and back go to wikipedia, theres a great aretical, alternitavly you could go look at the rfc for MD5 but its not pritty AT ALL. So, those of you that are well firmiluare with MD5, you know that esencialy you are reducing a 512 bit (well 448) block to a 128 bit block thru 4 rounds of 16. In the MD5 algarithum you take the password and cut it up into 512 bit chuncks. THen, add a 1 and pad with NULLS till the length is 448%512. THen you add a 64-bit big edine to the end of the Block. Then you break it up into 16 32-bit little eddines. You then perform functions f,g,h, and i on ABCD and then rotate.(im over simplifing it but if you know what im talking about this is enough). Now, the MD5 algarithum was invented for more of an integready check algarithum for large files (greater than 1 MEG) that have alot of Blocks. Now the problem is that if you just do 512bit to 128 bit (forget about all the padding), thats a 4-1 reduction. Thats a 2^4 or 16 collisions (not that many, that means you ahve to go thru a full 2^128 passwords to theoreticly get 1 probable colision. If you do 2 Blocks, a 1KB file, its 2^4^2 or 256 collisions, that means that treated as a 1kb pass you have to do only 2^64th passwords to get a probbable colion because of 16-1 reduction. At 4KB you get 65535 collions and, at 8 its 2^32... now granted that these passwords are longer, and therefore ar equal in the number of crack cycles since a 1meg file=a 512 bit file in crackign puprosed (we are tallking megabits and kilabits). This causes the algarithum to work worse the bigger the Block number is. If you have a say 100meg file you have a HUGE number of collision, now granted that you still have the same number of crack sycles to get a collions, evnetialy the collions reach infinity, and the probablty of getting a collisoin of the nth attempt aprochase 100%. This makes shorter password thoereticly harder to crack. Asuming the averge password is under 14 char, you get 8bits*14char, or 112 non zero bits. That leaves 336 bits of zeros, next you have an automatic 1 at the 448th bit, so thasts 337 bits you know, Next, 7 bits of the 64-bits of the big eddine are used to give the bit length of a 14 char password (112<128). So that means taht you have 57 more known bits + the 337 gives you 394 known bits, and 118 that you have to calculate. Now asmuning that you have the 7 that are random, you have those 112 that can be attacked burte forcefully, and the other 7 can jsut be compiled thru the bruteforce. So we got back to 256^14 combinations thats alot, Lets start haking away at the ascii table, throw away all ther extended ascii since its not on the keyboard and most places that use MD5 (web forums likehak5( don't allow them. THats only 128^14, take out the first 32 numbers because you cant have say a new line char in your password. Thats 96^14, take away sybles tahts only 64^14 now thats still a CRAP load of collisons, but far better than 2^512 possibities. And its only 1/4 of that since probaility sates that tis a 4-1 reduction so there are 4 512 blocks for ever 128 bit hash. Now MD5 beats DES any day since DES is first of all all upercase so its only 2^36^7*2, so its VERY easy to crack. So in short MD5 collisons are MUCH faster to callculate then say MDCRACK can becasue of this fact, you take a chance on a ,001% of passwords but hey 1 hour vs 12 years for 99.9% of passwords any day.

lol yeh I could do taht but I'm lazy if yu want me to stil pm me ill do it

well, tight vnc is ther server, but u could very easly do say a reverse shell and loaunch a loopback vieweer thru it. Thats what I would recomend doign a reverse bind sell, but ud need a server or soe other form of connecion to be able to do a reverse shell since now you would have to have a port open

its to set a service

well yeh its a service

you can either delete it form the bat or put a :: before it to comment it out offtopic: sorry that Ive been sorta not here the last liek 3 weeks, and sorry to peopel liek twighlight who have asked me to code soemthign but I nver got around to it, let me know what u guys need im back (sorta)