- wlug - list.wlug.org.nz

Does Desktop Linux Have a Firefox Problem?
by Peter Reutemann 14 Aug '23

14 Aug '23

'OS News' managing editor calls Firefox "the single most important desktop Linux application," shipping in most distros (with some users later opting for a post-installation download of Chrome). But "I'm genuinely worried about the state of browsers on Linux, and the future of Firefox on Linux in particular..." While both GNOME and KDE nominally invest in their own two browsers, GNOME Web and Falkon, their uptake is limited and releases few and far between. For instance, none of the major Linux distributions ship GNOME Web as their default browser, and it lacks many of the features users come to expect from a browser. Falkon, meanwhile, is updated only sporadically, often going years between releases. Worse yet, Falkon uses Chromium through QtWebEngine, and GNOME Web uses WebKit (which are updated separately from the browser, so browser releases are not always a solid metric!), so both are dependent on the goodwill of two of the most ruthless corporations in the world, Google and Apple respectively. Even Firefox itself, even though it's clearly the browser of choice of distributions and Linux users alike, does not consider Linux a first-tier platform. Firefox is first and foremost a Windows browser, followed by macOS second, and Linux third. The love the Linux world has for Firefox is not reciprocated by Mozilla in the same way, and this shows in various places where issues fixed and addressed on the Windows side are ignored on the Linux side for years or longer. The best and most visible example of that is hardware video acceleration. This feature has been a default part of the Windows version since forever, but it wasn't enabled by default for Linux until Firefox 115, released only in early July 2023. Even then, the feature is only enabled by default for users of Intel graphics — AMD and Nvidia users need not apply. This lack of video acceleration was — and for AMD and Nvidia users, still is — a major contributing factor to Linux battery life on laptops taking a serious hit compared to their Windows counterparts... It's not just hardware accelerated video decoding. Gesture support has taken much longer to arrive on the Linux version than it did on the Windows version — things like using swipes to go back and forward, or pinch to zoom on images... I don't see anyone talking about this problem, or planning for the eventual possible demise of Firefox, what that would mean for the Linux desktop, and how it can be avoided or mitigated. In an ideal world, the major stakeholders of the Linux desktop — KDE, GNOME, the various major distributions — would get together and seriously consider a plan of action. The best possible solution, in my view, would be to fork one of the major browser engines (or pick one and significantly invest in it), and modify this engine and tailor it specifically for the Linux desktop. Stop living off the scraps and leftovers thrown across the fence from Windows and macOS browser makers, and focus entirely on making a browser engine that is optimised fully for Linux, its graphics stack, and its desktops. Have the major stakeholders work together on a Linux-first — or even Linux-only — browser engine, leaving the graphical front-end to the various toolkits and desktop environments.... I think it's highly irresponsible of the various prominent players in the desktop Linux community, from GNOME to KDE, from Ubuntu to Fedora, to seemingly have absolutely zero contingency plans for when Firefox enshittifies or dies...' -- source: https://news.slashdot.org/story/23/08/13/226217 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

Mozilla To Bring Firefox Desktop Extension To Android Browser
by Peter Reutemann 12 Aug '23

12 Aug '23

'Scott DeVaney, writing at Mozilla blog: In the coming months Mozilla will launch support for an open ecosystem of extensions on Firefox for Android on addons.mozilla.org (AMO). We'll announce a definite launch date in early September, but it's safe to expect a roll-out before the year's end. Here's everything developers need to know to get their Firefox desktop extensions ready for Android usage and discoverability on AMO. For the past few years Firefox for Android officially supported a small subset of extensions while we focused our efforts on strengthening core Firefox for Android functionality and understanding the unique needs of mobile browser users. Today, Mozilla has built the infrastructure necessary to support an open extension ecosystem on Firefox for Android. We anticipate considerable user demand for more extensions on Firefox for Android, so why not start optimizing your desktop extension for mobile-use right away?' -- source: https://news.slashdot.org/story/23/08/11/1234201 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

