Data leak at Sonicwall: All cloud backups of firewalls stolen
Initially, only a few percent of backup data were thought affected; now it's 100 percent. Admins must take action.

Data leak at Sonicwall: All cloud backups of firewalls stolen
Initially, only a few percent of backup data were thought affected; now it's 100 percent. Admins must take action.
@bekopharm @michaelkofler Ja. Ist mir auch gelungen.
Wollte ne externe Festplatte verschenken und Daten vorher löschen. Sicher löschen. Hab das falsche Device ausgewählt.
Zack. Boot-Device platt.
#Backup war vom Vortag. Glück gehabt.
Datenleck bei Sonicwall: Alle Cloud-Backups von Firewalls gestohlen
Hieß es zunächst, es seien nur wenige Prozent der Sicherungsdaten betroffen, wird nun klar: Es sind tatsächlich 100 Prozent - Admins sollten handeln.
And the tool I found necessitates the source instance to,be online and doesn't allow using like a #backup file...
Wednesday, October 8, 2025
Partisans derail train carrying military cargo in Russia -- Liberating our land, step by step; Ukraine reports successful counterattack in Dnipropterovsk Oblast, shows footage -- Indian national surrenders to Ukraine after fighting for Russia for 3 days -- Ukraine allocates $36 million to bolster energy grid of frontline regions amid Russian strikes ... and morehttps://activitypub.writeworks.uk/2025/10/wednesday-october-8-2025/
borgmatic 2.0.9 has been released with ZFS, Btrfs, and LVM improvements, more flexible systemd credentials, and support for Python 3.14.
#borgmatic #borgbackup #backup
Release notes: https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/2.0.9
Der Bundesrechnungshof hat übrigens dem Bund bescheinigt, dass unsere Rechenzentren ebenfalls unzureichend abgesichert sind!
#KRITIS Sektor #Staat und #Verwaltung
#Backup fehlt: Feuer zerstört ungesicherte #Cloud der koreanischen #Regierung
"750.000 Beamte haben ihre Dateien in dem zerstörten Cloud-System abgelegt. Das war aber nicht an ein Back-up angeschlossen – ein fataler Fehler."
They had a backup. In the same room. Apparently no one knew about 3-2-1 backups
https://www.chosun.com/english/national-en/2025/10/02/FPWGFSXMLNCFPIEGWKZF3BOQ3M/
Pesadelo digital na Coreia do Sul: incêndio apaga 858 TB de dados do governo por não ter backups https://tugatech.com.pt/t72389-pesadelo-digital-na-coreia-do-sul-incendio-apaga-858-tb-de-dados-do-governo-por-nao-ter-backups
Here’s another link to an explanation:
https://www.techtarget.com/searchdatabackup/definition/3-2-1-Backup-Strategy
« The G-Drive has been in use since 2018, requiring gov officials to store all work documents in the cloud instead of on personal computers. It provided around 30 Gb per person. However, […] no external #backup were maintained — meaning all data has been permanently lost » https://koreajoongangdaily.joins.com/news/2025-10-01/national/socialAffairs/NIRS-fire-destroys-governments-cloud-storage-system-no-backups-available/2412936
My prediction: a proper investigation would find several message chains each year of this thing's operation in which a sysadmin says "Why don't we have a backup for this?" and is not answered in any satisfactory manner.
My bet is that there was a budget for studying the backup methodology most consonant with the unique nature of the system and it all disappeared in a high-level exec's discretionary budget.
Kopi-Docka v2.0 - Disaster Recovery für #Docker
Server-Crash? Kein Problem: Cold Backups mit #Kopia (verschlüsselt, dedupliziert)
DR-Bundle → ./recover.sh → 15 Min. → fertig!
Multi-Cloud: S3, B2, Azure, GCS, SFTP
Von C#/VB.NET zu #Python mit KI-Support gebaut
(Perplexity + ChatGPT + Claude Code)
100% #OpenSource, MIT-Lizenz:
https://github.com/TZERO78/kopi-docka
I wished @thisdoesnotcomp made a #playlist with his #BackgroundMusic and called it something like: "#SmoothJazz to think about #ObsoleteMedia and restore #VintageComputers to" or something...
Also besides #Zip & #Jaz, #iomega also had a QIC #TapeDrive called #ditto which also had the same case design like the former, but in a bordeaux-coloured plastic case in the external, parallel port version...
I have one laying around, somewhere...
so now, let's point imessage-exporter at the archive and let it go.
and it, actually worked.
So now I have
- an improved backup of my iphone photos (found quite a few were missing) and
- an archive of my iphone; and
- a useable backup of my iMessages.
Sweet!
So this has been a useful Saturday morning.
Digikam - has a really solid set of search tools, let me quickly set up a filtered list showing my iPhone photos, which then showed me some (unexpected) gaps in my photo archive. (if you've never taken a look at the files, the images are numbered in sequence, so a missing number = a missing photo.)
Grabbed iPhone, pulled over the missing months. Done.
Also, have managed to (mostly) backup my iPhone to my Linux Mint laptop. That was a bit arduous, recipe follows.
There are 2, potentially 3, steps if you want to do this.
Archive your iphone.
This reddit thread (https://www.reddit.com/r/linuxquestions/comments/1euono4/importing_imessage_data_from_iphone_to_linux/) says that you can use libimobiledevice to make an unencrypted backup of your iPhone.
Last updated in 2020, but what's the worst that can happen, right? (Documentation suggests that it is being checked against iOS updates and continues to work so....I guess?)
The project's webpage has install instructions for both Debian and Ubuntu (https://libimobiledevice.org/#get-started), I followed the Ubuntu script and, ok so far so good, installation complete.
Connecting my iphone, telling it to trust my laptop, and then entering ideviceinfo into the terminal showed that it could see and get data from my iphone.
(This thread was helpful with syntax questions that came up during the next step (spaces are your friend) https://askubuntu.com/questions/1127798/how-to-run-a-iphone-backup-with-idevicebackup2
From there, open notepad and build out instructions to pull a full, unencrypted archive of my phone.
back into terminal, work through the mistakes, and voila, a 200GB backup sitting in my documents folder.
inhale, exhale, go for a walk
Step 2 (or 2 and 3)
imessage-exporter works on iPhone backups. And following the steps above, we now have one.
So how do we get this thing running on Linux Mint.
Fortunately, there is a binary.
https://github.com/ReagentX/imessage-exporter/blob/develop/imessage-exporter/README.md
Using something called cargo.
Hmmmm.
Anyway. (and this is the potential extra step) entering that command into Terminal told me that
1- cargo is installed
2- it's out of date
the additional step -> Great. update cargo, and what the heck is cargo anyway.
Poking around (and I did a lot of poking around this morning, I've no idea where this misplaced confidence in my computer skills came from today but whatever) I found that
Cargo is part of the Rust environment; and
Rustup (claims) that using this _completely different_ set of terminal commands will install a current version of things.
Ok. sure.
So I did that and then repeated the imessage-exporter install. Which failed, with the same error message.
I will now jump forward a lot of time, and provide the answer which is to close, and then reopen, the Terminal. It needed that to refresh the version of Cargo.
This time, entering
cargo install imessage-exporter
worked.
So, the sequence so far
install libimobiledevice
use devicebackup2 to build a full iPhone archive
install imessage-exporter
v2.0.0: Stable Release of Immich (complete with Merch and DVD)
v2.0.0: Stable Release of Immich (complete with Merch and... #immich #selfhosted #homeserve #backup #image #photography #software #technology #foss #linuxv2.0.0: Stable Release of Immich (complete with Merch and DVD)
v2.0.0: Stable Release of Immich (complete with Merch and... #immich #selfhosted #homeserver #photography #backup #foss #software #linux