- wlug - list.wlug.org.nz

Canon Warns Printer Users To Manually Wipe Wi-Fi Settings Before Discarding
by Peter Reutemann 03 Aug '23

03 Aug '23

'Printer manufacturer Canon is warning that sensitive Wi-Fi settings don't automatically get wiped during resets, so customers should manually delete them before selling, discarding, or getting them repaired to prevent the settings from falling into the wrong hands. >From a report: "Sensitive information on the Wi-Fi connection settings stored in the memories of inkjet printers (home and office/large format) may not be deleted by the usual initialization process," company officials wrote in an advisory on Monday. They went on to say that manual wiping should occur "when your printer may be in the hand of any third party, such as when repairing, lending or disposing the printer." Like many printers these days, those from Canon connect to networks over Wi-Fi. To do this, users must provide the SSID name, the password preventing unauthorized access to the network, and in some cases, additional information such as Wi-Fi network type, the local network IP address, the MAC address, and network profile. It would be reasonable to assume that performing a simple factory reset that returns all settings to their defaults would be enough to remove these settings, but Monday's advisory indicated that isn't necessarily the case. In the event this information is exposed, malicious actors could use them to gain unauthorized access to a network hosting a Canon printer.' -- source: https://hardware.slashdot.org/story/23/08/02/116218 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

AWS To Start Charging For Public IPv4 Addresses
by Peter Reutemann 01 Aug '23

01 Aug '23

'The Register: Cloud giant AWS will start charging customers for public IPv4 addresses from next year, claiming it is forced to do this because of the increasing scarcity of these and to encourage the use of IPv6 instead. It is now four years since we officially ran out of IPv4 ranges to allocate, and since then, those wanting a new public IPv4 address have had to rely on address ranges being recovered, either from from organizations that close down or those that return addresses they no longer require as they migrate to IPv6. If Amazon's cloud division is to be believed, the difficulty in obtaining public IPv4 addresses has seen the cost of acquiring a single address rise by more than 300 percent over the past five years, and as we all know, the business is a little short of cash at the moment, so is having to pass these costs on to users. "This change reflects our own costs and is also intended to encourage you to be a bit more frugal with your use of public IPv4 addresses and to think about accelerating your adoption of IPv6 as a modernization and conservation measure,' writes AWS Chief Evangelist Jeff Barr, on the company news blog. The update will come into effect on February 1, 2024, when AWS customers will see a charge of $0.005 (half a cent) per IP address per hour for all public IPv4 addresses. These charges will apparently apply whether the address is attached to a service or not, and like many AWS charges, appear inconsequential at first glance but can mount up over time if a customer is using many of them. These charges will apply to all AWS services including EC2, Relational Database Service (RDS) database instances, Elastic Kubernetes Service (EKS) nodes, and will apply across all AWS regions, the company said. However, customers will not be charged for IP addresses that they own and bring to AWS using Amazon's BYOIP feature. AWS offers a free tier for EC2, and this will include 750 hours of public IPv4 address usage per month for the first 12 months, starting from the same date the charges do.' -- source: https://tech.slashdot.org/story/23/08/01/0013249 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

2 1

Python’s GIL, a “major obstacle to concurrency”, will likely be removed – but slowly
by Lawrence D'Oliveiro 01 Aug '23

01 Aug '23

The Python Steering Council has officially decided on a roadmap for removing a major bottleneck to multithreading performance in Python <https://devclass.com/2023/07/31/pythons-gil-a-major-obstacle-to-concurrency…>. Currently Python uses a combination of reference-counting and garbage collection in order to avoid the need for programmers to have to keep track of allocated objects and remembering when to dispose of them. A pure garbage collection scheme, like in Java or LISP, makes it easier to support multithreading, but at the cost of memory usage that can easily get out of hand. Reference counting helps to ensure that objects disappear as soon as the program forgets its last reference to them, and this works well for most objects in a typical program, with garbage collection as a fallback for cleaning up the rest. But Python’s present scheme for maintaining reference counts (the “Global Interpeter Lock” or “GIL”) prevents Python code for taking full advantage of multiple threads. Some are advocating switching to the pure garbage-collection approach, but fortunately (I think) this is not the plan that has been adopted by the Council. Instead, they are going to use a technique known as “Biased Reference Counting”. This splits the reference count into two components, one managed by a thread which is considered to “own” the object (and is presumably responsible for most accesses to the object), while the other is managed on a shared basis by other threads accessing the object (and making fewer accesses to it). This seems to offer the best performance in tests so far. The switchover is a complicated procedure, which is certain to have implications for some existing Python code that never had to worry about thread safety before, as well as far-reaching implications for the design of the CPython implementation itself. So it will take place in multiple stages over some years, and if worst comes to worst, the changes can always be rolled back. (Or a different strategy chosen.) Seems some people are still smarting over the flak they got from the Python 2 → 3 transition. “This is not Python 4,” they are saying. But why not call it “Python 4”, as a warning over the likely compatibility issues? Even if it probably won’t be quite as painful ...

