Indiana University is a perfect example of a university being counterproductive in preparing students for the porn industry. A group of students tried to make up for what the school wasn't teaching them, and the school tries to press charges. This is comparable to the whole "Trip Hawkins' professor shooting him down" thing.
Similar such oppression has occurred at my school. One afternoon, a student was researching the pornography industry in the library, and he was ESCORTED OUT! I couldn't believe such a travesty would occur to someone whom I assume was just hoping to break into that $11 billion industry.
I've only heard it pronouced soul-air-iss(as in kiss), before the trailer. There really isn't a definitive answer, the right pronouciation is whatever the hell Sun wants it to be. And they ain't talking.
Every developer should have a guide on how to say the name of their product.
There's a unix pronouciation guide here or here, but the solaris pronunciation is none too specific. I have always said a lot of things on the list, like AIX, etc, tcl, and url, as the letters (A-eye-ex, ee-tee-see, tee-cee-el, you-are,el), not pronoucing them as words (aches, et-see, tickle, earl). Which is the right way, and which way will not make people look at me like an idiot?
Excellent point, although I still think it is a necessary security policy.
If a customer needs to allow source address's outside the network, simply update the access list. Just remember, you're doing the world a favor.
If you are offering a service to businesses, it would be good policy to notify them before making major configuration changes.
When I had my first job as a network engineer, I discovered that our email server was an open relay. I changed that, only to discover a (large) number of our customers who we did not provide bandwidth for used us as their SMTP relay. I then allowed the entire range (if it was assigned dynamically) of IPs of the ISPs they used (hell if i'm going to talk everyone through changing their SMTP server setting), and had future customers set it up right.
BTW, (to the best of my knowledge) asymetric routing is any routing that may not take the same path to and from the destination. This applies to the majority of routing these days, not just that with a different specified source address than actual source address.
All ISP's should have access lists on their routers allowing traffic out only if the source address is within their network. Directed Broadcasts should be turned off to limit smurfattacks. This itself would cut the problem ten fold.
Slashdot Mirror
My threatening phone calls paid off!
Similar such oppression has occurred at my school. One afternoon, a student was researching the pornography industry in the library, and he was ESCORTED OUT! I couldn't believe such a travesty would occur to someone whom I assume was just hoping to break into that $11 billion industry.
With the porn industry with estimated $11 billion in annual sales (besting the video game industry by $1.6 billion), where's the Porn University?
I feel many universities not only fail to prepare students for the porn industry, but still don't take it seriously.
Every developer should have a guide on how to say the name of their product.
There's a unix pronouciation guide here or here, but the solaris pronunciation is none too specific. I have always said a lot of things on the list, like AIX, etc, tcl, and url, as the letters (A-eye-ex, ee-tee-see, tee-cee-el, you-are,el), not pronoucing them as words (aches, et-see, tickle, earl). Which is the right way, and which way will not make people look at me like an idiot?
Excellent point, although I still think it is a necessary security policy.
If a customer needs to allow source address's outside the network, simply update the access list. Just remember, you're doing the world a favor.
If you are offering a service to businesses, it would be good policy to notify them before making major configuration changes.
When I had my first job as a network engineer, I discovered that our email server was an open relay. I changed that, only to discover a (large) number of our customers who we did not provide bandwidth for used us as their SMTP relay. I then allowed the entire range (if it was assigned dynamically) of IPs of the ISPs they used (hell if i'm going to talk everyone through changing their SMTP server setting), and had future customers set it up right.
BTW, (to the best of my knowledge) asymetric routing is any routing that may not take the same path to and from the destination. This applies to the majority of routing these days, not just that with a different specified source address than actual source address.
While I was reading about DOS attacks and the need for distributed DNS, I never thought I'd come across a post like this.
All ISP's should have access lists on their routers allowing traffic out only if the source address is within their network. Directed Broadcasts should be turned off to limit smurf attacks. This itself would cut the problem ten fold.