[...]
> Would open-source prevent this kind of thing? Probably.
I don't think I could have made the argument better than you have.
The point isn't that all closed source software does this, or even that most does it. The point is that when you cannot control the software, the abuse can happen. Anyone who has power can abuse it, which means that if you cede control over software in your router to Cisco, you have to trust Cisco not to abuse it. If you don't, then you don't have to worry.
You might be breaching the terms & conditions of their cloud stuff, but you could simply choose not to use it.
Open source protects the technical literate people, but it's not the silver bullet that solves this issue. Raising awareness and pushing back is at least as important and that's possible with closed source as well.
Yes, pushing back is possible with closed source as well.
The real question becomes, which is harder? and for who? To push back at closed source, you'd have to be a big consumer of them or atleast big enough to be able to sue the vendor. If you're an individual, you're in real trouble. Of course, there are people who play both roles.
And I see Open-source as the best enabler for technical individuals. As far as i can see, of course.
Again, the problem --Cisco wanting access to your data-- does not have a direct causation link to the fact that their software is closed. No such connection exists.
Would open-source prevent this kind of thing? Probably. In this case, someone has to make the hardware, supply and maintain the infrastructure, so the problem is probably a little more complex than the simple contrast between closed and open source. There really aren't a lot of large open-source-everything projects out there (hardware + software + mechanical + whatever else) to know how this would play out.
Hardware, as a business, is really capital intensive. Software isn't. A college student in a dorm can sit down and write software that gets distributed to millions and reaches every corner of the world. And the cost of doing so is virtually nothing.
To replicate this in hardware is almost impossible (yet). There's a lot more to it than just designing and building it. There's support, warranties, regulatory requirements, etc.
Here's a dumb example: Who wants to be responsible for the lawsuit when an ill-designed piece of hardware kills someone because it does not deal with high-voltages in a safe manner?
Or another one: Who wants to be responsible for a recall of thousands or even millions of devices if they are found to be defective in some way?
Again, regardless of the contrast between hardware and software I don't think that this issue can be used to champion the FOSS flag.