But in 10 years, every new car sold in the US, including the lowest-end Fiesta, will have options for some degree of automated driving. At the very least, there will be a driverless highway mode.
Why does everyone want to not drive? I find driving to be a particularly enjoyable task, hell I don't even mind being stuck in traffic as long as I have NPR/CBC or decent podcasts to listen to.
I would prefer to pay them in Ningi.
It kind of begs the question about what the US is still doing in South Korea anyhow. South Korea is a rich country. They can afford their own defense, but its convenient for them for Uncle Sam to pick up the tab. I have stood on the North side of the DMZ and it is clear that the US is just a thorn in the situation making everybody tense. There is no doubt that the South Koreans can adequately defend themselves against any potential "invasion" from the North. There is no reason for the US to be there. The constant presence of US marines on the DMZ make the North Koreans nervous that the South will invade them.
One of the running half-jokes amongst the US troops and marines in South Korea is their primary purpose is to keep the South Korean army in the south, not the other way around. The US influence keeps the south somewhat calm, and acts as a deterrent to the north.
Hah, no. There's a heck of a lot more that goes on there beyond the detention facilities. The real reason though was pretty boring, I was doing some work for the on-base cable company.
This is why there are now standards for what wood can be shipped internationally. All wood packaging entering the United States (Pallets, Cable spools, crates, etc...) is supposed to be fumigated and treated to avoid this. This is one of the things that import inspections actually do catch.
Cellular is pretty much the only reasonable option given the lack of infrastructure. It can be installed completely wireless, aside from power. And finally, an answer to where the old phones can go.
It already is. I was at GTMO on business, and as I was walking into one of the dining facilities, my cell phone rang. Everyone looked at me like I was from Mars, until I explained that as a Canadian phone, it happily roamed onto the Cuban cell network.
Exactly. I work in an environment with very limited bandwidth (1.8Mbps private satellite link servicing ~80 people). SSL by default is the bane of my existence. Right now, I've got Cisco WAAS deployed, and it adds about another 30% of effective capacity to my link, and often more. If everything goes encrypted by default, then I lose all of that. I get no caching gain, no compression gain, nothing, unless I MITM the link, which is evil and causes no end of support headaches.
Encrypt what needs to be encrypted (Authentication mechanisms, financial transactions, etc...) and leave the rest. There's no reason to encrypt cute cat pictures or grandma's chocolate chip cookie recipe.
Sure, but you can verify that the ANI (originating number) belongs to a block that the customer is allowed to use. I have a PRI with two 100 blocks associated with it. I would expect that the telco would verify that the originating number I send to the switch is taken from those 200 valid numbers, if only in case someone calls 911 etc...
Remember, the old Lee Enfield rifles were never designed as sniper weapons. They were battle rifles first and foremost, which just happened to be pretty serviceable as sniper weapons. Additionally, I don't think the rifles to be replaced are scoped rifles. As far as I know they are simply standard Lee Enfield No.4's.
Years ago, I was working in a research camp in the high arctic, and the Arctic Ranger in our camp let me shoot his Lee Enfield. Amazing weapon, and the perfect thing for knocking down a polar bear. The amazing thing with the weapon I used, is that it had graphiti on the stock... Scratched into it, and nearly worn away was written "June 6, 1944." which to me indicates that the weapon had been used at Normandy. The serial number on the barrel also indicated that the weapon pre-dated the Normandy landings as well.
Eh? I always thought of my three sports (Skiing, Sailing, and SCUBA diving) as all being pretty nerdy sports... you need plenty of equipment, often with funny names, and know how to use that equipment properly (some more than others of course... when skiing, if your equipment doesn't work right, you faceplant... in Sailing, you don't go anywhere, and in SCUBA if your equipment isn't working, you might die).
Welcome to the new world...
Am I wrong? That's how I read the whitepaper.
You are wrong. At least one model of Meraki access point has a dedicated radio for this purpose. It attacks other wifi networks through a number of mechanisms, including pretending to be the AP under attack, to attract clients to it, sending spoofed de-auth packets to the clients of other APs, and other techniques to effectively conduct a denial of service attack on whatever other wireless network that may exist within its range. This is precisely what I was encountering on my network.
The main issue I have with this technology is that it can be set to attack all other wifi networks. If it was limited to protecting the SSIDs under its control, I would have less of an issue with it. IE if the wireless system is advertising the SSID "Marriott Convention Center" and someone else sets up a rogue AP using the same SSID, then that's fair game, as the person running the rogue AP is either clueless, or has nefarious intent. If it's attacking "Bob's iPhone Network" then that's another matter.
Because most of the more expensive hotels are catering to business travellers, who will moan, then just expense the cost of getting online.
As much as I dislike Mariott's practice here, this is clearly outside the scope of the FCC's regulatory powers and as far as I know isn't even in violation of their own regulations. First of all, WiFi operates on UNREGULATED spectrum, which means anyone can use, and anyone must accept interference from other users.
Not quite true, the ISM bands are Unlicensed bands, not unregulated. In order to sell equipment used to transmit on these bands, the systems must be type approved. Part of this type approval process includes ensuring that the equipment in question will not cause undue interference to other users on the band. To me, sending rogue de-auth packets constitutes interference.
In Meraki's Air Marshal Whitepaper, they explicitly state on page 8 that Unauthorized containment is prosecutable by law (subject to the FCC’s Communications Act of 1934, Section 333, ‘Willful or Malicious Interference’)..
I actually had this particular issue affect me. As a volunteer, I operate a community-wide network, including a widespread wifi network, at a retreat centre high in the mountains of WA. At this time, there is a significant mine remediation project going on in our valley, so we have leased out several buildings to the construction companies, who setup their own Meraki system. Unfortunately, they enabled Air Marshal, which then went on to attack our wireless network. Despite running WPA-Enterprise on our network, it was still successful in attacking our networks, and rendering them nearly useless. In the end, we had to flex our muscles as the landlord to get the feature disabled.
In my mind, the ability to attack adjacent networks should be illegal, and Cisco and the others should not be permitted to sell this technology to the general public. Rather the systems should simply alert on the presence of other wifi networks, and assist in locating them. Also, the wifi standards should really be updated to fix this type of vulnerability... in a WPA-Enterprise environment, clients should only respond to a de-auth packet encrypted/signed with the session key between the client and the AP its connected to.
Adding to your insightful commentary, I do NOT want anyone to access the programming I have setup on my devices because I do not want anyone with possibly malevolent intentions being able to guess when I am home/on vacation.
Huh? How would accessing the programming tell when you were on vacation? The program/configuration that controls your stuff is stored on the device itself, not stored/run in the cloud. The only information stored in the cloud is how your remote/system is configured, not its state. Once you configure the device, if you're exceedingly paranoid, you can always firewall it off from the outside world, and it will continue to work.
Kleeneness is next to Godelness.