'The Open Source Licensing War is Over'
by Peter Reutemann 12 Aug '23

12 Aug '23

'It's time for the open source Rambos to stop fighting and agree that developers care more about software's access and ease of use than the purity of its license, reads a piece on InfoWorld. From the report: The open source war is over, however much some want to continue soldiering on. Recently Meta (Facebook) released Llama 2, a powerful large language model (LLM) with more than 70 billion parameters. In the past, Meta had restricted use of its LLMs to research purposes, but with Llama 2, Meta opened it up; the only restriction is that it can't be used for commercial purposes. Only a handful of companies have the computational horsepower to deploy it at scale (Google, Amazon, and very, very few others). This means, of course, it's not "open source" according to the Open Source Definition (OSD), despite Meta advertising it as such. This has a few open source advocates crying, Rambo style, "They drew first blood!" and "Nothing is over! Nothing! You just don't turn it off!", insistent that Meta stop calling Llama 2 "open source." They're right, in a pedantic sort of way, but they also don't seem to realize just how irrelevant their concerns are. For years developers have been voting with their GitHub repositories to pick "open enough." It's not that open source doesn't matter, but rather it has never mattered in the way some hoped or believed. More than 10 years ago, the trend toward permissive licensing was so pronounced that RedMonk analyst James Governor declared, "Younger [developers] today are about POSS -- post open source software. [Screw] the license and governance, just commit to GitHub." In response, people in the comments fretted and scolded, saying past trends like this had resulted in "epic clusterf-s" or that "promiscuous sharing w/out a license leads to software-transmitted diseases." And yet, millions of unlicensed GitHub repositories later, we haven't entered the dark ages of software licensing. Open source, or "open enough," software now finds its way into pretty much all software, however it ends up being licensed to the end user. Ideal? Perhaps not. But a fact of life? Yep. In response, GitHub and others have devised ways to entice developers to pick open source licenses to govern their projects. As I wrote back in 2014, all these moves will likely help, but the reality is that they also won't matter. They won't matter because "open source" doesn't really matter anymore. Not as some countercultural raging against the corporate software machine, anyway. All of this led me to conclude we're in the midst of the post-open source revolution, a revolution in which software matters more than ever, but its licensing matters less and less.' -- source: https://news.slashdot.org/story/23/08/11/1221250 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

The Eternal Sunshine Of The SEO-Focused Site
by Lawrence D'Oliveiro 11 Aug '23

11 Aug '23

This report <https://arstechnica.com/information-technology/2023/08/the-internet-is-not-…> says that CNET, and possibly other large sites, are deleting online archives of decades-old articles in an effort to improve their rankings with search engines like Google. Google, on the other hand, is saying that such behaviour makes no difference to their rankings. I found the closing paragraph particularly interesting: From time immemorial, the protection of historical content has required making many copies without authorization, regardless of the cultural or business forces at play, and that has not changed with the Internet. Archivists operate in a parallel IP universe, borrowing scraps of reality and keeping them safe until shortsighted business decisions and copyright protectionism die down. Hopefully, despite the link rot, future historians can piece together an accurate history of our fragile digital era. In there is a link to this item from the same author <https://www.technologizer.com/2012/01/23/why-history-needs-software-piracy/>, from over a decade ago, on “Why History Needs Software Piracy”: When viewed in a historical context, the benefits of software piracy far outweigh its short-term costs. If you care about the history of technology, in fact, you should be thankful that people copy software without permission.

1 0

Abuses Of AI #397: Pak’N’Save’s Savey-Meal Bot Goes Off The Rails
by Lawrence D'Oliveiro 11 Aug '23

11 Aug '23

I wonder whose bright idea it was to offer an AI-powered recipe advisor that offered free-text input <https://www.theregister.com/2023/08/11/supermarket_reins_in_ai_recipebot/>. So naturally somebody tried entering such hazardous ingredients as ammonia and bleach, to see if the bot would make up a recipe from them. Which it did. Complete with glowing recommendations like “the perfect non-alcoholic beverage to quench your thirst and refresh your senses. It combines the invigorating scents of ammonia, bleach, and water for a truly unique experience!" It has since been revised to be a bit more, ah, conservative with its suggestions, and also only allow selection from a limited list of ingredients. Though a reader suggests that the list restriction is only implemented within the HTML page itself, not in the actual back end.

