GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Its three most controversial features are remote attestation, binding, and sealing. Remote attestation creates an unforgeable summary of the software on a computer, allowing a third party (such as a digital music store) to verify that the software has not been compromised. Sealing encrypts data in such a way that it may be decrypted only in the exact same state (that is, it may be decrypted only on the computer it was encrypted running the same software). Binding encrypts data using the TPM Endorsement Key (a unique RSA key put in the chip during its production) or another 'trusted' key . The first feature is seen as a potential threat to privacy by many, while the second and the third are often seen as a herald to Digital Rights Management systems of unprecedented restrictiveness. Direct anonymous attestation improves privacy, but is still considered insufficient by some.
was looking at nvidia based motherboard
wouldnt be suprised if other motherboards and chipsets crop up soon with it.
was looking at AM2 socket motherboard with Quadro built in video and north bridge. not sure if the security chip is seperate chip that can be toyed with. MSI K9NBPM2-FID and Asus M2NBP-VM
information is on the net. hardware is coming out I would hazard to guess 2007 tech is going to be loaded with DRM and security features that are not kind to linux as if linux had it easy to begin with.
its already adopted by many companies/corporations otherwise it wouldnt be coming out now. big names Intel,AMD,IBM,Microsoft,RedHat,Novell etc.
lots and lots of companies.
When you discover which is the latest-greatest motherboard without that chip, please post. I'll be interested in a board built to accommodate more than 1 processor. Hopefully by the time that board is obsolete, there will be methods or hardware in place to allow a choice of whether or not hardware DRM should be used.
This is bad news for some vista users, I guess, but since many of us will likely never use vista (myself included), I don't see the point in being alarmed. Does anyone see the possibility that the open source world will adopt these weird, greedy, draconian schemes? The linux-oriented companies will almost certainly use it for legitimate security in an enterprise mileu, and it will be an option you can turn off if you don't want it, just as just about everything is now. If the chip is not enabled and utilized restrictively, it will just be there in an easily-forgettable way.
If anything, this technology will drive more people toward linux.
pretty soon we might not even be able to use linux anymore. emails and documents we make won't "work" on other computers, our ISPs might not allow linux computers onto the internet, and it might even be illegal to run an open source OS or application. all the TC/DRM crap is definitely very, very bad news.
This all reminds me of the whole Pentium III ID chip saga, where some unique ID was assigned to each processor, allowing you to be uniquely identified. It seems that it fell by the wayside; hopefully this will too.
Good for you. Keep your blinders on and forge ahead. Don't worry, be happy.
I want a state of the art motherboard pre- Trusted Platform Module Security Chip. There is no way to know exactly what that chip is capable of doing"
i think eerok has a point ...
as long as we remain using only plain text in everything and its open for all on earth to peek at , i see no great problems with that as long as we dont waste our time on silly pc things ...
anyway , it wont be a threat , i mean at least it wont be a "warring" threat , this sort of threat are for other more important worldly issues if we choose to worry about this and that minutely i guess ...
actually i dont understand this one ... for the internet connectivity problem , isnt it sound too far fetched ??