Word 97's ghost in the machine: The crash that vanished the moment anyone looked at it

This week MacSparky is sponsored by Daylite.
For years I ran a law practice, and the hardest part of client work was never the work. It was keeping track of it. Where that email went, what we agreed to on a phone call, which version of the document was current, who I owed a call back. Some of it lived in Mail, some in a folder somewhere, and too much of it lived only in my head.
That’s the problem Daylite has been chipping away at for more than twenty years. It pulls your clients, projects, tasks, calendars, and communications into one place, so every email, meeting, note, and follow-up becomes part of an ongoing history of that relationship. Open up a client, and you can see what happened, what’s next, and who is waiting on you.
The newest piece of that is Mail in Daylite, which brings your email inside the app alongside everything else. A message stops being one more thing you have to file. It attaches itself to the person, the deal, and the project it belongs to.
I also like that Daylite is built only for Mac, iPhone, and iPad. It isn’t a web app wearing a Mac costume, and you can feel the difference in how it behaves.
If you run a service business and you’re tired of carrying the whole client history around in your head, take a look at Daylite. There’s a free trial.
The post Daylite Puts the Whole Client Relationship in One Place appeared first on MacSparky.
Many of the recent supply-chain attacks could have been caught earlier if defenders looked closely at the telemetry GitHub already provides, researchers said.
At their Black Hat USA 2026 presentation, researchers Yossi Weizman of Microsoft and Mor Weinberger of Echo argued the case, saying, “GitHub can tell you’re being hacked. You’re just not listening.”
The duo described an EDR-style detection approach built from GitHub’s own event stream rather than relying solely on conventional endpoint or network telemetry.
After studying recent supply-chain attacks, including Shai-Hulud, Trivy, and Megalodon, the researchers found that seemingly different incidents repeatedly used the same techniques, from forged commit identities and poisoned tags to workflow abuse, OpenID Connect (OIDC) theft, and attempts to erase evidence.
They said they turned those recurring techniques into behavioral detections, combining GitHub webhooks, API data, and Git repository inspection to build a historical view of activity.
Their new open-source tool, dubbed “GitHub Threat Detector,” reportedly includes 22 production detection rules and 12 beta rules, with compound detections designed to correlate individually weaker signals into high-confidence alerts.
The central observation in Weizman and Weinberger’s research is that supply-chain attacks often repeat the same patterns even when the targeted projects are unrelated.
A compromised identity, for example, may not be obvious from the commit itself because Git metadata can be forged. An attacker can set the author name, email, timestamp, parent, and other metadata to make a malicious commit appear legitimate.
But GitHub separately records the authenticated user who pushed the commit.
When the commit author does not match the authenticated pusher, defenders have something worth investigating, they explained. Added to this, their analysis revealed that attackers sometimes reuse the same forged identities across multiple victims. Searching GitHub for the same author’s email can therefore help connect seemingly unrelated incidents into a broader campaign.
“Forged identities in the repo which appear in other repos as well-is a strong indication of compromise,” they said.
The research found “forged maintainer’s identity” used across many attacks, including Trivy, tj-actions, Megalodon, TanStack, and Red Hat.
Another detection pitched on the same principle included tracking “Mass tag poisoning.” Mass tag poisoning involves force-moving numerous release tags onto a malicious commit so that workflows using a version such as @v1 execute attacker-controlled code. Researchers recommended adding tracking GitHub tag history through the GitHub API and comparing old and new commit references to catch this out.
OIDC offers another signal. Attackers can modify workflows to generate short-lived identities for cloud or package registries instead of stealing long-lived credentials. Watching for new or modified workflows that enable OIDC token issuance can help, the researchers said.
GitHub Threat Detector follows an EDR-like pipeline: collect activity, enrich it with context, detect suspicious behavior, and then investigate or respond. The signals it ingests include live GitHub webhooks, API events, commits, tags, and Actions activity, while Git inspection provides additional context such as tag provenance.
Additionally, a PostgreSQL-backed activity store keeps the history needed to correlate events over time.
The tool took over 30 detection rules and tested them against 52 attack simulations, including reproduction of Trivy, TanStack, Megalodon, and Bitwarden CLI incidents. A separate “noise lab” helped researchers measure detection prevalence and recall, while tuning rules through allowlisting and severity adjustments.
The system, however, is not without drawbacks. Some of the trade-offs it carries include possibly disabled webhooks, rate-limited APIs, and Git inspection not being real-time.
The article originally appeared on CSO.

If your iPhone or iPad is misbehaving and initial solutions are not working, a full reset may be necessary. Taking your device back to how it was out of the box can often help resolve issues like constant crashing, freezing or other serious problems.
It’s something of a nuclear option, though, so before you take this route we’d recommend restarting or force-restarting your iPhone or iPad, as that will leave your data and settings intact. Another option is to ensure that the version of iOS or iPadOS on your device is up to date, as the problem might be caused by an issue that has since been patched by Apple. We explain how to do this in our how to update iOS guide.
Of course, if you’re selling your iPhone (or passing it down to a family member or friend) it’s absolutely vital that you delete all the sensitive data stored on it. If not, an unscrupulous buyer could gain access to your social media profiles, financial information and even your personal photos and videos.
As with any activity that deletes data, we’d recommend that you back up your iPhone or iPad before you attempt resetting the device. After your device has been wiped you will be able to download your data from your backup.
We’ll concentrate on iPhone for this tutorial, but the steps will be more or less the same for iPad. There are two ways to erase your iPhone or iPad, one is useful if you just want to erase everything and then recover the data from a backup, the other is useful if you are moving to a new device and selling or passing on the one you are erasing. There’s also a basic Reset option that might be all you need to do in order to fix a troublesome issue.