1 0

Intel's GPU Drivers Now Collect Telemetry, Including 'How You Use Your Computer'
by Peter Reutemann 10 Aug '23

10 Aug '23

'ExtremeTech: Intel has introduced a telemetry collection service by default in the latest beta driver for its Arc GPUs. You can opt out of it, but we all know most people just click "yes" to everything during a software installation. Intel's release notes for the drivers don't mention this change to how its drivers work, which is a curious omission. News of Intel adding telemetry collection to its drivers is a significant change to how its GPU drivers work. Intel has even given this new collation routine a cute name -- the Intel Computing Improvement Program. Gee, that sounds pretty wonderful. We want to improve our computing, so let's dive into the details briefly. According to TechPowerUp, which discovered the change, Intel has created a landing page for the program that explains what is collected and what isn't. At a high level, it states, "This program uses information about your computer's performance to make product improvements that may benefit you in the future." Though that sounds innocuous, Intel provides a long list of the types of data it collects, many unrelated to your computer's performance. Those include the types of websites you visit, which Intel says are dumped into 30 categories and logged without URLs or information that identifies you, including how long and how often you visit certain types of sites. It also collects information on "how you use your computer" but offers no details. It will also identify "Other devices in your computing environment." Numerous performance-related data points are also captured, such as your CPU model, display resolution, how much memory you have, and, oddly, your laptop's average battery life. The good news is that Intel allows you to opt out of this program, which is not the case with Nvidia. According to TechPowerUp, they don't even ask for permission! As for AMD, they not only give you a choice to opt out but they also explain what data they're collecting.' -- source: https://yro.slashdot.org/story/23/08/09/2030205 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

Microsoft Visual Studio Code flaw lets extensions steal passwords
by Peter Reutemann 10 Aug '23

10 Aug '23

'Microsoft's Visual Studio Code (VS Code) code editor and development environment contains a flaw that allows malicious extensions to retrieve authentication tokens stored in Windows, Linux, and macOS credential managers. These tokens are used for integrating with various third-party services and APIs, such as Git, GitHub, and other coding platforms, so stealing them could have significant consequences for a compromised organization's data security, potentially leading to unauthorized system access, data breaches, etc. The flaw was discovered by Cycode researchers, who reported it to Microsoft along with a working proof-of-concept (PoC) they developed. Yet, the tech giant decided against fixing the issue, as extensions are not expected to be sandboxed from the rest of the environment.' -- source: https://www.bleepingcomputer.com/news/security/microsoft-visual-studio-code… 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

Bram Moolenaar, Author of the Open Source Vim Code Editor, Has Died
by Peter Reutemann 08 Aug '23

08 Aug '23

'The creator of one of the most popular programming editors of all time, Vim, has died after a brief illness. :wq. You may not have known Bram Moolenaar’s name, but all developers know his open source programming editor, Vim. His family has reported to the Vim announcement list that Moolenaar has died. According to the note, “Bram Moolenaar passed away on 3 August 2023.” Bram suffered from a medical condition that progressed quickly over the last few weeks.” No further details are available at this time. They added Bram had “dedicated a large part of his life to VIM, and he was very proud of the VIM community that you are all part of.” This is true. Under his guidance, Vim became one of the most popular code editors in the world. Vim was based on Unix’s Vi, a screen-oriented text editor created by Bill Joy that proved to be immensely popular. Indeed, it was my first editor. Its command set, while often used in jokes, is powerful. It’s still embedded in my fingers today. I’m far from the only programmer who can say that.' -- source: https://thenewstack.io/bram-moolenaar-author-of-the-open-source-vim-code-ed… 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

Qualcomm—one of Arm’s biggest customers—starts a RISC-V joint venture
by Peter Reutemann 07 Aug '23

