Security → Re: Windows XP: Remove the Cable, Tape Up the Ethernet Port

Not really all that different from what is happening on my 2002 vintage Windows XP workstation at this moment (except that I use SeaMonkey instead of Firefox).

FWIW, the high usage on the beginning of the chart was an HD streaming video (which this old box does well enough that I have no plans to replace either it or its OS).

The main difference is he's using all current software, not 13 year old software with a few current pieces that still work on the digital fossil.

What can I say except that us old fossils have to stick together. I am from the era when vacuum tube computers were just beginning to be developed, and I wear the fossil label with pride.

My "13 year old software" does everything I need it to do. Why should I spend hard to come by money just because somebody else decides that I need new software?

Because your 13 year old operating system is a gaping security hole. If you where running a f/oss operating system you can stay up to date and keep your old software chugging along without the security holes unless they exist in your old app.

Clinging to an ancient version of Windows and hoping that your next trip online wont require you to reformat due to security holes that are known and will never be fixed is not a solution. Or do you not remember the Vista exploit that has apparently been exploitable there since Win3.11?

Fun thing about a competent bit of malware is you may never know its there »it.slashdot.org/story/13 ··· omputers

What can I say except that us old fossils have to stick together. I am from the era when vacuum tube computers were just beginning to be developed, and I wear the fossil label with pride.

My "13 year old software" does everything I need it to do. Why should I spend hard to come by money just because somebody else decides that I need new software?

My lineage is similar to yours, and I still know how to mend old vacuum tube audio amplifiers and such, if any present themselves, and have the test equipment to help me do so.

I'll remember that if I ever blow any more tubes in my Pioneer tube amp.

HEAR, HEAR !

My lineage is similar to yours, and I still know how to mend old vacuum tube audio amplifiers and such, if any present themselves, and have the test equipment to help me do so.

Is that one of those radios that you have to let warm up before you can safely transmit or risk damage to the tubes? I seem to remember once encountering an old ham set that would have to be turned on and let sit for a little bit to warm up the tubes.

Actually I think there's a small but active market in vacuum tubes. Many audiophiles and old-school folks repair and maintain such systems--even computers

[att=1]
ENIAC Type Arithmetic System-Computer

And not being connected to the internet I bet that ENIAC is secure even though "support" has long since ended

All this hoopla about XP/2003 not being secure after April 2014 is just a running joke.

1. XP Professional, Enable Software Restriction Policies, white list your known good apps, and nothing else will run on it...malware problem solved....malware can't install if the scripts/executable won't even run.

2. Install the AV/Security Suite of your choice (XP will be supported by vendors for quite awhile longer because the market is their for them to make money)

3 enjoy your XP/2003 system for as long as you want....if you want to be evne more secure install Windows SteadyState..works just fine for XP.

in terms of security one "could" argue that newer versions of Windows are more of a security risk...because Windows 7 Code base, for exmaple, is huge in comparison with XP...just look at the amount of hard drive space each install takes...more lines of code = greater chance a flaw exists somewhere.

That post you listed to by Diddier Stevens was patched long ago. Its also only exploitable if you have applications such as Office with macros, or other applications that use scripting languages...no one on this forum enables Office Macro's by default, and Scripting inside PDF readers is the kiss of death here.

»support.microsoft.com/kb/2532445

Larry, I don't even know where to begin, but i will try.

1. SRP is enough. That post you listed to by Diddier Stevens was patched long ago.

Its also only exploitable if you have applications such as Office with macros, or other applications that use scripting languages...no one on this forum enables Office Macro's by default, and Scripting inside PDF readers is the kiss of death here.

»support.microsoft.com/kb/2532445

2. Im not saying AV/Security software is good. However it will do good enough in the 10% of the time SRP doesn't stop something 1st.

3. Your speaking of Kernel Exploits, but your leaving out the mention of those who practice safe hex...those who don't run as admin, those who don't visit unfamlair websites, those who have IE settings cranked to the max except the few sites we trust....under those conditions...XP will be fine for a long time.

Many of these "kernel exploits" are very hyped up...most only work on a "default configuration" of the said OS...you really think people here are not running a tweaked version?

DEP makes heap sprays much harder to pull off.

there is a multitude of factors at play here...XP can be secure enough to use after support as long as one plays it safe. The OS will be as safe as whats between the ears of its user.

The fact is most malware is ran by users, not by exploits, and with most of them elevating it, otherwise already running as a full admin they let that trojan horse onto the system themselves.