nelz wrote:Ombra wrote:Yes, CONFIG_INTEL_TXT "can be used to prevent changes to the kernel for security reasons." What apologists always seem to forget to mention is them other far less benign things it can be used for.
The same applies to kitchen knives, that's no reason to get rid of them.
CONFIG_INTEL_TXT is an OPTION that can be used by those building custom kernels for use in their corporate environment, it is not intended to be used, nor is it used, by standard desktop distros.
It is there for the owner of the computer to prevent its misuse, not for someone other than the owner to control your use of it.
Your trying to link anything security related to DRM is as bad as the opposite stance taken on "secure boot" where the name implies that disabling it makes the computer insecure and therefore that operating system that need it disabled (i.e. Linux) are somehow less secure than good old Windows.
wyliecoyoteuk wrote:Actually, that is just a list of all Intel related items, if you remove all of them you will probably end up with a non-functioning system.
Rhakios wrote:wyliecoyoteuk wrote:Actually, that is just a list of all Intel related items, if you remove all of them you will probably end up with a non-functioning system.
I said it was a way of finding one item that had cropped up in this discussion, I didn't say that it didn't find other things as well (of course it did, given the search terms). Why do people get so nit-picky?
wyliecoyoteuk wrote:I wasn't criticising your post, just explaining it out to the OP, who seemed to have assumed that it was ALL DRM
Rhakios wrote:It wasn't intended to be a specific indication of all the DRM in the kernel, I was just showing where you would find what's compiled into your kernel (in the config file in boot) and a way of locating one particular thing that has happened to come up during the discussion. This happens to be an Ubuntu system and as you can see the offending Intel entry is compiled in, on the other hand, it's running on an AMD processor, so I don't expect it's doing anything.
Overall, I'd be inclined to load the config file into a text editor and then use Find to look for offending entries, then when you want to recompile the kernel you can just change those entries.
Rhakios wrote:wyliecoyoteuk wrote:I wasn't criticising your post, just explaining it out to the OP, who seemed to have assumed that it was ALL DRM
Not the way I read his reply, but still. It does show all the Intel entries, including some that might be bothersome for those worried about "DRM".
Anyway, if one's first attempt to compile a kernel from source boots properly, one just hasn't been trying hard enough.
Ombra wrote:Don't expect too much from AMD processors. I've been running across some distasteful info on them, that suggests they have at least begun to join the DRM fanclub. Looks like AMD-V and maybe VT-x or VT-d is in the PhenomII x6. Have to research it more.
lok1950 wrote:As nelz has mention roll your own kernel from the source code leaving out the doggy bits lots of documentation on the web on doing that for just about all distros but you are being at bit paranoid as there is no current implementation of DRM on Linux mainstream distro kernels,it is a possibility but remote as there is no need for it in most home/commercial installations so in their policy distro's do not include those modules of the kernel to keep it's size down.
Enjoy the Choice
Rhakios wrote:You could always start with gNewSense, if it's good enough for RMS it should meet at least some of your needs.
Users browsing this forum: Yahoo [Bot] and 1 guest