07 Aug '23

'Arm is facing down its biggest competition ever, with the up-and-coming RISC-V architecture threatening to unseat it as the CPU at the center of almost every portable device. Now, one of Arm's biggest customers is trying out RISC-V, as Qualcomm is getting involved in a joint venture dedicated to the architecture. The joint venture doesn't have a name yet, but Qualcomm, NXP, Nordic Semiconductor, Bosch, and memory giant Infineon are all teaming up to form a new company that Qualcomm's press release says is "aimed at advancing the adoption of RISC-V globally by enabling next-generation hardware development." At first, the group will be focused on automotive uses, with an "eventual expansion" to IoT and mobile, Qualcomm's biggest market. Arm doesn't manufacture any chips itself and instead exists as a design and licensing operation. It licenses both the Arm architecture, allowing companies to design an Arm-compatible chip themselves (this is what Apple does), and it also licenses completed CPU designs, allowing partners like Qualcomm, Samsung, and MediaTek to produce new SoCs year after year. Previously, we would have said Qualcomm's "next-generation hardware" project revolves around its acquisition of Nuvia, a chip design house that was founded by ex-SoC engineers from Apple, which currently makes the fastest mobile ARM chips available. Qualcomm's CPUs all use Arm's designs, and they are regularly a generation or two behind what Apple can do. If Nuvia lives up to its potential, Qualcomm's Arm chips would finally be competitive. The company says chips from Nuvia are expected to hit the market in 2024 for PCs, so Qualcomm will be sticking with Arm for a while longer. Qualcomm's "Snapdragon Automotive" products are usually based on 5-year-old phone designs, but it sounds like that's changing. A RISC-V transition, if one ever comes, is a few years down the line. RISC-V is threatening Arm for a few reasons. First is its open source licensing, which potentially lets companies avoid the fees Arm charges to make any chip compatible with its instruction set. Second is that RISC-V is also a way for companies to insulate themselves from Arm, which has become an increasingly unstable hardware partner. Arm is at the center of most mobile devices, but it doesn't make a ton of money off of this licensing business. ' -- source: https://arstechnica.com/gadgets/2023/08/qualcomm-one-of-arms-biggest-custom… 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

Asahi Linux’s new “flagship” distro for M-series Macs is a Fedora Remix
by Peter Reutemann 07 Aug '23

07 Aug '23

'Asahi Linux, the project aiming to bring a fully functional Linux system to Apple computers running on that company's own M-series chips, has announced that its new "flagship distro" is Fedora Asahi Remix. As announced at Fedora's Flock conference this week in Cork, Ireland, (and on Asahi Linux's blog), the Fedora Asahi Remix should be officially released by the end of August 2023. You can try it out now, but you should "expect rough spots (or even complete breakage)." The new distro will be "upstream-first," sending as many of its bespoke M-series tools back to Fedora's mainline offerings as possible. Hector Martin, writing on Asahi Linux's blog, notes that the existing project based on Arch Linux was "fully downstream." Asahi added its own package repository with scripts, forked kernel and Mesa packages, bootloader parts, and userspace support, but with "no significant involvement with upstream Arch Linux ARM or Arch Linux." Neal Gompa from Fedora reached out to talk about integrating Asahi with Fedora after the project's debut, and work began in late 2021. Now it's ready to spread a bit further. "Collaborating with distro integration experts and using distro infra(structure) like this frees us up to continue focusing on what we do best: reverse engineer hardware and develop bespoke drivers and software," Martin writes. Integration with a well-established distribution also means that bugs in desktop ARM64 Linux, "a niche platform (until now!)," Martin writes, can be addressed more quickly.' -- source: https://arstechnica.com/gadgets/2023/08/asahi-linux-will-offer-a-flagship-f… 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

The State Of ARM
by Lawrence D'Oliveiro 06 Aug '23

06 Aug '23

