Burnings and wholesale murder of civilians came was standard operating procedure. Most of the atrocities were carried out by tories serving under British & American officers.
One of the unpleasant aftereffects of 9/11 is the flood of computer security consultants on the market. To less-than-competent security folks, reverse DNS is considered to be some sort of security hole.
I'd expect to run into this at larger corps and government more than in small or midsize companies.
MIPS and PA-RISC are already dead, PowerPC and Sparc are the next in line. Everyone will be buying commidity x86 hardware in 10 years.
RISC machines once had an impressive performance advantage. Today that is mostly myth. When you see major Unix vendors like IBM, HP and Sun make linux transition plans, you should be seeing the end of Unix "Big-Iron"
Water distribution is rolled into your rent, so the vast majority of poor people do not directly pay for it. If their rent is too high, there are plenty of assistance programs available.
The whole idea of perl is that you can write quick scripts or real applications without learing a new language without having a deep understanding of programming.
The only problem is when people who write quick scripts decide to try and make real programs, and the result is unreadable spaghetti. The same thing used to happen when sysadmin "gurus" strung together unreadable combinations of shell, sed, and awk...
If you to do "serious" programming, "use strict;" is your friend. Or waste time with C or Java.
You are either a troll or a complete idiot. I'm not sure which.
Let's see a quote where RIAA said that music sharing was legal. I suppose the arrest of those cadets at the US Naval Academy for sharing music was a sign of music publishers "approval" of file sharing.
Unless you are completely delusional, there is no way that you can assert and signifigant percentage of Kazaa traffic is used to distribute material other than pirated music, porn, and software.
Your examples of garage bands that have used P2P as a free distributional are heart warming -- but they are exception rather than the rule.
Opensource and freeware can be easily obtained from web pages. While it is possible to use kazaa for legit things, nobody is using Kazaa for legitimate purposes.
Also, I would be concerned that a P2P app like Kazaa would "hijack" important ports.
Re:The VISA application for the US
on
Stupid Security
·
· Score: 1
That sort of thing helps the prosecution in court.
"Mr aWalrus, is it not true that on January 1, 1980, you submitted a signed statement asserting that you a not a member of a violent terrorist organizatino"
Proving that the accused is a liar is a powerful force in criminal trials.
I fail to understand how getting rid of the WinSock API would make network programming more secure.
When you & 10,000 other developers wrote your own memory swapping code, there were probaly 4,000 mistakes that crashed computers or broke apps. Generally available constructs like malloc eliminated those 4,000 bugs by creating standardization.
If you had to go through tedium to create your own "WinSock" equivilent, you'd introduce even more bugs, and probaly decide to not include security features either.
The thinking about the underlying system should have been done already. Somebody figures out how a system should behave, and you code around those parameters.
That thinking should be done by the admins of the system. Any dope who puts a network intensive app on a 10Mb LAN when the app needs more bandwidth or a switched network gets what he deserves.
When new airplanes are developed, test pilots push the aircraft to it's outer limits. The flight manual for an airplane is based upon the testing experience.
Keeping "the big picture" in focus means that you don't really care how a motor lowers landing gear... you just care that the landing gear is down when you land.
Re:Why not just use Web proxies
on
Blocking Kazaa 2.0?
·
· Score: 2, Interesting
Pirating software & music is illegal.
Specifically enabling a P2P app to traverse your network sounds like an invitation to the BSA for a visit or an opportunity for RIAA lawyers to earn their pay.
There is no place for Kazaa or eDonkey on a commercial network.
At one time, it was believed that driving at 15mph was good enough. There was really no reason to go faster.
Railroad executives thought that 18 hour train rides were good enough. Nobody will pay for fast airplanes.
Ten years from now, when an entire motherboard is integrated into a CPU, Slashbotters everywhere will have dim memories of the good old primitive days, when CPUs were mere microprocessors.
No, bargaining is when the four guys that you are paying $1000 to unload a box from your car work 4 hours a week and make more than some IT puke who works 14 hours a day to pay for some retarded convention.
The customary system has much more convenient units than the metric system...
The rigidity of the metric system leads to absurd units... a cup is like 253 mL, 1/3 of a liter is 333 mL, etc...
The units may seem trivial, but really make intuitive sense. a foot is roughly the length of a man's forearm. customary units are designed to be divided or cut into fractional parts. people think in terms of "one-half" or "two-thirds" not.33 or.4
This is not a theoretical discussion. The process as you define it is broken. The "fix" is to design software so that it is not vulnerable to simple, yet devastating hacks. Microsoft has a long history of making fundamentally unintelligent decisions regarding the default state of it's software.
Your assertion that patches should be applied without a second thought (in a perfect world) is the type of intellectual laziness that fosters the kind of security bugs that we are talking about. Code modifications should NEVER be applied to production systems without through testing. The public's acceptance of the notion that sysadmins should be applying patches every week allows shoddily designed software to remain on the market.
The excuse that "no code is perfect" does not affect fundamentally bad design. It wasn't acceptable for GM when they made the "unsafe at any speed" Corvair or Ford when they made the explosively poor Pinto. It shouldn't be acceptable for "enterprise" software.
I guess the clue train hasn't arrived at your dorm yet.
Applying a Windows service pack is a very big deal. They tend to create a bunch of problems when they re-apply default setting and oftentimes disable previous patches.
Easy administration for products like SQL server means that people who have no business running an RDBMS will be running it. When a product that should have professional admins does not, things like patches fall by the wayside.
I work in a place with a 3-week transition period from lab to production no matter what (with the exception of extreme security patches) we firewall intelligently and expose as little to the internet as possible. We have not been affected by any of these.
It's been a well-known fact for some time that the netcraft numbers are badly skewed, since a couple of firms that park domains have thousands of generic pages running apache.
Please shut up. If you make a product easy to setup and administer, don't be suprised when incompetents or people are aren't dedicated IT dorks are responsible for things.
The problem is poor design. If you design easy to use software, it should be easy to use safely.
Slashdot Mirror
Ever read about the war in the south?
Burnings and wholesale murder of civilians came was standard operating procedure. Most of the atrocities were carried out by tories serving under British & American officers.
If you are looking to connect sites in remote areas, satelliete untethers you from the phones.
If you are looking at satellite for any other reason, forget about it. Especially if you are looking to use Direcway as your solution.
Satellite give you fast transfer rates, but managing a network on the other side will be very difficult.
Hate DNS.
One of the unpleasant aftereffects of 9/11 is the flood of computer security consultants on the market. To less-than-competent security folks, reverse DNS is considered to be some sort of security hole.
I'd expect to run into this at larger corps and government more than in small or midsize companies.
Oh yeah, try getting docs on the UltraSparc 3
MIPS and PA-RISC are already dead, PowerPC and Sparc are the next in line. Everyone will be buying commidity x86 hardware in 10 years.
RISC machines once had an impressive performance advantage. Today that is mostly myth. When you see major Unix vendors like IBM, HP and Sun make linux transition plans, you should be seeing the end of Unix "Big-Iron"
Water distribution is rolled into your rent, so the vast majority of poor people do not directly pay for it. If their rent is too high, there are plenty of assistance programs available.
So basically, everyone gets water.
haha nice troll.
I suppose all of those proprietary chips like MIPS, PA-RISC, SPARC, etc are going the way of the dodo because Intel sux...
Go back to overclocking your little gamer desktop.
I'm afraid you're right about Perl 6... breaking lots of compatability features with no real goal just doesn't strike me as a good idea.
The whole idea of perl is that you can write quick scripts or real applications without learing a new language without having a deep understanding of programming.
The only problem is when people who write quick scripts decide to try and make real programs, and the result is unreadable spaghetti. The same thing used to happen when sysadmin "gurus" strung together unreadable combinations of shell, sed, and awk...
If you to do "serious" programming, "use strict;" is your friend. Or waste time with C or Java.
You are right and wrong. There isn't really such a thing as a Class C address these days... nowadays we use CIDR.
/ netcalc .htm
Check out this link:
http://www.telusplanet.net/public/sparkman
They have a bunch of network calculators which will make it alot clearer than I can.
You are either a troll or a complete idiot. I'm not sure which.
Let's see a quote where RIAA said that music sharing was legal. I suppose the arrest of those cadets at the US Naval Academy for sharing music was a sign of music publishers "approval" of file sharing.
Unless you are completely delusional, there is no way that you can assert and signifigant percentage of Kazaa traffic is used to distribute material other than pirated music, porn, and software.
Your examples of garage bands that have used P2P as a free distributional are heart warming -- but they are exception rather than the rule.
Opensource and freeware can be easily obtained from web pages. While it is possible to use kazaa for legit things, nobody is using Kazaa for legitimate purposes.
Also, I would be concerned that a P2P app like Kazaa would "hijack" important ports.
That sort of thing helps the prosecution in court.
"Mr aWalrus, is it not true that on January 1, 1980, you submitted a signed statement asserting that you a not a member of a violent terrorist organizatino"
Proving that the accused is a liar is a powerful force in criminal trials.
I fail to understand how getting rid of the WinSock API would make network programming more secure.
When you & 10,000 other developers wrote your own memory swapping code, there were probaly 4,000 mistakes that crashed computers or broke apps. Generally available constructs like malloc eliminated those 4,000 bugs by creating standardization.
If you had to go through tedium to create your own "WinSock" equivilent, you'd introduce even more bugs, and probaly decide to not include security features either.
The thinking about the underlying system should have been done already. Somebody figures out how a system should behave, and you code around those parameters.
That thinking should be done by the admins of the system. Any dope who puts a network intensive app on a 10Mb LAN when the app needs more bandwidth or a switched network gets what he deserves.
When new airplanes are developed, test pilots push the aircraft to it's outer limits. The flight manual for an airplane is based upon the testing experience.
Keeping "the big picture" in focus means that you don't really care how a motor lowers landing gear... you just care that the landing gear is down when you land.
Pirating software & music is illegal.
Specifically enabling a P2P app to traverse your network sounds like an invitation to the BSA for a visit or an opportunity for RIAA lawyers to earn their pay.
There is no place for Kazaa or eDonkey on a commercial network.
There is no such thing as good enough.
At one time, it was believed that driving at 15mph was good enough. There was really no reason to go faster.
Railroad executives thought that 18 hour train rides were good enough. Nobody will pay for fast airplanes.
Ten years from now, when an entire motherboard is integrated into a CPU, Slashbotters everywhere will have dim memories of the good old primitive days, when CPUs were mere microprocessors.
XML continues to simplify our lives!
Just think, if we spoke XML, we could easy exchange data between people without speaking their language!
Post a complaint that sounds real bad, that a small percentage of the readers of the article will understand...
Maybe the author should be even more vague...
"If you install a software product when another software product is also installed, libraries will be overwritten. Other software will be affected."
Then the slashdot editor can append:
You probaly shouldn't install a software product.
No, bargaining is when the four guys that you are paying $1000 to unload a box from your car work 4 hours a week and make more than some IT puke who works 14 hours a day to pay for some retarded convention.
From restaurants. You can get dishtowels, napkins and tablecloths.
The customary system has much more convenient units than the metric system...
.33 or .4
The rigidity of the metric system leads to absurd units... a cup is like 253 mL, 1/3 of a liter is 333 mL, etc...
The units may seem trivial, but really make intuitive sense. a foot is roughly the length of a man's forearm. customary units are designed to be divided or cut into fractional parts. people think in terms of "one-half" or "two-thirds" not
This is not a theoretical discussion. The process as you define it is broken. The "fix" is to design software so that it is not vulnerable to simple, yet devastating hacks. Microsoft has a long history of making fundamentally unintelligent decisions regarding the default state of it's software.
Your assertion that patches should be applied without a second thought (in a perfect world) is the type of intellectual laziness that fosters the kind of security bugs that we are talking about. Code modifications should NEVER be applied to production systems without through testing. The public's acceptance of the notion that sysadmins should be applying patches every week allows shoddily designed software to remain on the market.
The excuse that "no code is perfect" does not affect fundamentally bad design. It wasn't acceptable for GM when they made the "unsafe at any speed" Corvair or Ford when they made the explosively poor Pinto. It shouldn't be acceptable for "enterprise" software.
I guess the clue train hasn't arrived at your dorm yet.
Applying a Windows service pack is a very big deal. They tend to create a bunch of problems when they re-apply default setting and oftentimes disable previous patches.
Easy administration for products like SQL server means that people who have no business running an RDBMS will be running it. When a product that should have professional admins does not, things like patches fall by the wayside.
I work in a place with a 3-week transition period from lab to production no matter what (with the exception of extreme security patches) we firewall intelligently and expose as little to the internet as possible. We have not been affected by any of these.
It's been a well-known fact for some time that the netcraft numbers are badly skewed, since a couple of firms that park domains have thousands of generic pages running apache.
Please shut up. If you make a product easy to setup and administer, don't be suprised when incompetents or people are aren't dedicated IT dorks are responsible for things.
The problem is poor design. If you design easy to use software, it should be easy to use safely.