"Out of date" is meaningess marketing blather. "End of life/support" is what counts, and for that, Windows 7 falls out of extended support in January 2020, nearly six years from now.
And what languages are these languages themselves written in? At some point you're working with something written in C, C++ or assembler, and if those languages are dangerous to directly write apps in, then surely they must be equally dangerous to write the compilers and platforms on which your non-VM language runs.
At some point it's turtles all the way down. By writing in some other language, you're putting your faith in the people writing the interpreters, VMs and/or compilers, and in many cases those developers are little different than the unfortunate fellow that introduced this particular vulnerability into OpenSSL.
Moving away from C just means you now have to have faith in some bytecode virtual machine's memory and buffer management. Is it a more secure approach? Maybe, but if the root complaint is putting faith in complex software, coding in Java or some.NET language means trusting the people coding those engines are equally capable of screwing up. All these higher level virtual machines and interpreters are ultimately written in C.
I know my webservers are all good, because they're linking against openssl 0.9.8. I just managed to confirm that Debian Squeeze's stock OpenVPN package links to the 0.9.8 library as well, and isn't statically linked, so, so far as I understand the vulnerability, there's no chance I was compromised.
It does indeed pay, on occasion, to stick with older versions. I had actually been looking to upgrade my VPN gateways to Wheezy a few months ago, and am rather glad I didn't.
What? Hebrew is a West/Central Semitic language, and Akkadian was an East Semitic language (there is no extant East Semitic language spoken today). Hebrew was a dialect of Canaanite, and closely related to the Phoenician language. Both Phenician and Hebrew were written in alphabetical scripts that cribbed a good deal of Egyptian writing.
As much as Theo can be an utter and insufferable prick, on this score he's right. This was an insanely trivial error which has exposed who knows how many systems to potential breaches. Right now I'm starting up a full audit of our systems. We use OpenVPN for our interoffice WAN, as well as for clients; many of them Windows, iOS and Android clients, not to mention reviewing all our *nix clients running SSH daemons. We're only a relatively small operation, and it's still a monumental pain in the ass.
It isn't a matter of what it looks like, it rips off the entire crystal dome notion. I don't know why that would bother you an more than the fact Hebrew is a Canaanite dialect written in a script that originates in Egyptian and Sumerian sources.
The Genesis cosmography is a rip off of the Sumero-akkadian cosmography, which was most definitely geocentric. Why do you think by the Hellenic age even the Jews had stopped interpreting Genesis literally?
I have OpenVPN installed on my portable devices, and it connects back to my VPN server, using my own CA. I have the devices set to use the VPN server as the gateway so when I'm doing any kind of data retrieval that I want to keep confidential, it's going through an encrypted tunnel. Yes, it does slow things down a bit, but I find most public WiFi sucks pretty serious donkey balls anyways.
Nothing is 100% secure, but I pretty much treat any public network; airport, airplane, hotel, restaurant, or the like as hostile territory.
Worse, it means retraining, it means loss of productivity, at least in the short term and it brings absolutely no advantage at all to the business workstation. Windows 7 was still part of an evolution from Windows 95. Much smoother and better done, but still, someone coming from XP could, after a few minutes, work in full swing.
Whether the Metro UI is better or not by some subjective, or heck, even objective standard is irrelevant. What is relevant is familiarity. QWERTY may not be the best keyboard layout, VHS may not have been better than Beta, and English spelling rules are a nightmare, but all three were familiar and dominant, and even some technical superiority of alternatives couldn't overcome the level of penetration that they enjoyed.
To my mind, it looks as if Metro will simply become another iteration of the old Active Desktop/Gadgets paradigm, and will likely be ignored by the bulk of PC users.
Pretty much. I know our suppliers simply ask "And you will want Windows 7 on that laptop/workstation, right?" There is an automatic assumption that Windows 8 is not wanted in the enterprise.
A long long time ago, I can still remember how that NT kernel made me smile. And I knew that if I had my chance, I'd write a helluva lot cool VB 6 apps. And maybe my manager would be happy for a while.
But April made me shiver, With each Win 8 PC I'd deliver. Bad news in the staffroom steps. And I couldn't take one more step.
I can't remember if I cried, When I read about some XP user heaved a sigh. But something touched me deep inside. The day Windows XP died.
So bye bye Windows XP has died. Rode my Segway to the to the levy, But the levy was dry. And good ol' sysadmins were drinking coffee and Sprite, Singing "This is the day Windows XP has died, This is the day Windows XP has died."
I can't see how wasting cycles on implanting an x86/x64 instruction set would be of much use commercially. I don't get the impression that many ARM manufacturers have any interest in trying to beat Intel on its own platform.
Slashdot Mirror
Yes Microsoft has done many nasty things, but shutting down support of a 13 year old OS isn't really one of them.
If you buy a product, find out the EOL date. If it is too soon for your liking, don't buy it.
"Out of date" is meaningess marketing blather. "End of life/support" is what counts, and for that, Windows 7 falls out of extended support in January 2020, nearly six years from now.
I don't know. I don't use it, and when it appears I go to classic view.
Well thank you for making this special trip to /. to tell us all about how you don't visit /. anymore.
I read the post as "She should have been helping her peiple, because she's black and a lot of blacks were harmed in Katrina." It is inherently racist.
And what languages are these languages themselves written in? At some point you're working with something written in C, C++ or assembler, and if those languages are dangerous to directly write apps in, then surely they must be equally dangerous to write the compilers and platforms on which your non-VM language runs.
At some point it's turtles all the way down. By writing in some other language, you're putting your faith in the people writing the interpreters, VMs and/or compilers, and in many cases those developers are little different than the unfortunate fellow that introduced this particular vulnerability into OpenSSL.
Moving away from C just means you now have to have faith in some bytecode virtual machine's memory and buffer management. Is it a more secure approach? Maybe, but if the root complaint is putting faith in complex software, coding in Java or some .NET language means trusting the people coding those engines are equally capable of screwing up. All these higher level virtual machines and interpreters are ultimately written in C.
Yeah, I'm sure Comcast's management and investors totally feel bad about that whole public opinion thing.
I know my webservers are all good, because they're linking against openssl 0.9.8. I just managed to confirm that Debian Squeeze's stock OpenVPN package links to the 0.9.8 library as well, and isn't statically linked, so, so far as I understand the vulnerability, there's no chance I was compromised.
It does indeed pay, on occasion, to stick with older versions. I had actually been looking to upgrade my VPN gateways to Wheezy a few months ago, and am rather glad I didn't.
All my servers are sitting at 0.9.8, but at least some of the Windows clients are not. Do I need to worry about?
Don't worry. I've more than made up for Theo's unusual calmness this morning, and have called them names that would make the gods blanch.
Um, that's right, because everywhere and nowhere is the center of the universe, as the CMBR clearly indicates.
What? Hebrew is a West/Central Semitic language, and Akkadian was an East Semitic language (there is no extant East Semitic language spoken today). Hebrew was a dialect of Canaanite, and closely related to the Phoenician language. Both Phenician and Hebrew were written in alphabetical scripts that cribbed a good deal of Egyptian writing.
Nothing you wrote was right.
Exactly
As much as Theo can be an utter and insufferable prick, on this score he's right. This was an insanely trivial error which has exposed who knows how many systems to potential breaches. Right now I'm starting up a full audit of our systems. We use OpenVPN for our interoffice WAN, as well as for clients; many of them Windows, iOS and Android clients, not to mention reviewing all our *nix clients running SSH daemons. We're only a relatively small operation, and it's still a monumental pain in the ass.
It isn't a matter of what it looks like, it rips off the entire crystal dome notion. I don't know why that would bother you an more than the fact Hebrew is a Canaanite dialect written in a script that originates in Egyptian and Sumerian sources.
You could start with the CMBR.
The Genesis cosmography is a rip off of the Sumero-akkadian cosmography, which was most definitely geocentric. Why do you think by the Hellenic age even the Jews had stopped interpreting Genesis literally?
I have OpenVPN installed on my portable devices, and it connects back to my VPN server, using my own CA. I have the devices set to use the VPN server as the gateway so when I'm doing any kind of data retrieval that I want to keep confidential, it's going through an encrypted tunnel. Yes, it does slow things down a bit, but I find most public WiFi sucks pretty serious donkey balls anyways.
Nothing is 100% secure, but I pretty much treat any public network; airport, airplane, hotel, restaurant, or the like as hostile territory.
So if someone walks up and shoots you in the head, that's fine because it's evolution?
Evolutionary biology is science, not morality.
Worse, it means retraining, it means loss of productivity, at least in the short term and it brings absolutely no advantage at all to the business workstation. Windows 7 was still part of an evolution from Windows 95. Much smoother and better done, but still, someone coming from XP could, after a few minutes, work in full swing.
Whether the Metro UI is better or not by some subjective, or heck, even objective standard is irrelevant. What is relevant is familiarity. QWERTY may not be the best keyboard layout, VHS may not have been better than Beta, and English spelling rules are a nightmare, but all three were familiar and dominant, and even some technical superiority of alternatives couldn't overcome the level of penetration that they enjoyed.
To my mind, it looks as if Metro will simply become another iteration of the old Active Desktop/Gadgets paradigm, and will likely be ignored by the bulk of PC users.
Pretty much. I know our suppliers simply ask "And you will want Windows 7 on that laptop/workstation, right?" There is an automatic assumption that Windows 8 is not wanted in the enterprise.
A long long time ago,
I can still remember how that NT kernel made me smile.
And I knew that if I had my chance,
I'd write a helluva lot cool VB 6 apps.
And maybe my manager would be happy for a while.
But April made me shiver,
With each Win 8 PC I'd deliver.
Bad news in the staffroom steps.
And I couldn't take one more step.
I can't remember if I cried,
When I read about some XP user heaved a sigh.
But something touched me deep inside.
The day Windows XP died.
So bye bye Windows XP has died.
Rode my Segway to the to the levy,
But the levy was dry.
And good ol' sysadmins were drinking coffee and Sprite,
Singing "This is the day Windows XP has died,
This is the day Windows XP has died."
I can't see how wasting cycles on implanting an x86/x64 instruction set would be of much use commercially. I don't get the impression that many ARM manufacturers have any interest in trying to beat Intel on its own platform.