The difference is that in the Linux example, the user controls the keys that is necessary to determine what such a state is, whereas with DRM the user necessarily does not.
It's literally DRM, and I think it's a good thing, because it lets me protect sensitive information from theft.
This is the same kind of thing that happened to the "native advertising" people who hide adverts as news stories and wonder why people have come yo loath the term native advertising. They've unintrntionally established a colloquial definition that is actually quite distant from the textbook definition through their abuse. I argue the same has happened to DRM.
No, but we had those systems before, we just call it "security" and "authorization layer". DRM arose, as far as I know, to describe copy-protection mechanisms like SecuROM.
They've unintrntionally established a colloquial definition that is actually quite distant from the textbook definition through their abuse. I argue the same has happened to DRM.
Maybe so, but then I never got the original definition, and I don't understand why there was the need for a new term when authorization layers are old as dirt.
You seem to have an ideological need to call DRM bad in all cases and tell me how every other use of DRM is not "True DRM!", but I'm using it to stop people with access to the server from being able to open certain files even if they somehow break other security features which should prevent them from even getting access to the bits.
I'm not sure how much more DRM you can get than stopping people from viewing content unless they show their credentials to prove they're an authorized user.
Yes, which is why I wrote it's not DRM if you're not trying to protect data from the user itself. In that case, you are.
I'm using it to stop people with access to the server from being able to open certain files even if they somehow break other security features which should prevent them from even getting access to the bits. I'm not sure how much more DRM you can get than stopping people from viewing content unless they show their credentials to prove they're an authorized user.
I'm using the UNIX filesystem permissions for that. Is UNIX DRM now?
As far as I know, DRM as a term arose to describe the technologies that tried to allow the user to view the content while preventing him/her from copying it.
You seem to have an ideological need to call DRM bad in all cases and tell me how every other use of DRM is not "True DRM!"
No, I'm just trying to make sense of the fact that people are using a term in a different way than I've always seen it used, and which happens to be (in my opinion) much less useful, since it turns any authorization layer into "DRM".
I don't think that has anything to do with DRM, can you explain?