Fedora

A quick note to remind ThinkPad X1 Carbon 6 users that Lenovo just released a new firmware for the Thunderbolt on this laptop. And, it’s available via fwupd if you run Fedora (possibly also available on Ubuntu). [root@benji ~]# fwupdmgr update • Thunderbolt Controller has the latest available firmware version Upgrade available for Embedded Controller from 0.1.20 to 0.1.21 20KHCTO1WW must remain plugged into a power source for the duration of the update to avoid damage. Continue with update? [Y|n]: Downloading… [***************************************] Decompressing… [***************************************] Authenticating… [***************************************] Updating Embedded Controller…************************************] Scheduling… [***************************************] Successfully installed firmware • Intel Management Engine has the latest available firmware version • SAMSUNG MZVLW256HEHP-000L7 has no available firmware updates • System Firmware has the latest available firmware version An update requires a reboot to complete. Restart now? [y|N]: All you need to do is rebooting the machine.

It seems like Lenovo releases a new BIOS firmeware every month for its ThinkPad, at least for the ThinkPad P1 Gen1. On July 21, the BIOS firmware version 1.31 was released. CHANGES IN THIS RELEASE Version 1.31 [Important updates] - Address CVE-2020-0548, (https://cve.mitre.org//cgi-bin//cvename.cgi?name=CVE-2020-0548) - Address CVE-2020-0549, (https://cve.mitre.org//cgi-bin//cvename.cgi?name=CVE-2020-0549) - Address CVE-2020-0543, (https://cve.mitre.org//cgi-bin//cvename.cgi?name=CVE-2020-0543) [New functions or enhancements] - Updated the CPU microcode. [Problem fixes] - Fixed an issue where Force PXE boot by Intel AMT did not work. This firmware supports both ThinkPad P1 Gen1 and ThinkPad X1 Extreme 1: ...

Update BIOS firmware version 1.9.1 is available for Dell Latitude 7400. This firmware was released on 30 June 2020. It is marked Urgent and contains the following fixes and enhancements: Fixes: Fixed the issue where the system cannot detect the Intel Software Guard Extensions (SGX) device when SGX is enabled. Firmware updates to address security advisory INTEL-SA-00295 (CVE-2020-0531, CVE-2020-0532, CVE-2020-0533, CVE-2020-0535, CVE-2020-0536, CVE-2020-0537, CVE-2020-0538, CVE-2020-0539, CVE-2020-0540, CVE-2020-0545, CVE-2020-0594, CVE-2020-0595, CVE-2020-0596, and CVE-2020-8674). Firmware updates to address the Intel Security Advisory INTEL-SA-00320 (CVE-2020-0543). Firmware updates to address the Intel Security Advisory INTEL-SA-00329 (CVE-2020-0548 and CVE-2020-0549). Firmware updates to address the Intel Security Advisory INTEL-SA-00322 (CVE-2020-0528 and CVE-2020-0529). Enhancements: ...

I’ve been meaning to pick up a micro-controller and work on it again. About 5 years ago when I first encountered Arduino, I spent sleepless night learning about it, and creating things from DIY weather station, world clock, light sensor, etc. Fast forward to the current days, I almost forgot everything I learned. But we can always re-learn, or can’t we? Tonight, I found an Stm32 Nucleo F401RE micro-controller, and I want to start by updating the firmware on it (admittedly, this is the easiest thing to do). ST provides a tool called STW-LINK007, which can be freely downloaded from its website, to flash the firmware on a range of its micro-controllers. I have also written a blog post to update a similar micro-controller, STM32F4-Discovery, in the past. ...

On most my systems I created a user called devops with its home directory created at /srv/devops. And on Fedora or CentOS systems, those home directories have their SELinux context set correctly when created. Recently, I found out that on all 3 machines so far, the SELinux context has been reverted. ~# ls -lZ /srv total 0 drwx------. 5 devops devops system_u:object_r:var_t:s0 127 Oct 30 2019 devops It should have had the same context as the normal user kenno in /home directory: ...