1 0

Android malware steals user credentials using optical character recognition
by Peter Reutemann 31 Jul '23

31 Jul '23

'Security researchers have unearthed a rare malware find: malicious Android apps that use optical character recognition to steal credentials displayed on phone screens. The malware, dubbed CherryBlos by researchers from security firm Trend Micro, has been embedded into at least four Android apps available outside of Google Play, specifically on sites promoting money-making scams. One of the apps was available for close to a month on Google Play but didn’t contain the malicious CherryBlos payload. The researchers also discovered suspicious apps on Google Play that were created by the same developers, but they also didn’t contain the payload. The apps took great care to conceal their malicious functionality. They used a paid version of commercial software known as Jiagubao to encrypt code and code strings to prevent analysis that can detect such functionality. They also featured techniques to ensure the app remained active on phones that had installed it. When users opened legitimate apps for Binance and other cryptocurrency services, CherryBlos overlaid windows that mimicked those of the legitimate apps. During withdrawals, CherryBlos replaced the wallet address the victim selected to receive the funds with an address controlled by the attacker. The most interesting aspect of the malware is its rare, if not novel, feature that allows it to capture mnemonic passphrases used to gain access to an account. When the legitimate apps display passphrases on phone screens, the malware first takes an image of the screen and then uses OCR to translate the image into a text format that can be used to raid the account. “Once granted, CherryBlos will perform the following two tasks: 1. Read pictures from the external storage and use OCR to extract text from these pictures [and] 2. Upload the OCR results to the C&C server at regular intervals,” the researchers wrote. Most apps related to banking and finance use a setting that prevents the taking of screenshots during sensitive transactions. CherryBlos appears to bypass such restrictions by obtaining accessibility permissions used by people with vision impairments or other types of disabilities.' -- source: https://arstechnica.com/security/2023/07/android-malware-uses-ocr-to-captur… Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

GNOME Devs Are Working on a New Window Management System
by Peter Reutemann 31 Jul '23

31 Jul '23

'Managing windows — "even after 50 years, nobody's fully cracked it yet," writes GNOME developer Tobias Bernard: Most of the time you don't care about exact window sizes and positions and just want to see the windows that you need for your current task. Often that's just a single, maximized window. Sometimes it's two or three windows next to each other. It's incredibly rare that you need a dozen different overlapping windows. Yet this is what you end up with by default today, when you simply use the computer, opening apps as you need them. Messy is the default, and it's up to you to clean it up... We've wanted more powerful tiling for years, but there has not been much progress due to the huge amount of work involved on the technical side and the lack of a clear design direction we were happy with. We now finally feel like the design is at a stage where we can take concrete next steps towards making it happen, which is very exciting! The key point we keep coming back to with this work is that, if we do add a new kind of window management to GNOME, it needs to be good enough to be the default. We don't want to add yet another manual opt-in tool that doesn't solve the problems the majority of people face. The current concept imagines three possible layout states for windows: - Floating, the classic stacked windows model - Edge Tiling, i.e. windows splitting the screen edge-to-edge - Mosaic, a new window management mode which combines the best parts of tiling and floating Mosaic is the default — where "you open a window, it opens centered on the screen at a size that makes the most sense for the app." (Videos in the blog post show how this works.) "As you open more windows, the existing windows move aside to make room for the new ones. If a new window doesn't fit (e.g. because it wants to be maximized) it moves to its own workspace. If the window layout comes close to filling the screen, the windows are automatically tiled." You can also manually tile windows. If there's enough space, other windows are left in a mosaic layout. However, if there's not enough space for this mosaic layout, you're prompted to pick another window to tile alongside. You're not limited to tiling just two windows side by side. Any tile (or the remaining space) can be split by dragging another window over it, and freely resized as the window minimum sizes allow. So what's next? Windows can already set a fixed size and they have an implicit minimum size, but to build a great tiling experience we need more... At the Brno hackfest in April we had an initial discussion with GNOME Shell developers about many of the technical details. There is tentative agreement that we want to move in the direction outlined in this post, but there's still a lot of work ahead... We'd like to do user research to validate some of our assumptions on different aspects of this, but it's the kind of project that's very difficult to test outside of an actual prototype that's usable day to day. "There's another issue with GNOME's current windowing system," notes 9to5Linux. "If the stacking is interrupted, newly opened windows will be opened from the top, covering the first opened window." For this new windowing system to become a reality, the GNOME devs would have to do a lot of user research and test numerous scenarios so that everyone can be happy. As you can imagine, this could take months or even years, so if you want to get involved and help them do it faster, please reach out to the GNOME team here.' -- source: https://tech.slashdot.org/story/23/07/30/2357246 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Libreboot Creator Says After Coding a Fork for 'GNU Boot Project', FSF Sent a Cease-and-Desist Letter Over Its Name
by Peter Reutemann 31 Jul '23