Everybody knows that ARM dominates the embedded market, where it ships more units per year than the entire population of the Earth. But it is making inroads in, shall we say, more “niche” markets, too, like PCs and servers. According to this <https://www.theregister.com/2023/08/02/arm_server_china/>, Canalys boss Steve Brazier says ARM already makes up 16% of the public cloud (and an even higher proportion of servers in China). But another interesting figure he mentions is “nine percent of PCs”. Now, we know that Windows-on-ARM is not that popular. Therefore, that 9% must be almost entirely running Linux-based OSes, including ChromeOS.

2 4

Linux Surpasses Mac Among Steam Gamers
by Lawrence D'Oliveiro 06 Aug '23

06 Aug '23

Windows dominates non-console gaming, of course. But according to this report <https://arstechnica.com/gadgets/2023/08/linux-surpasses-the-mac-among-steam…>, the number 2 platform (or platform family) is Linux, admittedly quite a way behind at 1.96%, ahead of the Apple Mac at 1.84%. Of the Linux share, 42% is made up of users of the Steam Deck, which is a handheld device (presumably the rest come from the various more conventional desktop distros). Microsoft has taken note of this, and is reportedly working on a “Handheld Mode” for Windows, which so far is still vapourware. Apple is also trying to do its own porting kit for Windows games to run better on Mac, analogous to WINE/Proton for Linux.

1 0

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

Firmware vulnerabilities in millions of computers could give hackers superuser status
by Peter Reutemann 21 Jul '23

21 Jul '23

'Two years ago, ransomware crooks breached hardware-maker Gigabyte and dumped more than 112 gigabytes of data that included information from some of its most important supply-chain partners, including Intel and AMD. Now researchers are warning that the leaked information revealed what could amount to critical zero-day vulnerabilities that could imperil huge swaths of the computing world. The vulnerabilities reside inside firmware that Duluth, Georgia-based AMI makes for BMCs (baseboard management controllers). These tiny computers soldered into the motherboard of servers allow cloud centers, and sometimes their customers, to streamline the remote management of vast fleets of computers. They enable administrators to remotely reinstall OSes, install and uninstall apps, and control just about every other aspect of the system—even when it's turned off. BMCs provide what’s known in the industry as “lights-out” system management. Lights-out forever Researchers from security firm Eclypsium analyzed AMI firmware leaked in the 2021 ransomware attack and identified vulnerabilities that had lurked for years. They can be exploited by any local or remote attacker with access to an industry-standard remote-management interface known as Redfish to execute malicious code that will run on every server inside a data center. Until the vulnerabilities are patched using an update AMI published on Thursday, they provide a means for malicious hackers—both financially motivated or nation-state sponsored—to gain superuser status inside some of the most sensitive cloud environments in the world. From there, the attackers could install ransomware and espionage malware that runs at some of the lowest levels inside infected machines. Successful attackers could also cause physical damage to servers or indefinite reboot loops that a victim organization can’t interrupt. Eclypsium warned such events could lead to “lights out forever” scenarios.' -- source: https://arstechnica.com/security/2023/07/millions-of-servers-inside-data-ce… 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

Kevin Mitnick, Hacker Who Once Eluded Authorities, is Dead at 59
by Peter Reutemann 21 Jul '23

21 Jul '23

