I'm sure that's what the left-wing conspiracy theorists believe, but in reality he shot himself with an AK-47, and there was no need to reload : http://en.wikipedia.org/wiki/Death_of_Salvador_Allende
You do not have a shortage of good applicants, such a shortage is impossible in a market system like we have. What you have is too low a price point.
I wish that were true
This chart is nearly useless, as it doesn't account for the average distance traveled per country. You'd be better off reading the wikipedia page that has those stats : http://en.wikipedia.org/wiki/List_of_countries_by_traffic-related_death_rate
Or looking at trend in deaths / mile over time. For example, the US rate of 1.1 per 100M miles in 2011 is an all-time low : http://en.wikipedia.org/wiki/List_of_motor_vehicle_deaths_in_U.S._by_year
Couldn't a similar suit be brought against the developers iptables or squid if those applications are used by an oppressive government? Just answering a question from a user with
I'm up to 15644 commits in total on the Webmin / Virtualmin projects..
The trouble with Linux, and I'm speaking as someone who's used YaST in precisely this context, is that you have to make a choice - do you let the GUI manage it or do you CLI it?
Or you can use a GUI tool that can parse manually created config files and not break settings in them that it doesn't understand, such as Webmin. YaST has its own separate configuration database that it generates the Apache config files from, so any manual changes you make will either be ignored or over-written.
On a VPS, it really doesn't matter if the hosting company has your root password or not - they can directly access the filesystem to view or modify any files any time they want.
For some virtualization types (like Xen and KVM) it is more convenient for the host to know the root password so they can login to manage the VPS. Without it, filesystem access requires that the VPS be shut down, with is worse for everyone.
For other types like OpenVZ, the host can login as root any time they want, without even knowing the password.
In the case of GoDaddy, they would probably be better off setting up VPSs they sell with an additional root-equivalent account or using SSH keys - that way the customer can keep their root password secret.
While I totally agree that overriding NXDOMAIN responses is evil, returning different DNS responses based on the clients location or for load balancing purposes is an extremely useful technique for last companies serving a large amount of web traffic. For example, check out what www.google.com resolves to from different countries or even at different times - depending on where you look it up from and what network links are up, you will get a different set of IPs.
Sure, determining a browser's location from the DNS client source IP is not totally reliable
Wrong wrong wrong!
Do you think Comcast has a connection they own all the way to every website you visit? Of course not
And even at the tier-1 ISP level, fibre in the ground or under the ocean only has limited capacity. When that gets used up, they have to lay more fibre
Since I live in the area where this happened and it was reported extensively on the local news, I noticed *many* errors in TFA, such as :
- Morgan Hill was not specifically targeted
- Cables were cut in four different locations, so there was no single point of failure.
- Hosting everything at your site might help in cases like this, but is your mail really more reliable if managed by a part-time sysadmin on a single $1000 box, or at Google where they have triple-redundant everything?
your credit cards you carry around? the PIN number isn't stored on the card - but an MD5 hash of the PIN number *is* stored on the card (making replay attacks possible, believe it or not).
I sure as hell hope not! If that was the case, anyone with a card reader could brute-force your PIN in under a second by taking the MD5 hash of all 4 digit numbers, and comparing them to be hash that is supposedly on the card.