Originally posted by marccollin
View Post
Announcement
Collapse
No announcement yet.
Lenovo Begins Supporting LinuxBoot Firmware With ByteDance
Collapse
X
-
Originally posted by Jonjolt View Post
Last time I checked, both of those are banned in China, why should we allow a hostile regime access to our markets if they will not allow our products in theirs
- Likes 2
Comment
-
You couldn't pay me to use Lenovo products after their 2015 scandal remote-installing adware and spyware through the UEFI.
Anyways though, if the Chinese government wants to compete with the US Government over who can give Linux the most money and improvement -- I don't mind being the winner of such a competition.
Obviously China is trying to bootstrap their own domestic chips and using Linux fits their "communism ideology" even though in practice they are nothing like it.
All the RISC-V stuff feels like an attempt to "get good" from FiveStar (Notice the name mirrors the CCP Flag)
Competition is good for innovation -- so I hope Beagle, Texas Instruments and others turn up the heat and we get some cool SBC shit out of this.
- Likes 2
Comment
-
-
-
Originally posted by Jonjolt View Postwhy should we allow a hostile regime access to our markets if they will not allow our products in theirs
- probably Frédéric Bastiat
Originally posted by ElectricPrism View PostYou couldn't pay me to use Lenovo products after their 2015 scandal remote-installing adware and spyware through the UEFI.
- Likes 1
Comment
-
SemiAccurate is already going as calling it the 'Pluton Malware'. They declare Intel is still safe from it but AMD and Qualcomm have already baked it in. Suffice it to say, I will not be buying any of the Ryzen 6000 processors and try not to get the Qualcomm models. Really don't need any baked in Rootkits from Lenovo, ByteDance, SuperMicro (past), AMD or Qualcomm.
https://www.semiaccurate.com/2021/12/01/qualcomm-8cx-gen-3-too-dangerous-to-deploy/
- Likes 2
Comment
-
I would like to point that I'm definitely going to take a second look at the ByteDance/Lenovo involvement. All of this is such b.s. that we all have to examining source code at the CPU level and CPU diagrams. I'll admit I have a lot yet to learn and may not be correct at all. I've only just recently been able to remove all the SSH Private keys from all my Linux and Windows machines using (import into @keepassxc mgr. which has a CLI version, also). Works with Pageant/Putty/WinSCP. Microsoft's included OpenSSH agent in Win 10, 11, Server and WSL is still broken and Windows Update wont fix it. The latest Powershell Github ssh-agent works though . . . but NOT in WSL still. But at least its working now. No more passwords or private keys, no thanks to Microsoft or TPM.
I am doing everything I can possibly think of to keep my cryptographic keys out of Pluton, TPM, the cloud and anywhere else where someone want to 'help' me and store my keys for me.
Comment
Comment