You want to know what I think ? I think it's just normal that they choose the to use the shortest path in there internet routing. It's just common sense. So please countries around the world, setup local internet exchanges, the Netherlands already has atleast 6.
I don't understand why people want word-processors in the first place. They are usually the wrong tool for the job. So they are a poor example of what people need anyway.
Actually that's not quiet what happens, AT&T already gets routes for Google, Verisign, Yahoo, etc. from their transit-provider.
Transit-providers should check very closely what they want to accept from there customers. The problem with all of this is ofcourse, the transit-providers peer with other transit-providers, they really can not check every single route they get from them. It's all about the weakest link, if one announces something a lot of others will get it.
For example we peer with Hurricane Electric, do you really think I want to or can check every single one of there 7032 routes they give us ?
So the verification should be automated.
The problem is how to do it.
If DNSSec would really be deployed, we could use that. In a way just like SPF-records are used.
I don't thienk there is a network that is big enough to have Lime Light or Akamai talk to them that doesn't have their own ASN. Also it's a lot easier if they location supports dynamic routing.
I didn't read the summary and read the article instead, I thought it might be interresting. Well not much. But I also think they aren't correct concerning Akamai. For starters, Akamai doesn't use the public internet. Well unless ofcourse they dont' have an agreement with your ISP.
That's why I think some company should offer a per-issue support for Debian/Ubuntu. Not cheap, but good. Not just per phone, but by e-mail too. Maybe a webbased-ticked-system with e-mail updates ?
That's why you give stupid users a linux or unix computer or laptop and no rights and set noexec on/home and/tmp (and make sure they can only write there).
I've not seen any problems with PDF's and non-Adobe-readers on Linux since years.
There is a Evince-package for Debian/MIPS.
So it's probalby just fine.
You want to know what I think ? I think it's just normal that they choose the to use the shortest path in there internet routing. It's just common sense. So please countries around the world, setup local internet exchanges, the Netherlands already has atleast 6.
I don't understand why people want word-processors in the first place. They are usually the wrong tool for the job. So they are a poor example of what people need anyway.
BGP is used to handles announcements of IPv4- and IPv6-routes, so no this is not IPv4-specific.
It's probably easier to just connect to an Internet Exchange, getting a PC-router on 100Mbit port isn't really all that expensive.
That was exactly what I was thinking about when I read the article.
Actually that's not quiet what happens, AT&T already gets routes for Google, Verisign, Yahoo, etc. from their transit-provider.
Transit-providers should check very closely what they want to accept from there customers. The problem with all of this is ofcourse, the transit-providers peer with other transit-providers, they really can not check every single route they get from them. It's all about the weakest link, if one announces something a lot of others will get it.
For example we peer with Hurricane Electric, do you really think I want to or can check every single one of there 7032 routes they give us ?
So the verification should be automated.
The problem is how to do it.
If DNSSec would really be deployed, we could use that. In a way just like SPF-records are used.
Actually some CA's are actually owned by other CA's if I'm not mistaken.
Your transit does not filter out RFC1918 ? That's pretty sad. If I have any choice, which I probably do, I would not choose them.
And check your NAT didn't screw up your source-port-randomisation.
You almost got childish and pedophile in the same sentence, those usually don't go well together.
Even if it doesn't mplayer will. Ironically in Windows I have more proplems with codecs.
I use libswfdec, it doesn't download/run anything by default. It saves me from a lot of annoying flash ads.
I don't thienk there is a network that is big enough to have Lime Light or Akamai talk to them that doesn't have their own ASN. Also it's a lot easier if they location supports dynamic routing.
I didn't read the summary and read the article instead, I thought it might be interresting. Well not much. But I also think they aren't correct concerning Akamai. For starters, Akamai doesn't use the public internet. Well unless ofcourse they dont' have an agreement with your ISP.
I wanted to ask, does it run Linux, but the answer is also usually: yes
The default is actually to give this error, someone didn't change the default.
It depends ARP spoofing is just confined to the broadcast-domain (possible a VLAN), while a DNS-server probably is used by a much broader 'audiance'.
A server at a hosting-provider might be a nice place for this exploit. But everyone in the know, already knew this was a possible target.
That's why I think some company should offer a per-issue support for Debian/Ubuntu. Not cheap, but good. Not just per phone, but by e-mail too. Maybe a webbased-ticked-system with e-mail updates ?
It has one open port: avahi-daemon atleast on the Desktop.
It's in the article: they got the SQL-server on an academic-license and 50 computers for the same shoe-string butget.
That's why you give stupid users a linux or unix computer or laptop and no rights and set noexec on /home and /tmp (and make sure they can only write there).
There is also a flash-plugin for Linux
There also seems to be a MSN-update available, because I had an e-mail about that too.