2 ms·
I'd say that we're duty-bound, not to knowingly release insecure software, or at least, put big red "cigarette warning" labels on the packages. If the only way
by ChrisMarshallNY 3y ago
I'd say that we're duty-bound, not to knowingly release insecure software, or at least, put big red "cigarette warning" labels on the packages.
If the only way we can make cheap software, is to make insecure software, then maybe we shouldn't be selling cheap software.
It's a conundrum. If we don't sell cheap stuff, someone else will, and eat our lunch.
That's one reason that a regulated industry is sometimes the only solution (an unpopular stance -as evidenced by the almost instantaneous reaction to this comment).
- deleted 3y ago[deleted]
- Buttons840 3y agoI wonder how this would look in a lawsuit. Claiming that a company is liable for security flaws in their software is a lot easier when the company sells solutions to those security flaws as a premium product.
- mistrial9 3y agopolitely disagree -- this framing misses an orthogonal component.. purpose.. a simple example is a desktop publishing app on a desktop computer. Minus complicated fringe cases, the purpose of the software and its setting are not really related to security in the way that communications on a network are related to security. The furor and obsession with networked communication has obscured simplicity in so many cases.
- ChrisMarshallNY 3y agoThat’s an excellent point. Not sure I’d think of it as a “disagreement,” though; just another angle.