News for hackers. Stuff that matters.
Re:Dumb Ideas in Computer Security (2005) by TeMPOraL on Friday January 02, 2015 @05:38PM (#8828966)
I totally agree. For a long time I had this feeling that improving security is basically killing all fun and joy. When I was learning to code, there was no such thing as Data Execution Prevention on Windows, and you could even access and write to memory of another process. What that meant was interesting and fun things. For instance, you could write programs that totally tweaked software that was poorly written or that you just didn't like. You could make computers do your bidding instead of being locked in the ways of thinking of original software authors. Every single improvement in the field of computer security was, and is, slowly eroding this fun.

Back then I thought about it mostly as killing fun; nowdays I consider it killing of flexibility. Computers are increasingly being locked down and dumbed down to prevent users from doing anything the authors don't want them to do. It's especially visible in mobile. I can understand the rationale behind it, that an average Joe needs protection from the heavily complicated magic box in front of him. But for those who understand and know how to use that magic, security means less joy, less flexibility, less power.

Re:Dumb Ideas in Computer Security (2005) by userbinator on Friday January 02, 2015 @09:06PM (#8829642)
Indeed, every time I hear advocacy of "safer" languages, formal verification, heavily-constrained runtime environments, etc., it's a rather odd feeling; on one hand I think there are definite advantages (e.g. I don't want government backdoors as much as anyone else advocating strong security), but on the other hand, I can't help but think that the strong security of these systems can often be used against the user. One of the most common examples of this is jailbreaking - which basically wouldn't exist at all if systems were built with strong proofs of security. There are also those who think the problem is at the policy level and strongly secure systems should be strongly advocated anyway, but since there has been very little in the way of laws protecting users' freedom to control the hardware and software they own (and instead the opposite has been happening), often the most practical way to freedom is insecurity. As that famous saying goes, "those who give up freedom for security deserve neither."

I can understand the rationale behind it, that an average Joe needs protection from the heavily complicated magic box in front of him. But for those who understand and know how to use that magic, security means less joy, less flexibility, less power.

This might be an issue of societal attitudes - there seems to be much emphasis on systems being "easy to use" without any knowledge, which ultimately leads to systems in which the user has absolutely no control; after all, the easiest system to "use" is one that makes all the decisions for the user. And as users start making fewer decisions because of this automation, the "advanced features" that they would otherwise use get used less, leading to their eventual removal. The decreasing motivation of users to learn about and control their systems causes systems to allow less control (and consequently become easier to "use"), feeding back to decreased motivation of the users in a vicious cycle. The biggest concern is that the developers of the future are the users of today, so the increased "automation"/decreased flexibility feeds them too.

It's hard to find a solution to this, but I think it's one that will need to involve a huge shift in societal attitudes - from "I don't know how to do X but Y will do it for me so I don't care about learning more" to "I don't know X so I'll learn how, then find a way to use Y to do it better".

Re:Dumb Ideas in Computer Security (2005) by afarrell on Friday January 02, 2015 @09:45PM (#8829718)
The problem is that learning how to do things is really expensive for many people. I think the fundamental problem isn't user-centered design but lopsided bifurcation in who the users are.

For a product like a recipe/grocery app, I genuinely don't care about abstraction layers it uses below its UI. I just want my wife and I to plan our meals and do our grocery shopping in a time-efficient way. I don't want to run into situations where "it doesn't work" and I have to figure out why.

For a product like gulp.js, vim, or google chrome's layout engine, I really do care about those abstraction because I am trying to build things with them and I expect that I'll run into situations where "it doesn't work" and I have to figure out why. So give me the conceptual tools to do so. If that means source-diving without clear documentation about how to do that spelunking, fine. I'll procrastinate on it and be unhappy, but I'll do it. So starting from that perspective, any improvement on the fixing-things experience is a blessing rather than an irrelevance.

But some things necessarily straddle both. It would be very difficult to fund a hardware manufacturing supply chain for a phone without mass-market appeal. Yet the app ecosystem that produces much of the value of a smartphone requires some ability to do things the phone manufacturer did not anticipate, even if it within a playpen.

Re:Dumb Ideas in Computer Security (2005) by digi_owl on Saturday January 03, 2015 @03:08PM (#8831811)
Another issue is that modern personal computers make it massively easy to hide what it is doing.

The phone before me seems to be idle as best i can tell, but if i fire up a process viewer i see 20+ ongoing tasks.

This in contrast mechanical devices of old that only did the one task they were built to do, and were very "loud" (not just auditory) about when they were doing it.

Heck, recently i found myself wondering about hooking up some kind of audio system to wireshark and play around with having various packet traffic produce various sounds. This after reading about a guy that set up his phone to play certain noises to his hearing aid based on the characteristics of wifi networks encountered when walking around town.

Consider also that we suspect something is up with a car or similar because the steering wheel develops an odd rattle, or some unfamiliar noise is heard when doing certain things.

Never mind the old analog modem handshake where we could tell by experience when we got a bad connection, compared to the modern variant where we have to check some "dashboard" to tell if we are connected at all.

Re:Dumb Ideas in Computer Security (2005) by zrm on Saturday January 03, 2015 @04:33AM (#8830335)
> And as users start making fewer decisions because of this automation, the "advanced features" that they would otherwise use get used less, leading to their eventual removal.

That much is probably inevitable. When they build a house they provide you a light switch that will cause the room to be illuminated and then put up drywall everywhere which makes it less easy for you to add new switches and outlets. What they don't do is fill the walls with cement and epoxy everything with a screw thread and then, when a light bulb burns out which is permanently affixed to the frame of the building, tell you to buy House 2.0.

It's one thing to not spend time adding a feature most people don't use, but which the owner can add later with some work. It's quite another thing to actively spend effort to prevent the owners from exercising control over their own devices.

Re:Dumb Ideas in Computer Security (2005) by digi_owl on Saturday January 03, 2015 @03:10PM (#8831820)
Something like how it becomes harder and harder to jailbreak android phones, while at the same time Chromebooks ship with a "developers switch"?

I find myself thinking of Doctorow's arguments about "(civil) war on computing"...