Of course I have a point, but you don't come here to argue, you come here to make your penis bigger and call people idiots once you realize they're way more intelligent than you are.
Whatever can be done with virtualization, can be done better with host partitioning mechanisms -- this is why they were developed after virtualization, and virtualization was gone from OS design for decades. Just because VMWare spent countless amount of time writing tools for the former instead of latter, does not mean that virtualization is not a dead end in technology development.
I'm sorry the work you do is so unimportant you've never had a use case for full virtualization before. But it's impossible to change your mind on anything because you're an arrogant condescending prick, so either you'll die never understanding it or one day you'll be forced to use it and get the point. There's no use discussing with a child.
Except I do Linux kernel development, and actually know what I am talking about.
I grew up in Russia in the foresty plains where earthquakes are as common as -30'C in San Francisco and I find it hard to understand how one can have a laid back attitude to life while knowing about the impeding "Big One" or similar catastrophic event that will destroy everything tangible they own and possibly kill them in the process.
That's because no matter where you live in US, there are so many things that can leave you poor, sick or dead at any moment, the possibility of an earthquake is very far toward the end of the list of worries.
(written at home, in a place where the ground is going to liquify in the next earthquake)
Also, I don't understand the joy of having a cold ocean (8'C all year round thanks to upwelling) that you cannot swim in. Having to wear jacket in May because of the cold breeze from the said ocean is not a good summer experience either:) Also, I prefer to have snow in winter instead of rain.
Think of ocean shore as an impenetrable sprawl-limiting boundary.
Actually the original plan was to "wind down" slavery over decades, just to avoid any appearance of federal government depriving anyone of property or overriding too much in states' decisions. What was horrendous bullshit because it placed respect of property above the idea of equality.
But then some slave owners and rednecks declared independence, started a war, ate flaming death, and the point was moot.
Do you actually have a point? I know that the use of virtualization is common. So was lead in food handling, bloodletting in medicine, radium in watch faces, and thousands of other instances where wrong and stupid solutions were happily used by millions of people out of ignorance and poorly chosen directions of technology development. Anyone with a brain can tell you that stacking multiple layers of identical functionality is a terrible software design that only appears when someone is stuck with a bad solution that he can't avoid. This means, the development of virtualization instead of OS-supported host partitioning meahcnisms is wrong, and there can be no question about it. The only thing one can argue about, is if existence of bad software justifies its use, or not.
In the case being discussed it's clearly not, because the only reason this "technology" is being used (one instance of Linux server on one host!) is admin's inability to use tools that do not require additional layers between things he does not understand (OS) and other things he does not understand (hardware), so he adds those layers just to have something he can "administer". What clearly identifies him as a VMWare jockey.
Yes, and the place for full virtualization is to run Windows, and be used for testing/debugging, not anything even remotely related to production. What in its turn, would never justify giant commercial projects like VMWare, if not for Windows being stuffed where it does not belong.
It is also about making a system open and extensible by providing clean APIs, web services, mechanisms for adding extensions, function hooks, etc.
It's called "interface". Interfaces exist in many forms (functions, object model, network protocols, interprocess communications protocols, even file formats when they are used for data exchange and communications -- for example, maildir is mostly an interface) but must be handled in the same manner.
Other aspects of design are data model (almost always a central part of design) and data flow (that is somewhat a part of data model but usually distinct from it as it involves short-lived data and its interaction with interfaces and processing mechanisms).
2) Writing very clean code, and then keeping it clean, does NOT save you time in the long run.
It very much does, if the whole process is directed toward writing code that is not broken.
While it does reduce bugs and (in theory) makes it faster to add features in the future, the length of time it takes to write the code in the first place exceeds
If code would have less bugs if it was developed slower, then you are writing it in a hurry, and can't rely on anything written in such manner. All such code will eventually have to be replaced, thus negating all perceived savings (if it won't destroy your project first). This is acceptable as a last-resort effort for pushing a known-bad release out of the door, but it does not work in the long term.
the time saved by fewer bugs, and the future features must also be clean, which *always* requires more refactoring than you would expect.
Good code does not need "refactoring", unless there is a major design change in the middle of a project. If you have to constantly reimplement the same functionality, either your design is fundamentally wrong, or you never implemented it properly, or (most likely) both, and you are incompetent.
As I have mentioned, the whole direction is wrong. Efforts wasted on Xen and KVM (and User Mode Linux) could be spent better on LXC, OpenVZ and other legitimate host partitioning mechanisms and tools for their management.
The whole virtualization fad exists only because Windows has no host partitioning mechanisms, so it's ok to add another layer of absolutely everything (virtual memory, scheduler, filesystem, drivers...) on top of the sorry excuse of OS that is Windows. Full virtualization is an obsolete technology that was used in mainframes and was abandoned when minicomputers replaced them. At this point it's an undead monstrosity, restored back to life by the extreme level of crappiness, only present in the worst general-purpose operating system in existence -- Windows.
Too many advantages to list here, but the top two are, Abstraction away from specific hardware, Backup (Snapshot). Makes recovery a breeze and as painless as your last snapshot.
Translation: "I am a VMWare jockey who juggles snapshot images as a replacement of package manager, backup, configuration management, intrusion detection, disaster recovery, ongoing maintenance, deployment, and everything else, because I don't know anything but Windows".
More like, special pricing you get when you are trying to produce a report that is supposed to show how cheap it is to keep using Microsoft software. Microsoft can just quote arbitrary numbers and claim that someone, somewhere, could get them if they didn't use something else.
Channel partners don't continue buying product if it isn't selling you fool, but they have continued to buy Windows 8 licenses. It's not spectacular and it's not setting any records but it is solid.
They don't have time to "continue" when Microsoft already "sold" a year's supply to them.
It doesn't mean, it's sold to consumers, you dumbass. Microsoft is famous for stuffing distribution channels with unpopular products while claiming that they are sold to consumers, in hope to push those products on impression of being popular.
No, it does not. The letter claims that "attack" involved SQL injection, however the nature of the problem described in the article excludes the possibility of it, unless two unrelated security problems are conflated. SQL injection involves a malformed input that results in SQL statements embedded in such input being executed. The article, on the other hand, says:
While looking at the student portal's website, they discovered that by exchanging other student numbers in the encrypted links, they could easily obtain information such as the social insurance numbers, home addresses and phone numbers of more than 250,000 students.
When the server expects and accepts requests without any conversion or filtering as a part of its interface, a client that produces an such request is nothing but a legitimate client, even if the request is unexpected. Anyone who can't distinguish between this and SQL injection attack, is completely ignorant of anything related to computer security, and should never be allowed to make any decisions related to it.
Kaspersky really should stop pretending to know anything other than DOS and Windows malware. "Cyber weapons" exploit easily avoidable vulnerabilities, that exist because companies responsible for infrastructure-critical software are incompetent and greedy. Stop filling the market with overpriced hastily built crap, and there would be no "evil hackers" to speak about.
I also remember it being an SQL injection, but I don't want to go on record saying that because I'm not 100% sure (my friend was also telling me that same day that the other guy, who didn't get expelled, was using an SQL injection to break in to the Pizza Pizza system and remove his order so he could then call them up and say he had placed an order that hadn't arrived yet, resulting in free pizza).
I can assure you that if it was an SQL injection attack, you would remember it VERY clearly, as it's a very distinct type of vulnerabilities.
Apparently, the programmer and one of the other guys decided they were just going to take the info, which was easy to do since Omnivox is such a terrible system, by breaking in.
The information is either accessible or not. If it is accessible through a provided interface, there is no "breaking in", interface just has bad access control and must be fixed.
There is a possibility that the students discovered a nontrivial vulnerability such as SQL injection attack, and somehow based their application on it, however unless this is spelled out, there is no reason to believe that this is the case, and if there wasm everyone would be trumpeting this instead of using weasel words.
Slashdot Mirror
Oh wow, I was arguing with a moron who thinks, Linux kernel is shitty because it's in C. What a waste of time and bandwidth.
Of course I have a point, but you don't come here to argue, you come here to make your penis bigger and call people idiots once you realize they're way more intelligent than you are.
Whatever can be done with virtualization, can be done better with host partitioning mechanisms -- this is why they were developed after virtualization, and virtualization was gone from OS design for decades. Just because VMWare spent countless amount of time writing tools for the former instead of latter, does not mean that virtualization is not a dead end in technology development.
I'm sorry the work you do is so unimportant you've never had a use case for full virtualization before. But it's impossible to change your mind on anything because you're an arrogant condescending prick, so either you'll die never understanding it or one day you'll be forced to use it and get the point. There's no use discussing with a child.
Except I do Linux kernel development, and actually know what I am talking about.
I grew up in Russia in the foresty plains where earthquakes are as common as -30'C in San Francisco and I find it hard to understand how one can have a laid back attitude to life while knowing about the impeding "Big One" or similar catastrophic event that will destroy everything tangible they own and possibly kill them in the process.
That's because no matter where you live in US, there are so many things that can leave you poor, sick or dead at any moment, the possibility of an earthquake is very far toward the end of the list of worries.
(written at home, in a place where the ground is going to liquify in the next earthquake)
Also, I don't understand the joy of having a cold ocean (8'C all year round thanks to upwelling) that you cannot swim in. Having to wear jacket in May because of the cold breeze from the said ocean is not a good summer experience either :) Also, I prefer to have snow in winter instead of rain.
Think of ocean shore as an impenetrable sprawl-limiting boundary.
Actually the original plan was to "wind down" slavery over decades, just to avoid any appearance of federal government depriving anyone of property or overriding too much in states' decisions. What was horrendous bullshit because it placed respect of property above the idea of equality.
But then some slave owners and rednecks declared independence, started a war, ate flaming death, and the point was moot.
Do you actually have a point? I know that the use of virtualization is common. So was lead in food handling, bloodletting in medicine, radium in watch faces, and thousands of other instances where wrong and stupid solutions were happily used by millions of people out of ignorance and poorly chosen directions of technology development. Anyone with a brain can tell you that stacking multiple layers of identical functionality is a terrible software design that only appears when someone is stuck with a bad solution that he can't avoid. This means, the development of virtualization instead of OS-supported host partitioning meahcnisms is wrong, and there can be no question about it. The only thing one can argue about, is if existence of bad software justifies its use, or not.
In the case being discussed it's clearly not, because the only reason this "technology" is being used (one instance of Linux server on one host!) is admin's inability to use tools that do not require additional layers between things he does not understand (OS) and other things he does not understand (hardware), so he adds those layers just to have something he can "administer". What clearly identifies him as a VMWare jockey.
Yes, and the place for full virtualization is to run Windows, and be used for testing/debugging, not anything even remotely related to production. What in its turn, would never justify giant commercial projects like VMWare, if not for Windows being stuffed where it does not belong.
It is also about making a system open and extensible by providing clean APIs, web services, mechanisms for adding extensions, function hooks, etc.
It's called "interface". Interfaces exist in many forms (functions, object model, network protocols, interprocess communications protocols, even file formats when they are used for data exchange and communications -- for example, maildir is mostly an interface) but must be handled in the same manner.
Other aspects of design are data model (almost always a central part of design) and data flow (that is somewhat a part of data model but usually distinct from it as it involves short-lived data and its interaction with interfaces and processing mechanisms).
2) Writing very clean code, and then keeping it clean, does NOT save you time in the long run.
It very much does, if the whole process is directed toward writing code that is not broken.
While it does reduce bugs and (in theory) makes it faster to add features in the future, the length of time it takes to write the code in the first place exceeds
If code would have less bugs if it was developed slower, then you are writing it in a hurry, and can't rely on anything written in such manner. All such code will eventually have to be replaced, thus negating all perceived savings (if it won't destroy your project first). This is acceptable as a last-resort effort for pushing a known-bad release out of the door, but it does not work in the long term.
the time saved by fewer bugs, and the future features must also be clean, which *always* requires more refactoring than you would expect.
Good code does not need "refactoring", unless there is a major design change in the middle of a project. If you have to constantly reimplement the same functionality, either your design is fundamentally wrong, or you never implemented it properly, or (most likely) both, and you are incompetent.
As I have mentioned, the whole direction is wrong. Efforts wasted on Xen and KVM (and User Mode Linux) could be spent better on LXC, OpenVZ and other legitimate host partitioning mechanisms and tools for their management.
Xen is crap, too.
The whole virtualization fad exists only because Windows has no host partitioning mechanisms, so it's ok to add another layer of absolutely everything (virtual memory, scheduler, filesystem, drivers...) on top of the sorry excuse of OS that is Windows. Full virtualization is an obsolete technology that was used in mainframes and was abandoned when minicomputers replaced them. At this point it's an undead monstrosity, restored back to life by the extreme level of crappiness, only present in the worst general-purpose operating system in existence -- Windows.
If you can benefit from crutches, it means that you are lame. Nothing else matters.
Same applies to software tools designed as crutches for Windows sysadmins.
Too many advantages to list here, but the top two are, Abstraction away from specific hardware, Backup (Snapshot). Makes recovery a breeze and as painless as your last snapshot.
Translation: "I am a VMWare jockey who juggles snapshot images as a replacement of package manager, backup, configuration management, intrusion detection, disaster recovery, ongoing maintenance, deployment, and everything else, because I don't know anything but Windows".
More like, special pricing you get when you are trying to produce a report that is supposed to show how cheap it is to keep using Microsoft software.
Microsoft can just quote arbitrary numbers and claim that someone, somewhere, could get them if they didn't use something else.
Just because it is "less one-sided" does not mean, it is not bullshit.
Channel partners don't continue buying product if it isn't selling you fool, but they have continued to buy Windows 8 licenses. It's not spectacular and it's not setting any records but it is solid.
They don't have time to "continue" when Microsoft already "sold" a year's supply to them.
Just the opposite.
Douchebaggery directed against objective truth deserves more harsh response than personal attacks.
At 4chan they are called fucktards, just like everyone else.
One user in five Universes!
It doesn't mean, it's sold to consumers, you dumbass. Microsoft is famous for stuffing distribution channels with unpopular products while claiming that they are sold to consumers, in hope to push those products on impression of being popular.
1. It depends on the intensity. Obviously being far enough from any source of radiation, you get lower amount of it.
2. You are an idiot.
s/produces an/produces any/
No, it does not. The letter claims that "attack" involved SQL injection, however the nature of the problem described in the article excludes the possibility of it, unless two unrelated security problems are conflated. SQL injection involves a malformed input that results in SQL statements embedded in such input being executed. The article, on the other hand, says:
While looking at the student portal's website, they discovered that by exchanging other student numbers in the encrypted links, they could easily obtain information such as the social insurance numbers, home addresses and phone numbers of more than 250,000 students.
When the server expects and accepts requests without any conversion or filtering as a part of its interface, a client that produces an such request is nothing but a legitimate client, even if the request is unexpected. Anyone who can't distinguish between this and SQL injection attack, is completely ignorant of anything related to computer security, and should never be allowed to make any decisions related to it.
Kaspersky really should stop pretending to know anything other than DOS and Windows malware. "Cyber weapons" exploit easily avoidable vulnerabilities, that exist because companies responsible for infrastructure-critical software are incompetent and greedy. Stop filling the market with overpriced hastily built crap, and there would be no "evil hackers" to speak about.
I also remember it being an SQL injection, but I don't want to go on record saying that because I'm not 100% sure (my friend was also telling me that same day that the other guy, who didn't get expelled, was using an SQL injection to break in to the Pizza Pizza system and remove his order so he could then call them up and say he had placed an order that hadn't arrived yet, resulting in free pizza).
I can assure you that if it was an SQL injection attack, you would remember it VERY clearly, as it's a very distinct type of vulnerabilities.
Apparently, the programmer and one of the other guys decided they were just going to take the info, which was easy to do since Omnivox is such a terrible system, by breaking in.
The information is either accessible or not. If it is accessible through a provided interface, there is no "breaking in", interface just has bad access control and must be fixed.
There is a possibility that the students discovered a nontrivial vulnerability such as SQL injection attack, and somehow based their application on it, however unless this is spelled out, there is no reason to believe that this is the case, and if there wasm everyone would be trumpeting this instead of using weasel words.