Foundry
To factory-reset an iPhone follow these steps (after backing up your device).
You may need to remove your device from Find My before you begin. You will also need to be connected to Wi-Fi or cellular for this process to work.
If you want help backing your data up to iCloud and want to make sure you cover all the important steps that you should make when selling your old device, you can make use of the Prepare for New iPhone instructions, which will walk you through the process.

During the process for resetting you iPhone your passcode will be requested, you may also need to use the password associated with your Apple ID. This is a problem if you have forgotten it.
There is a workaround if you have forgotten your passcode but remember your Apple ID password:
After a few minutes, your iPhone or iPad will restart and you’ll be at the setup screen, as if it was a new device you just took out of the box. For obvious security reasons, there’s no way to reset your iPhone after a lost passcode without erasing all your apps and data. It would provide an exploitable loop for bad actors to get around the passcode timeouts and such. But as long as you back up your iPhone regularly (either via iCloud or with a connection to your computer) it shouldn’t be too onerous to start over.
Resetting without a password used to require plugging into a computer via USB, entering iPhone recovery mode…it was a whole process. The good news is, Apple made this a lot easier as of iOS 15.2 (and iPadOS 15.2). So, if your device is running that version or later you can follow the steps below (otherwise click on the link above to reset via a computer). If you have forgotten your Apple ID password read this for help: How to reset Apple ID if you forgot the password.
If, having erased the content of the phone, you intend to keep using it, you can restore the content to your phone from your backup – assuming you have one, if not check out the section below. Here’s to recover your iPhone or iPad data:
With the factory reset completed you’ll need to go through the setup of your iPhone again from the beginning:

Depending on the version of macOS you’re running, you’ll either be able to use Finder (macOS Mojave and later) or iTunes (macOS Catalina or earlier) to restore a backup.

If you didn’t backup your iPhone or iPad first, it’s likely that you won’t be able to retrieve data once you have deleted it.
The data on an iOS device is automatically encrypted, and wiping the device destroys the encryption key, making it more or less impossible to get anything back when it’s been fully erased and reset without access to a backup.
In an emergency you could try speaking to someone at an Apple Genius Bar, but it’s a long shot to say the least. (This applies to a full erase/reset, mind you – in other circumstances, such as data corruption, a malfunctioning device and so on, the experts may be able to help.) This also reinforces our frequent advice to back up regularly.
If you’re worried that your iPhone or iPad wasn’t backed up, don’t give up hope: there’s a chance there may be a backup of which you’re unaware.
To find out if you’re backing up to iCloud follow these steps:
One of the backups should say that it is This iPhone or This iPad. Tap on that and you can see what is, and isn’t being backed up. You can basically turn things on and off so that they don’t take up your full free 5GB iCloud allocation, or you can pay a few dollars/pounds a month for more storage.

If you don’t see a backup from the device you were hoping to recover, but you do have backups of other devices (perhaps you have an iPad backup, but not an iPhone backup) you should be able to recover some of your data simply because once you link your iPhone to your iCloud account the shared data should be available on your iPhone.
If you weren’t backing you iPhone up to iCloud we suggest you do! Read How to back up an iPhone or iPad or follow the steps below.
If the backup is going to take ages you can reduce the amount of data being backed up. For example, you may think that some of the apps don’t need to be backed up; after all, you will be able to download them again from the App Store as you already own them. But note that the data may include saved data for games, and other settings and preferences you would prefer not to lose.

There you have it. A quick guide on resetting your iPhone and then restoring it once more. Of course, if you’re moving on from that older device and fancy something newer, be sure to read our best iPhone deals roundup to see if you can save some money in the process.

xfwl4, compositor Wayland do Xfce, ganha recursos de gestão de janelas e aprimora a interação com dispositivos de entrada.
O post xfwl4 4.21.1: Xfce lança segunda prévia do compositor Wayland com melhorias em janelas e entrada apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.
Wear OS ganha atualização do Google Play Services para rotas de treino mais precisas e melhorias para apps e tablets Android.
O post Atualização do Google Play Services aprimora rotas de treino no Wear OS apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.
Conheça o SparkyLinux 8.4, que retorna com suporte 32-bit para PCs antigos e traz atualizações baseadas no Debian 13.
O post SparkyLinux 8.4: volta do suporte 32-bit para PCs antigos com Debian 13 apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.
CompartilharO GNOME Disks está sendo atualizado para GTK4 e libadwaita e o GNOME Disks com GTK4 e libadwaita muda completamente de visual. Veja as principais …
O post GNOME Disks com GTK4 e libadwaita muda completamente de visual; veja como ficou apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.