I guess the software under attack is designed to stop limited exploits from becoming big ones, and it's referring to the image in the.DLL in it's loaded into memory state, not on disk.
I'd describe it as like knowing how to use a coathanger to unlock a car door.
I'm talking about major changes to the IO system to reduce the number of redundant write operations, and to align those operations (and paging) with the native block size of the device.
An SSD drive should last much longer under Win 8+ than older versions.
Versions that add support for major new hardware/API's suck, until driver/application developers catch up with the new tech (including Microsoft internal developers...)
(1x) 1.0 > 2.0 > 2.1 I think I was still using an Amiga that generation... So I don't recall the details. (3x) So 3.0 > 3.1 > 3.11 (Cooperative Multitasking, Protected memory mode) (4x) 95 > 98 > 98 SE (Explorer, TCP/IP, COM interfaces) (5x) (2K/ME) > XP > XP SP2 (an actual, but underused security model, removal of Real mode DOS, SFP, System Restore) (6x) Vista > (Marketing skip) Seven > Seven (with patches) Added real 64 bit support, native IPv6, No longer Administrator as default user. (8x) 8, 8.1, 9 (Tablet interface, SSD support, 'Metro'/RT)
Years ago I was the IT guy for a local government budget office.
After I stopped the servers from crashing any spending an hour rebuilding every day, and fixed the backup system so it actually backed up data, I had plenty of free time.
Instead of hiding in my office looking busy while playing MUDS/Nethack I took the time to sit with individual users, and quietly//observe their workflow.//
They spent most of the day comparing two columns of numbers (one from mainframe, one from SQL) for equality.
After a quick VBA prototype, they ended up with simple daily reports of where the numbers didn't match, saving about 40 hours a day between the 20 analysts.
The key thing many IT guys miss, is taking the time to fully understand what the users actually need/want; but instead jump to conclusions that everyone wants what a programmer wants.
I used to set lead type in my parents print shop as a kid, and I'm perfectly fine, even after setting lead type in my parents print shop, it had no effect on me, just like setting lead type in my parents print shop.
My point was, I've heard of 'upstate New York' without ever coming within 1000 miles of it. But no one here, that I know of, ever called any part of Washington 'upstate', so it's a meaningless description.
Back when I did tech support for a lightweight Mac database product, they didn't use Parity (much less ECC) RAM.
I had a customer call in because students were continually getting corrupted databases on their assignments.
over the course of several phone calls, we narrowed it down to only happening in 1 of 3 labs.
After excluding anything high-energy (like a physics lab) in the building, I got the customer to reveal that they were constructing a new building next door, and the construction power tools were running off the same circuits as the computer lab...
They got the construction workers to use a different source of power, and the corruption problems disappeared.
"they work for peanuts, literally"
By 'E. Indian' did you mean 'Elephants (Indian)'?
... and I hate those spies always sapping my sentries.
My Dad was a wiring inspector for Boeing; he did the wiring in our house. ...
I don't fly.
... Metallica isn't real metal.
OK, replying to myself, after doing more reading.
I guess the software under attack is designed to stop limited exploits from becoming big ones, and it's referring to the image in the .DLL in it's loaded into memory state, not on disk.
I'd describe it as like knowing how to use a coathanger to unlock a car door.
If you are able to arbitrarily modify system .DLLs, aren't you already in the system?
Sounds an awful lot like today's Old New Thing post: http://blogs.msdn.com/b/oldnew...
I'm talking about major changes to the IO system to reduce the number of redundant write operations, and to align those operations (and paging) with the native block size of the device.
An SSD drive should last much longer under Win 8+ than older versions.
It's pretty simple actually.
Versions that add support for major new hardware/API's suck, until driver/application developers catch up with the new tech (including Microsoft internal developers...)
(1x) 1.0 > 2.0 > 2.1 I think I was still using an Amiga that generation... So I don't recall the details.
(3x) So 3.0 > 3.1 > 3.11 (Cooperative Multitasking, Protected memory mode)
(4x) 95 > 98 > 98 SE (Explorer, TCP/IP, COM interfaces)
(5x) (2K/ME) > XP > XP SP2 (an actual, but underused security model, removal of Real mode DOS, SFP, System Restore)
(6x) Vista > (Marketing skip) Seven > Seven (with patches) Added real 64 bit support, native IPv6, No longer Administrator as default user.
(8x) 8, 8.1, 9 (Tablet interface, SSD support, 'Metro'/RT)
I think having one of those would be a republican presidential candidate requirement.
Years ago I was the IT guy for a local government budget office.
After I stopped the servers from crashing any spending an hour rebuilding every day, and fixed the backup system so it actually backed up data, I had plenty of free time.
Instead of hiding in my office looking busy while playing MUDS/Nethack I took the time to sit with individual users, and quietly //observe their workflow.//
They spent most of the day comparing two columns of numbers (one from mainframe, one from SQL) for equality.
After a quick VBA prototype, they ended up with simple daily reports of where the numbers didn't match, saving about 40 hours a day between the 20 analysts.
The key thing many IT guys miss, is taking the time to fully understand what the users actually need/want; but instead jump to conclusions that everyone wants what a programmer wants.
As a trans-offended person, I'm offended by your reluctance to allow people to be offended.
Some of us enjoy being shocked, offended, and triggered so stop cis-comfort-zone oppressing us.
... also traffic cameras.
How does the logic of this decision impact future 'legalize' campaigns for marijuana?
Some of us just don't care about some One Percenter's waterfront mansion.
I used to set lead type in my parents print shop as a kid, and I'm perfectly fine, even after setting lead type in my parents print shop, it had no effect on me, just like setting lead type in my parents print shop.
The Titanic == Itanium
*cough* Microsoft .net
Each letter in an english word only stores one bit worth of data on average.
see: http://www.maximumcompression....
And moist anjone can eaiily correc simxle errors automaxically while reeding in there heads.
I'm sure mistakes were made while carving stone tablets, and they just said 'Fuck it, it's fine.'
I was at a Pho shop the other day, with etched glass windows reading 'NODDLE SOUP' (in Comic Sans...)
First read as "Flesh eating spiders"
all the 'nope' in the world isn't enough.
And Prison inmate are considered paragons of morality?
Talk about moving the goalposts...
My point was, I've heard of 'upstate New York' without ever coming within 1000 miles of it. But no one here, that I know of, ever called any part of Washington 'upstate', so it's a meaningless description.
I've lived in Washington 40 years, and I'm never heard of a town/county named 'upstate'.
... I was following until you randomly brought 9/11 into it, thereby showing you are a nutjob.
He explains it by not taking his anti-psychotic medication.
Back when I did tech support for a lightweight Mac database product, they didn't use Parity (much less ECC) RAM.
I had a customer call in because students were continually getting corrupted databases on their assignments.
over the course of several phone calls, we narrowed it down to only happening in 1 of 3 labs.
After excluding anything high-energy (like a physics lab) in the building, I got the customer to reveal that they were constructing a new building next door, and the construction power tools were running off the same circuits as the computer lab...
They got the construction workers to use a different source of power, and the corruption problems disappeared.