'Kevin Mitnick, once the so-called "most wanted computer criminal in US history," died on Sunday. He was 59. The New York Times adds: The cause was complications from pancreatic cancer. He had been undergoing treatment at the University of Pittsburgh Medical Center following his diagnosis more than a year ago, according to the King David Memorial Chapel & Cemetery in Las Vegas. After serving prison time for breaking into and tampering with corporate computer networks, he was released in 2000 and began a new career as a security consultant, writer and public speaker. Mr. Mitnick was best known for the crime spree during the 1990s that involved the theft of thousands of data files and credit card numbers from computers across the country. He used his skills to work his way into the nation's phone and cell networks, vandalizing government, corporate and university computer systems. Investigators at the time named him the "most wanted" computer hacker in the world. In 1995, after a more than two-year-long manhunt, Mr. Mitnick was captured by the F.B.I. and charged with the illegal use of a telephone access device and computer fraud. "He allegedly had access to corporate trade secrets worth millions of dollars. He was a very big threat," Kent Walker, a former assistant U.S. attorney in San Francisco, said at the time. In 1998, while Mr. Mitnick awaited sentencing, a group of supporters commandeered The New York Times website for several hours, forcing it to shut down. The next year, Mr. Mitnick pleaded guilty to computer and wire fraud as part of an agreement with prosecutors and was sentenced to 46 months in prison. He was also prohibited from using a computer or cellphone without the permission of his probation officer for the three years following his release. >From an obituary: Kevin was an original; much of his life reads like a fiction story. The word that most of us who knew him would use -- magnificent. He grew up brilliant and restless in the San Fernando Valley in California, an only child with a penchant for mischief, a defiant attitude toward authority, and a love for magic. Kevin's intelligence and delight in holding the rapt attention of audiences revealed themselves early in his childhood and continued throughout his life. In time, he transitioned from pranks and learning magic tricks to phone phreaking, social engineering, and computer hacking. When his desire to push boundaries led him too far astray, he landed in juvenile detention and eventually served a couple of stints in prison. His time on the FBI's Most Wanted List was well documented in his New York Times bestselling book, The Ghost in the Wires: My Adventures as the World's Most Wanted Hacker, and his other titles: The Art of Deception, The Art of Intrusion, both co-authored with William Simon, and The Art of Invisibility with Robert Vamosi. Kevin emerged from his final prison term, which he deemed a 'vacation,' in January 2000. He was a changed individual, and began constructing a new career, as a White Hat hacker and security consultant. He became a highly sought-after global public speaker, a writer, and established the successful Mitnick Security Consulting. In November 2011, he became the Chief Hacking Officer and part owner of security awareness training company KnowBe4, founded by close friend and business partner Stu Sjouwerman.' -- source: https://news.slashdot.org/story/23/07/20/031216 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

Fear, loathing, and excitement as Threads adopts open standard used by Mastodon
by Peter Reutemann 20 Jul '23

20 Jul '23

'Days after Meta launched its new app, Threads, this month, a software engineer at the company named Ben Savage introduced himself to a developer group at the World Wide Web Consortium, a web standards body. The group, which maintains a protocol for connecting social networks called ActivityPub, had been preparing for this moment for months, ever since rumors first emerged that Meta planned to join the standard. Now, that moment had arrived. “I'm really interested to see how this interoperable future plays out!” he wrote. Warm replies to Savage’s email filtered in. And then came another response: “The company you work for does disgusting things among others. It harms relationships and isolates people. It builds walls and lures people into them. When that doesn't suffice, brutal peer pressure does … That said, welcome to the list, Ben.” Meta’s embrace of ActivityPub, used by apps including the Twitter-like Mastodon, was bound to be a little awkward. The constellation of small apps and personal servers that currently use the protocol, known as the Fediverse, is marked by an ethos of sharing and openness, not profit-seeking or user bases denominated in the billions. ActivityPub is designed to allow users of different apps to not only interact and view each others’ content, but also move their digital identity from one service to another. Mastodon, the largest app in the Fediverse, is open source and run by a nonprofit, and smaller Fediverse apps like PeerTube and Lemmy are often held up as a repudiation of the closed nature of services such as YouTube or Reddit. Corporations like Meta are typically held up as the enemy. No surprise that, despite appeals from ActivityPub leaders for civility when Meta arrived on the listserv, some couldn’t hold their tongue. Weeks-old Threads already dwarfs the Fediverse, which has been around for more than a decade and recently peaked at about 4 million active monthly users. Some Fediverse fans see that imbalance as a win: Suddenly, the network could become many times more relevant. Others consider that view naive and expect Meta’s size to push the small world of apps built on ActivityPub in undesirable directions. Some have circulated a pact to preemptively block content from Threads’ servers from appearing on their own.' -- source: https://arstechnica.com/tech-policy/2023/07/fear-loathing-and-excitement-as… 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