Why? What problem are you hoping to have fixed?
|
nothing, I just hope it doesn't break whats not broken.
|
don't play sc2 because it's not available on steam.
|
Thought it was meant to come out sometime today/tomorrow?
|
i noticed nothing with the leaked sp1, its a transperant mu released as an sp for all intents and purposes of the average user
underneath maybe it cuts out stuxnets enabling frameworks? who knows really its all internal whatever it is cue parody... |
remotefx and dynamic memory is great for virtualisation which is what SP1 introduces.
|
either way I won't be installing it. nothing on my PC is broken, I'll be waiting to see what breaks on everyone elses before I go for it (that's assuming there's a 32bit sp1)
|
I'll install it, I've noticed a few niggles. Like now, if I create a new folder on remote shares or on my desktop (lol?) I have to press F5 to refresh before I see it and can rename it.
Damn annoying s***. It's reinstall worthy, I just CBF'd. |
I've not seen much other than framework expansion ideas for some of the API which needed to be done. Many .DLL files have been recompiled with ASLR and DEP enabled which will break many exploits which relied on them being in predictable locations in memory.
|
I've got the exact same thing happening to me pinky
|
Looking forward to trying out remotefx as well. I was thinking they'd also bundle IE9 into SP1 but maybe not.
|
I heard that W7-SP1 was going to be much more of just a bundle of existing fixes. In the SP1 doco:
Service Pack 1 for Windows 7 will include previously released updates. |
I've not seen much other than framework expansion ideas for some of the API which needed to be done. Many .DLL files have been recompiled with ASLR and DEP enabled which will break many exploits which relied on them being in predictable locations in memory. By exploits do you mean virii or those not so kosher loaders used by those who sail the seven seas? |
Its a pain the way they released it on msdn, you can only get the 2gb iso wit the x86 x64 and Itanium versions of the service pack.
That actual sevice pack for each system is only about 500mb. kicked off the install on my work laptop, see how its gone on monday |
Looks like it hit VLSC about three days ago as well. The 2Gb not only including all languages, 32/64bit but is also win7 + win2k8. Guess I'll grab the iso to try it out for myself but will definitely wait til it hits windows updates to push through wsus for other machines.
|
Got it, and I'm still here.
fixed that annoying refresh that I had to do after creating a new file, dont notice anything else yet tho |
All good so far. No major differences so far really...
|
By exploits do you mean virii or those not so kosher loaders used by those who sail the seven seas? By exploits I mean code injected into an application that crashes it, takes control of the process and runs the shellcode put into memory. ASLR is Address Space Layer Randomization, it loads .DLL files into randomized locations in memory so that you can't predict where functions are in memory for your exploit's shellcode to use. DEP is Data Execution Protection which sets the pages/segments in memory to be W^X mode ( write or execute ) which stops shellcode from using kernel functions to access the routines at ring0 to set permissions on active or new memory segments. Put these 2 protection methods together and you make exploiting IE/Adobe/firefox/etc much harder as you will not be able to use the shellcode to run VirtualProtect() or WriteProcessMemory() to allow your shellcode to execute via Return Oriented Programming aka ROP. Virus code and cracks/trainers are just normal programs that have been built/compiled with linker information on which libraries to load and which functions they require. Shellcode used in exploits needs to travel without that data and build it at execution time. Using existing functions in the shellcode helps keep it small enough that you don't push beyond the stack/heap frame space given by the original overflow. [BITS 32] XOR ECX, ECX ; ECX = 0 MOV ESI, [FS:ECX + 0x30] ; ESI = &(PEB) ([FS:0x30]) MOV ESI, [ESI + 0x0C] ; ESI = PEB->Ldr MOV ESI, [ESI + 0x1C] ; ESI = PEB->Ldr.InInitOrder next_module: MOV EBP, [ESI + 0x08] ; EBP = InInitOrder[X].base_address MOV EDI, [ESI + 0x20] ; EBP = InInitOrder[X].module_name (unicode) MOV ESI, [ESI] ; ESI = InInitOrder[X].flink (next module) CMP [EDI + 12*2], CL ; modulename[12] == 0 ? JNE next_module ; No: try next module. Using this code I can find the base address of Kernel32 and then .... wait. What was I talking about again? Yeah never mind me. :P |
Installed it on about 15 odd servers last night including exchange and AD servers. No issues so far.
|
assembly mmmmm, I wish I could get my head around that.
|
Says the size is "73.6 MB - 892.6 MB". Seems very specific. Are they sure? |
It depends what updates & addons you've already got installed, noob.
|
Installed it on about 15 odd servers last night including exchange and AD servers. No issues so far. Realy? thats a pretty big call to go straight to production on 15 servers on a service pack that came out days ago. |
i agree with pARODY
except maybe that bit........nah i agree (pssst pARODY...keep off the Red Bull for a while) |