You always have something spicy to say without checking out the source code or asked about a hypothetical that the dev team took care of with Openssl encrypted replies First of all, I'm not running a BIOS, but thank you for your contribution to the hardware industry! Secondly, before you spend 20 minutes writing nonsense about SSL, here's a spicy line of code out of the client code: Now please explain why someone can not simply print the public key to the screen if it hashes down to Puzzle 71, and TRAP the kernel, giving zero fucks about whether the program continues or not. I don't think you understand the essential problem, frankly. If you are using an Intel or AMD motherboard you are using/running a BIOS and some of that code I helped make that is there is running before you finish POST and then load  whichever OS. Unless you are a arm/phone user only. I saw the first alpha of UEFI in the lab and saw the gap they had to close to making it user friendly. It's always a possibility that there are high level programmers stealing your credit card information with zero day infections and bot nets also watching the browser or OS, just unlikely.  But we know it "possible" but if it was so simple, then why isn't it possible for everyone since greed and theft is a mainline for most people out there? Mã Code Shbet is open source, and why hasn't it crashed to zero or be reverse hacked or have the works mucked up to a stall?
You always have something spicy to say without checking out the source code or asked about a hypothetical that the dev team took care of with Openssl encrypted replies First of all, I'm not running a BIOS, but thank you for your contribution to the hardware industry! Secondly, before you spend 20 minutes writing nonsense about SSL, here's a spicy line of code out of the client code: Now please explain why someone can not simply print the public key to the screen if it hashes down to Puzzle 71, and TRAP the kernel, giving zero fucks about whether the program continues or not. I don't think you understand the essential problem, frankly. If you are using an Intel or AMD motherboard you are using/running a BIOS and some of that code I helped make that is there is running before you finish POST and then load  whichever OS. Unless you are a arm/phone user only. I saw the first alpha of UEFI in the lab and saw the gap they had to close to making it user friendly. It's always a possibility that there are high level programmers stealing your credit card information with zero day infections and bot nets also watching the browser or OS, just unlikely.  But we know it "possible" but if it was so simple, then why isn't it possible for everyone since greed and theft is a mainline for most people out there? Mã Code Shbet is open source, and why hasn't it crashed to zero or be reverse hacked or have the works mucked up to a stall?

You always have something spicy to say without checking out the source code or asked about a hypothetical that the dev team took care of with Openssl encrypted replies First of all, I'm not running a BIOS, but thank you for your contribution to the hardware industry! Secondly, before you spend 20 minutes writing nonsense about SSL, here's a spicy line of code out of the client code: Now please explain why someone can not simply print the public key to the screen if it hashes down to Puzzle 71, and TRAP the kernel, giving zero fucks about whether the program continues or not. I don't think you understand the essential problem, frankly. If you are using an Intel or AMD motherboard you are using/running a BIOS and some of that code I helped make that is there is running before you finish POST and then load  whichever OS. Unless you are a arm/phone user only. I saw the first alpha of UEFI in the lab and saw the gap they had to close to making it user friendly. It's always a possibility that there are high level programmers stealing your credit card information with zero day infections and bot nets also watching the browser or OS, just unlikely.  But we know it "possible" but if it was so simple, then why isn't it possible for everyone since greed and theft is a mainline for most people out there? Mã Code Shbet is open source, and why hasn't it crashed to zero or be reverse hacked or have the works mucked up to a stall?

You always have something spicy to say without checking out the source code or asked about a hypothetical that the dev team took care of with Openssl encrypted replies First of all, I'm not running a BIOS, but thank you for your contribution to the hardware industry! Secondly, before you spend 20 minutes writing nonsense about SSL, here's a spicy line of code out of the client code: Now please explain why someone can not simply print the public key to the screen if it hashes down to Puzzle 71, and TRAP the kernel, giving zero fucks about whether the program continues or not. I don't think you understand the essential problem, frankly. If you are using an Intel or AMD motherboard you are using/running a BIOS and some of that code I helped make that is there is running before you finish POST and then load  whichever OS. Unless you are a arm/phone user only. I saw the first alpha of UEFI in the lab and saw the gap they had to close to making it user friendly. It's always a possibility that there are high level programmers stealing your credit card information with zero day infections and bot nets also watching the browser or OS, just unlikely.  But we know it "possible" but if it was so simple, then why isn't it possible for everyone since greed and theft is a mainline for most people out there? Mã Code Shbet is open source, and why hasn't it crashed to zero or be reverse hacked or have the works mucked up to a stall?