No Image

Releasing Windows 10 Build 19043.1149 (21H1) to Release Preview Channel

2021-07-21 KENNETH 0

Releasing Windows 10 Build 19043.1149 (21H1) to Release Preview Channel Hello Windows Insiders, today we’re releasing 21H1 Build 19043.1149 (KB5004296) to the Release Preview Channel for those Insiders who are on 21H1. NOTE: Windows Insiders in the Beta Channel on 21H1 will not receive this update. We will be flighting Windows 11 Insider Preview builds to these Insiders soon! This update includes the following change in addition to all the improvements listed as part of Build 19043.1147: We added a new policy that creates generic strings and removes branding-specific terms, such as “Windows” or “PC”, for IoT Enterprise editions. For example, we changed “computer” to “device”. Instead of “Getting Windows ready,” we changed that to “Getting things ready” and so on. These generic strings are displayed on a user’s screen when an update is in progress. Thanks, The Windows Insider [ more… ]

No Image

Announcing Windows 10 Insider Preview Build 19044.1149 (21H2)

2021-07-21 KENNETH 0

Announcing Windows 10 Insider Preview Build 19044.1149 (21H2) Hello Windows Insiders, today we are releasing Windows 10, version 21H2 Build 19044.1149 (KB5004296) to the Release Preview Channel. As a reminder, this update will apply to Windows Insiders in Release Preview already on Windows 10, version 21H2 (Build 19044.1147) and Insiders who were moved from the Beta Channel to the Release Preview Channel because their PC did not meet the hardware requirements for Windows 11. For those Insiders already on Windows 10, version 21H2, this update will come through automatically via Windows Update. For Insiders not yet on 21H2, if this update is available for you, it will be offered via our “seeker” experience which means these Insiders will need to go to Settings > Update & Security > Windows Update and choose to download and install Windows 10, version 21H2. [ more… ]

No Image

USN-5019-1: NVIDIA graphics drivers vulnerabilities

2021-07-21 KENNETH 0

USN-5019-1: NVIDIA graphics drivers vulnerabilities It was discovered that an assert() could be triggered in the NVIDIA graphics drivers. A local attacker could use this to cause a denial of service. (CVE-2021-1093) It was discovered that the NVIDIA graphics drivers permitted an out-of-bounds array access. A local attacker could use this to cause a denial of service or possibly expose sensitive information. (CVE-2021-1094) It was discovered that the NVIDIA graphics drivers contained a vulnerability in the kernel mode layer where they did not properly control calls with embedded parameters in some situations. A local attacker could use this to cause a denial of service. (CVE-2021-1095) Source: USN-5019-1: NVIDIA graphics drivers vulnerabilities

[도서] 야사와 만화로 배우는 인공지능 3

2021-07-21 KENNETH 0

[도서] 야사와 만화로 배우는 인공지능 3 분야별 신상품 – 국내도서 – 컴퓨터와 인터넷 [도서]야사와 만화로 배우는 인공지능 3 권건우,허령,김가인,전준혁 저 | 루나파인북스 | 2021년 07월 판매가 14,400원 (10%할인) | YES포인트 800원(5%지급) Source: [도서] 야사와 만화로 배우는 인공지능 3

No Image

USN-5018-1: Linux kernel vulnerabilities

2021-07-21 KENNETH 0

USN-5018-1: Linux kernel vulnerabilities It was discovered that the virtual file system implementation in the Linux kernel contained an unsigned to signed integer conversion error. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-33909) Piotr Krysiuk discovered that the eBPF implementation in the Linux kernel did not properly enforce limits for pointer operations. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-33200) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation did not properly clear received fragments from memory in some situations. A physically proximate attacker could possibly use this issue to inject packets or expose sensitive information. (CVE-2020-24586) Mathy Vanhoef discovered that the Linux kernel’s WiFi implementation incorrectly handled encrypted fragments. A physically proximate attacker could possibly use [ more… ]