31 Jul '23

'Libreboot is a distribution of coreboot "aimed at replacing the proprietary BIOS firmware contained by most computers," according to Wikipedia. It was briefly part of the GNU project, until maintainer Leah Rowe and the GNU project agreed to part ways in 2017. But here in 2023, the GNU project has created a fork of Libreboot named GNU Boot... The GNU Boot fork "currently does not have a website and does not have any releases of its own," points out Libreboot's Leah Rowe, adding "My intent is to help them, and they are free — encouraged — to re-use my work... " But things have gotten messy, writes Rowe: They forked Libreboot, due to disagreement with Libreboot's Binary Blob Reduction Policy. This is a pragmatic policy, enacted in November 2022, to increase the number of coreboot users by increasing the amount of hardware supported in Libreboot... I wish GNU Boot all the best success. Truly. Although I think their project is entirely misguided (for reasons explained by modern Libreboot policy), I do think there is value in it. It provides continuity for those who wish to use something resembling the old Libreboot project... When GNU Boot first launched, as a failed hostile fork of Libreboot under the same name, I observed: their code repository was based on Libreboot from late 2022, and their website based on Libreboot in late 2021. Their same-named Libreboot site was announced during LibrePlanet 2023... [N]ow they are calling themselves GNU Boot, and it is indeed GNU, but it still has the same problem as of today: still based on very old Libreboot, and they don't even have a website. According to [the FSF's Savannah software repository], GNU Boot was created on 11 June 2023. Yet no real development, in over a month since then... I've decided that I want to help them... I decided recently that I'd simply make a release for them, exactly to their specifications (GNU Free System Distribution Guidelines), talking favourably about FSF/GNU, and so on. I'm in a position to do it (thus scratching the itch), so why not? I did this release for them — it's designated non-GeNUine Boot 20230717, and I encourage them to re-use this in their project, to get off the ground. This completely leapfrogs their current development; it's months ahead. Months. It's 8 months ahead, since their current revision is based upon Libreboot from around ~October 2022... The GNU Boot people actually sent me a cease and desist email, citing trademark infringement. Amazing... I complied with their polite request and have renamed the project to non-GeNUine Boot. The release archive was re-compiled, under this new brand name and the website was re-written accordingly. Personally, I like the new name better.' -- source: https://news.slashdot.org/story/23/07/30/0312206 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Building a Better Server? Oxide Computer Ships Its First Rack
by Peter Reutemann 30 Jul '23

30 Jul '23

'Oxide Computer Company spent four years working toward "The power of the cloud in your data center... bringing hyperscaler agility to the mainstream enterprise." And on June 30, Oxide finally shipped its very first server rack. Long-time Slashdot reader destinyland shares this report: It's the culmination of years of work — to fulfill a long-standing dream. In December of 2019, Oxide co-founder Jess Frazelle had written a blog post remembering conversations over the year with people who'd been running their own workloads on-premises... "Hyperscalers like Facebook, Google, and Microsoft have what I like to call 'infrastructure privilege' since they long ago decided they could build their own hardware and software to fulfill their needs better than commodity vendors. We are working to bring that same infrastructure privilege to everyone else!" Frazelle had seen a chance to make an impact with "better integration between the hardware and software stacks, better power distribution, and better density. It's even better for the environment due to the energy consumption wins." Oxide CTO Bryan Cantrill sees real problems in the proprietary firmware that sits between hardware and system software — so Oxide's server eliminates the BIOS and UEFI altogether, and replaces the hardware-managing baseboard management controller (or BMC) with "a proper service processor." They even wrote their own custom, all-Rust operating system (named Hubris). On the Software Engineering Daily podcast, Cantrill says "These things boot like a rocket." And it's all open source. "Everything we do is out there for people to see and understand..." Cantrill added. On the Changelog podcast Cantrill assessed its significance. "I don't necessarily view it as a revolution in its own right, so much as it is bringing the open source revolution to firmware." Oxide's early funders include 92-year-old Pierre Lamond (who hired Andy Grove at Fairchild Semiconductor) — and customers who supported their vision. On Software Engineering Daily's podcast Cantrill points out that "If you're going to use a lot of compute, you actually don't want to rent it — you want to own it."' -- source: https://news.slashdot.org/story/23/07/29/192248 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Encryption-breaking, password-leaking bug in many AMD CPUs could take months to fix
by Peter Reutemann 26 Jul '23

26 Jul '23

'A recently disclosed bug in many of AMD's newer consumer, workstation, and server processors can cause the chips to leak data at a rate of up to 30 kilobytes per core per second, writes Tavis Ormandy, a member of Google's Project Zero security team. Executed properly, the so-called "Zenbleed" vulnerability (CVE-2023-20593) could give attackers access to encryption keys and root and user passwords, along with other sensitive data from any system using a CPU based on AMD's Zen 2 architecture. The bug allows attackers to swipe data from a CPU's registers. Modern processors attempt to speed up operations by guessing what they'll be asked to do next, called "speculative execution." But sometimes the CPU guesses wrong; Zen 2 processors don't properly recover from certain kinds of mispredictions, which is the bug that Zenbleed exploits to do its thing. The bad news is that the exploit doesn't require physical hardware access and can be triggered by loading JavaScript on a malicious website. The good news is that, at least for now, there don't seem to be any cases of this bug being exploited in the wild yet, though this could change quickly now that the vulnerability has been disclosed, and the bug requires precise timing to exploit. "AMD is not aware of any known exploit of the described vulnerability outside the research environment," the company told Tom's Hardware. Networking company Cloudflare also says there is "no evidence of the bug being exploited" on its servers. Since the vulnerability is in the hardware, a firmware update from AMD is the best way to fully fix it; Ormandy says it is also fixable via a software update, but it "may have some performance cost." The bug affects all processors based on AMD's Zen 2 architecture, including several Ryzen desktop and laptop processors, EPYC 7002-series chips for servers, and Threadripper 3000- and 3000 Pro WX-series CPUs for workstations.' -- source: https://arstechnica.com/information-technology/2023/07/encryption-breaking-… Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Android 4.4 KitKat is truly dead, loses Play Services support
by Peter Reutemann 26 Jul '23

26 Jul '23

'The Android ecosystem rightfully gets a lot of slack for being unable to deliver operating system updates to everyone in a timely manner, but there's more to Android updates than just OS support. App updates can keep a phone chugging along even after the updates have stopped, and Google's do-it-all super app, Google Play Services, contains a ton of app APIs and features and enables the really important stuff like Play Store transactions and advertisements. Google just announced Play Services is dropping support for an old version of Android, and while OS development might stop at just three or four years, Play Services goes back way longer than that. Google announced Play Services is dropping support for Android 4.4 KitKat, which is now 10 years old. Support isn't really being artificially cut off, either. Google says KitKat's active device count is "below 1 percent," so there's not much reason to support it anymore.' -- source: https://arstechnica.com/gadgets/2023/07/google-drops-play-services-support-… Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Slackware Linux Distribution Turns 30 Years Old
by Peter Reutemann 24 Jul '23

24 Jul '23

'This week the Slackware Linux project is celebrating its 30th anniversary. It is the oldest Linux distribution that is still in active maintenance and development. The Register reports: Version 1.0 of Slackware was announced on the July 16, 1993, and project lead Patrick Volkerding, who still maintains the distribution today, celebrated with a modest announcement: "Hey folks! It's time to acknowledge another one of those milestones... 30 (!) years since I made the post linked below announcing Slackware's first stable release after months of beta testing. Thanks to all of our dedicated contributors, loyal users, and those who have helped us to keep the lights on here. It's really been a remarkable journey that I couldn't have anticipated starting out back in 1993. Cheers! :-)"' -- source: https://linux.slashdot.org/story/23/07/21/2138223 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

2 1