Again this speculation needs to end. How exactly does this certificate arragement work. Will Verisign even sign an intermediate certificate to openSUSE or any other developer for that matter? What Jim points out is very valid. Let's say each kernel/complete packaged os release requires a unique certificate. Let's put money and whatever aside. If I want to go on the hypothetical future OBS to build an OS, I go through verisign and get the certificate, let's say that takes 24 hours, once I get that certificate would it be valid to boot on the ARM PC? Or does then the certificate holder have to go through a process to get their certificate included with the hardware vendor's product?
there's an extra hassle to do so.
Given that, I'd also expect that Microsoft would sell a virtualization solution for desktops. Why should they lose revenue to VMware Workstation and users to Oracle VM VirtualBox?
On Wed, Jun 6, 2012 at 1:21 AM, C
wrote: Swapnil has written an interesting blog post about the whole RedHat and UEFI thing that has been floating in the last day or so...
http://www.muktware.com/3699/secure-boot-uefi-fedora-red-hat-99-ubuntu-micro...
What are we as openSUSE going to do here? Do we pony up the $99 for the key registration fee? (my vote would be yes) Do we ignore it? Has anyone thought about this yet?
C. -- openSUSE 12.1 x86_64, KDE 4.8.3 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-- Twitter: http://twitter.com/znmeb Computational Journalism Server http://j.mp/compjournoserver
Data is the new coal - abundant, dirty and difficult to mine. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org