Okay, first of all, this won't require anyone to install any client application anywhere. That's the point. The filters would steer away malware at the router, before it even reaches the user.
Secondly, this is a good idea, so long as it's implemented only at gateways to private networks. Signature based filtering is bound to block some legit traffic, and network admins need to keep that in mind when implementing this kind of functionality.
Third, Cisco routers already do this to some extent. You can block some malware using NBAR (network based application recognition) and ACL's. (It's a good thing. It helped me make Code Red go away on my network back in the day.) This feature is a logical next step.
And finally, does anyone actually read these things before they post them (michael)? Even if you overlooked the grammatical errors, the factual inconsistencies alone should have kept this thing from ever hitting the front page.
When Code Red was at its worst, Comcast took it upon itself to filter inbound http requests to some (all?) of its subscribers. While this did prevent new IIS infections, it also disrupted service for a large number of people running more secure web servers, myself included. The way I saw it, I was being forced to suffer for my neighbors' stupidity. I lost the freedom to run a personal web server because there were too many morons sharing the network with me.
I like the idea of an ISP offering "secure" service as a [free] option. I even like the idea of enabling it by default, and forcing the customer to explicitly remove the feature if they don't want it. What I don't like is having my service crippled because someone else is too careless or clueless to secure their PC.
On the other hand, this would likely have the undesirable side effect of teaching users that they need not worry about security. "Why bother keeping my OS up to date? Isn't it my ISP's job to take care of me?"
One thing that struck me from my quick review of the referenced thread is that the moderators (TiVo reps) sure did take an insolent tone in the forum. Obviously, a lot of people are upset with them. I'd be upset, too, if I had one of these things. The fact that TiVo's response is so inflamatory ("screw you guys, you're not really our customers") doesn't help the situation.
How about putting a good face on your company, guys? Try being a little consolatory. Apologize for any confusion. Explain what provisions in the license agreement allowed TiVo to disable unsubscribed boxes. Thank the users that are currently paying for your service. Try making the rest of us feel like we might want to do business with your company at some point.
I, for one, won't be purchasing a TiVo unit anytime soon.
Get a Herman-Miller Aeron, the chair of choice for countless now-defunct dotcoms. You should be able to find one reasonably priced on E-Bay. I can work 16 hour days in mine without wanting to die. Also, a good footrest will help a lot.
You should also try getting out more. Find a hot geekgrrl that gives good back rubs.
I found some of my old UUCP map entries from around 1994 in comp.mail.maps. It was fun to browse through some of the other users in those files and remember people that I haven't talked to in 6 or 7 years...
During my last job hunt, I got several serious offers from SLC. I barely even considered them. The pay and benefits were competitive, but the community wasn't. I don't go to the bar that frequently, but I sure would hate to live somewhere where I didn't have the option.
If you want me to work in Salt Lake City, you'd better pay me enough to get the hell out of there with great regularity. We're talking 12 weeks paid vacation and a big buffer in my salary for plane tickets and what-not. Otherwise, I'm going to take the job in the city without a religious bug up its butt.
I'm currently in the process of implementing an IP telephony solution at work. In discussing new technologies with one of our consultants, I asked how far away we were from being able to carry around wireless IP phones. He said that Cisco is already working on (or has acquired someone that is working on) integrating 802.11b with cellular/PCS phones. From what he was saying, within a year or so, you'll be able to get cell phones that will double as wireless IP phones while on your WLAN campus. Cool stuff.
Also, Ann Arborites are putting together a city-wide WLAN. If you're in Ann Arbor, and you're interested in participating, subscribe to this egroup.
If the $2 billion Linux industry doesn't like Linus's kernel, they can write their own. No one is holding a gun to anyone's head here. We use Linus's kernel because we like it.
I've had countless problems like this with Sprint. The only reason I still have a Sprint phone is that I've handed out hundreds of business cards with my mobile number on them. *GRR!*
At one point, I got a text message from Sprint at 4:00 in the morning saying that I'd reached my "spending limit" and that my phone was disconnected. Talk about annoying -- not only had their billing system screwed up and wrongfully cut off my service, but they woke me up to tell me about it. I didn't have to sit on hold for half an hour to talk to someone about it, though, because at 4:00 in the morning, there's no wait. At one point in the conversation I asked why they couldn't wait until a more reasonable hour to send me that text message. The rep actually told me (can you believe this?) that I should have shut my phone off before I went to sleep if I didn't want it to wake me up.
Sprint's customer service SUCKS, and if you live in Southeast Michigan/Northwest Ohio, you know that they oversold their service here -- 75% of my incoming calls are met with "All Circuits Busy".
I'm happy with the SCH-8500, though, FWIW.
For anyone who is having trouble with Sprint's customer service center: If you think you're right, and that the person you're talking to is smoking tainted crack on his breaks, ask to speak to a supervisor. If you get the impression that his supervisor is smoking the same crack, ask to speak to another supervisor. If you get the same response, do this:
Call 913-624-3000, Sprint's corporate HQ in Kansas City. Ask the switchboard operator to transfer you to "Executive Services for PCS". Exec Services is an office of about 25 people that handles customer service requests referred by upper management. If you write a letter to a VP complaining about how horrible their call center is, they'll have you call these guys. The people I've talked to in the Executive Services office were actually intelligent, and resolved my complaints to my satisfaction with no hold-time and no stressful arguments with poorly trained monkeys.
Unfortunately, Sprint doesn't have the resources to train all of its call center reps to behave like the Exec Services office reps. If you're having problems, go through the *2 call center first -- don't call Executive Services until after you've already told their 'customer care' center to suck your balls. I know it's tempting to want to talk to someone with a brain right off the bat, but this system will only continue to work as long as it isn't abused.
Long story short: Don't go with Sprint PCS unless you like jumping through hoops and can tolerate poor performance.
The Internet Society probably isn't too happy about this. They released a statement on November 8th encouraging NSI to back off and let the IETFIDN WG do its job.
Also, there are companies that are already currently operating in this market, including WALID, which is taking registrations for Arabic domain names (AND RESOLVING THEM), and will soon be adding Hindi, Tamil, and two Chinese scripts before moving into other markets.
Slashdot Mirror
RTFA. This $16.2 billion is for praying our way to Mars.
I'm lazy, so I just Googled the answer.
Okay, first of all, this won't require anyone to install any client application anywhere. That's the point. The filters would steer away malware at the router, before it even reaches the user.
Secondly, this is a good idea, so long as it's implemented only at gateways to private networks. Signature based filtering is bound to block some legit traffic, and network admins need to keep that in mind when implementing this kind of functionality.
Third, Cisco routers already do this to some extent. You can block some malware using NBAR (network based application recognition) and ACL's. (It's a good thing. It helped me make Code Red go away on my network back in the day.) This feature is a logical next step.
And finally, does anyone actually read these things before they post them (michael)? Even if you overlooked the grammatical errors, the factual inconsistencies alone should have kept this thing from ever hitting the front page.
When Code Red was at its worst, Comcast took it upon itself to filter inbound http requests to some (all?) of its subscribers. While this did prevent new IIS infections, it also disrupted service for a large number of people running more secure web servers, myself included. The way I saw it, I was being forced to suffer for my neighbors' stupidity. I lost the freedom to run a personal web server because there were too many morons sharing the network with me.
I like the idea of an ISP offering "secure" service as a [free] option. I even like the idea of enabling it by default, and forcing the customer to explicitly remove the feature if they don't want it. What I don't like is having my service crippled because someone else is too careless or clueless to secure their PC.
On the other hand, this would likely have the undesirable side effect of teaching users that they need not worry about security. "Why bother keeping my OS up to date? Isn't it my ISP's job to take care of me?"
One thing that struck me from my quick review of the referenced thread is that the moderators (TiVo reps) sure did take an insolent tone in the forum. Obviously, a lot of people are upset with them. I'd be upset, too, if I had one of these things. The fact that TiVo's response is so inflamatory ("screw you guys, you're not really our customers") doesn't help the situation.
How about putting a good face on your company, guys? Try being a little consolatory. Apologize for any confusion. Explain what provisions in the license agreement allowed TiVo to disable unsubscribed boxes. Thank the users that are currently paying for your service. Try making the rest of us feel like we might want to do business with your company at some point.
I, for one, won't be purchasing a TiVo unit anytime soon.
Get a Herman-Miller Aeron, the chair of choice for countless now-defunct dotcoms. You should be able to find one reasonably priced on E-Bay. I can work 16 hour days in mine without wanting to die. Also, a good footrest will help a lot.
You should also try getting out more. Find a hot geekgrrl that gives good back rubs.
... that let u crawl...
'U' is a letter, not a word. Did you really save yourself ("urself", for the Y-O- challenged) that much time by neglecting the 'Y' and 'O'?
I found some of my old UUCP map entries from around 1994 in comp.mail.maps. It was fun to browse through some of the other users in those files and remember people that I haven't talked to in 6 or 7 years...
... remember when? :-)
During my last job hunt, I got several serious offers from SLC. I barely even considered them. The pay and benefits were competitive, but the community wasn't. I don't go to the bar that frequently, but I sure would hate to live somewhere where I didn't have the option.
If you want me to work in Salt Lake City, you'd better pay me enough to get the hell out of there with great regularity. We're talking 12 weeks paid vacation and a big buffer in my salary for plane tickets and what-not. Otherwise, I'm going to take the job in the city without a religious bug up its butt.
I'm currently in the process of implementing an IP telephony solution at work. In discussing new technologies with one of our consultants, I asked how far away we were from being able to carry around wireless IP phones. He said that Cisco is already working on (or has acquired someone that is working on) integrating 802.11b with cellular/PCS phones. From what he was saying, within a year or so, you'll be able to get cell phones that will double as wireless IP phones while on your WLAN campus. Cool stuff.
Also, Ann Arborites are putting together a city-wide WLAN. If you're in Ann Arbor, and you're interested in participating, subscribe to this egroup.
If the $2 billion Linux industry doesn't like Linus's kernel, they can write their own. No one is holding a gun to anyone's head here. We use Linus's kernel because we like it.
[smuj@pepper ~]$ ssh -l root admin.yourcar.com /usr/bin/honk -o /dev/horn /usr/bin/speed /dev/axle /dev/console
root@admin.yourcar.com's password:
admin#
admin#
Current Speed: 73MPH
admin# rm -f
admin# echo "Hahahahaha" >
admin# exit
Geez, I hope this flops. If it doesn't, I've got about 120 DVD's that I'll be boxing up in the basement with my 8-tracks. :-)
I've had countless problems like this with Sprint. The only reason I still have a Sprint phone is that I've handed out hundreds of business cards with my mobile number on them. *GRR!*
At one point, I got a text message from Sprint at 4:00 in the morning saying that I'd reached my "spending limit" and that my phone was disconnected. Talk about annoying -- not only had their billing system screwed up and wrongfully cut off my service, but they woke me up to tell me about it. I didn't have to sit on hold for half an hour to talk to someone about it, though, because at 4:00 in the morning, there's no wait. At one point in the conversation I asked why they couldn't wait until a more reasonable hour to send me that text message. The rep actually told me (can you believe this?) that I should have shut my phone off before I went to sleep if I didn't want it to wake me up.
Sprint's customer service SUCKS, and if you live in Southeast Michigan/Northwest Ohio, you know that they oversold their service here -- 75% of my incoming calls are met with "All Circuits Busy".
I'm happy with the SCH-8500, though, FWIW.
For anyone who is having trouble with Sprint's customer service center: If you think you're right, and that the person you're talking to is smoking tainted crack on his breaks, ask to speak to a supervisor. If you get the impression that his supervisor is smoking the same crack, ask to speak to another supervisor. If you get the same response, do this:
Call 913-624-3000, Sprint's corporate HQ in Kansas City. Ask the switchboard operator to transfer you to "Executive Services for PCS". Exec Services is an office of about 25 people that handles customer service requests referred by upper management. If you write a letter to a VP complaining about how horrible their call center is, they'll have you call these guys. The people I've talked to in the Executive Services office were actually intelligent, and resolved my complaints to my satisfaction with no hold-time and no stressful arguments with poorly trained monkeys.
Unfortunately, Sprint doesn't have the resources to train all of its call center reps to behave like the Exec Services office reps. If you're having problems, go through the *2 call center first -- don't call Executive Services until after you've already told their 'customer care' center to suck your balls. I know it's tempting to want to talk to someone with a brain right off the bat, but this system will only continue to work as long as it isn't abused.
Long story short: Don't go with Sprint PCS unless you like jumping through hoops and can tolerate poor performance.
A few notes...
The Internet Society probably isn't too happy about this. They released a statement on November 8th encouraging NSI to back off and let the IETF IDN WG do its job.
Also, there are companies that are already currently operating in this market, including WALID, which is taking registrations for Arabic domain names (AND RESOLVING THEM), and will soon be adding Hindi, Tamil, and two Chinese scripts before moving into other markets.