You're right about unnecessary remote access. Even on a local network though, you don't let everybody on the network have access to the control systems. Most, if not all, the things mentioned in your quote apply to local networks, too.
If I had my druthers, I would also pull out the floppy, CD and DVD drives and the USB and Firewire ports as well. Viruses, trojans and malware don't just come in over the Internet. I would also not have wi-fi. Just like with cell phones on airplanes, there may not be any chance of wi-fi interference with controls, but why take the chance if you don't have to?
It seems like not enough people consider taking away or disabling things, not just adding things, to make their infrastructure more secure.
Not everybody that uses OSS software is a developer.
Not everyone who uses OSS software has to be a developer to contribute. There are developers out there who wouldn't mind being paid to make an Enterprise Studio-y front end for MySQL for you. Hell, anything is possible; it's only a question of time and money.
I just now searched Google Maps for my home address, and brought up the satellite view. It shows only two areas of my subdivision and only one row of houses. Today, there are three areas fully built with a fourth well underway. If Google Street View's data will be this out of date, most people will have nothing to worry about.
Safari uses WebKit from KDE. Camino uses Gecko from Firefox. They're two entirely different browsers with two entirely different engines. Apples and oranges.
And since Camino uses the same engine as FireFox, how is FireFox any better at protecting users from phishing scams. And since FireFox is available for Linux and Windows, as well as OS X, wouldn't there be problems on those OSs as well.
I really don't see where this is a Mac problem, Safari problem, or anything other than a User problem.
This is a showcase review for our sponsors at The Code Project. These reviews are intended to provide you with information on products and services that we consider useful and of value to developers.
Bud: Yes.
Lou: What?
Bud: He's the Secretary of the Treasury.
Lou: Who?
Bud: He's the President.
Lou: Who is?
Bud: Right.
Lou: The President is Right?
Bud: Sometimes he is.
Lou: What are you talking about?
Bud: Hu is right sometimes.
Lou: I don't know.
Both: THIRD BASE!
I made some fancy programs at home on my Coleco ADAM's SmartLOGO and could type the printout character-for-character into a Commodore 64 and it would run fine! There were visual differences due to differing resolutions and colour palletes (both had 16 colour selections but didn't use the same 16 so it looked tacky on one of the machines). There was absolutely no way to accomplish this level of compatibility with BASIC (beyond the rudimentary MSBASIC standards, so no graphics or sound) with one exception--the Coleco computers' SmartBASIC was syntax-compatible with Applesoft BASIC.
This reminded me of this joke I heard in college. Thomas Hardy -- The man who put Apple software into an ADAM computer, and came up with the first computer with the knowledge of good and evil.
The people there have proven themselves to be the most paranoid and obnoxious people in the country. I'm never going anywhere near that city if I can at all help it. Osama, there's your next target. Help a brutha' out, dog.
If I paid money for something, I should be able to do whatever I want to with it. I shouldn't have to jump through hoops to use something I own. I don't call Honda to "enable" me to drive my car after I buy it. If I buy something, I should already be "enabled".
The moral of the story is "Write your own goddamned code". Note that this applies to *everybody*. BSD, stop using GPL'd code. GPL, stop using BSD'd code. Fuck Theo. Fuck Marcus. Fuck Michael. Fuck Bruce. Everyone should just do their own fucking work.
None of these facts are relevant to the discussion.
They _are_. Actually, these seem to be the _only_ facts that are relevant to the discussion in the first place.
What's also relevant is that a public "discussion" wasn't necessary. You could have avoided all this negative publicity by simply talking to Marcus in private, and if that fails, go public. But you refused to do that, so this circus is all on you.
It's interesting that people seem to think _I_ have to apologize, as the OpenBSD developers did the Bad Things in the first place. There's a simple rule: Don't violate copyrights and don't get blamed for it. It's so simple.
The copyright violation was not an excuse for public humiliation. As the wronged party in this, and the first responder, you could still have acted in a professional and respectful manner by talking privately with Marcus before taking it public. By bypassing all that, you just made yourself look like an asshat that no one would want to work with.
Of course. It was so obvious from looking at you. :)
You're right about unnecessary remote access. Even on a local network though, you don't let everybody on the network have access to the control systems. Most, if not all, the things mentioned in your quote apply to local networks, too.
If I had my druthers, I would also pull out the floppy, CD and DVD drives and the USB and Firewire ports as well. Viruses, trojans and malware don't just come in over the Internet. I would also not have wi-fi. Just like with cell phones on airplanes, there may not be any chance of wi-fi interference with controls, but why take the chance if you don't have to?
It seems like not enough people consider taking away or disabling things, not just adding things, to make their infrastructure more secure.
How do I feel. What do I say. Fuck you, it all goes away.
I just now searched Google Maps for my home address, and brought up the satellite view. It shows only two areas of my subdivision and only one row of houses. Today, there are three areas fully built with a fourth well underway. If Google Street View's data will be this out of date, most people will have nothing to worry about.
Is fanbo(i|y) like the new N-word or something?
Safari uses WebKit from KDE. Camino uses Gecko from Firefox. They're two entirely different browsers with two entirely different engines. Apples and oranges. And since Camino uses the same engine as FireFox, how is FireFox any better at protecting users from phishing scams. And since FireFox is available for Linux and Windows, as well as OS X, wouldn't there be problems on those OSs as well. I really don't see where this is a Mac problem, Safari problem, or anything other than a User problem.
Substitute, that is.
Bud: Yes.
Lou: What?
Bud: He's the Secretary of the Treasury.
Lou: Who?
Bud: He's the President.
Lou: Who is?
Bud: Right.
Lou: The President is Right?
Bud: Sometimes he is.
Lou: What are you talking about?
Bud: Hu is right sometimes.
Lou: I don't know.
Both: THIRD BASE!
Google "Darwin ports^W^WMacPorts". FTFY.
The people there have proven themselves to be the most paranoid and obnoxious people in the country. I'm never going anywhere near that city if I can at all help it. Osama, there's your next target. Help a brutha' out, dog.
You're not exactly avoiding the possible loss of life if you shoot her, are you? Or do only other people's lives count in your statement?
In Slashdot's RSS feed, the entry for this article has an inline ad for AT&T. Your world. Delivered (to the FBI). Indeed.
From the RSS feed, or as I call it, arsefeed, right below the article is an ad for AT&T.
If I paid money for something, I should be able to do whatever I want to with it. I shouldn't have to jump through hoops to use something I own. I don't call Honda to "enable" me to drive my car after I buy it. If I buy something, I should already be "enabled".
The moral of the story is "Write your own goddamned code". Note that this applies to *everybody*. BSD, stop using GPL'd code. GPL, stop using BSD'd code. Fuck Theo. Fuck Marcus. Fuck Michael. Fuck Bruce. Everyone should just do their own fucking work.