fresh install of Garuda, all updates performed
AUR for blackarch added
when trying to install (“pacman -S blackarch-forensic”), packages are downloaded, file-integrity-checks are performed but always ends with error messages like
“Datei /var/cache/pacman/pkg/testdisk-7.2-2-x86_64.pkg.tar.zst ist beschädigt (Ungültiges oder beschädigtes Paket).”
IDK, but
testdisk
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …
Paket (1) Neue Version Netto-Veränderung Größe des Downloads
extra/testdisk 7.2-2 1,68 MiB 0,44 MiB
Gesamtgröße des Downloads: 0,44 MiB
Gesamtgröße der installierten Pakete: 1,68 MiB
:: Installation fortsetzen? [J/n]
:: Pakete werden empfangen …
testdisk-7.2-2-x86_64 454,4 KiB 916 KiB/s 00:00 [--------------------------------------------------------] 100%
(1/1) Schlüssel im Schlüsselbund werden geprüft [--------------------------------------------------------] 100%
(1/1) Paket-Integrität wird überprüft [--------------------------------------------------------] 100%
(1/1) Paket-Dateien werden geladen [--------------------------------------------------------] 100%
(1/1) Auf Dateikonflikte wird geprüft [--------------------------------------------------------] 100%
(1/1) Verfügbarer Festplattenspeicher wird ermittelt [--------------------------------------------------------] 100%
:: Pre-transaction-Hooks werden gestartet …
(1/2) Rejecting pacman transaction if running in snapshot...
(2/2) Performing snapper pre snapshots for the following configurations...
==> root: 687
:: Paketänderungen werden verarbeitet …
(1/1) Installiert wird testdisk [--------------------------------------------------------] 100%
:: Post-transaction-Hooks werden gestartet …
(1/7) Arming ConditionNeedsUpdate...
is fiine here.
Have you tried to install using blackman?
pacman -S blackman
sudo blackman -g forensic
crazy thing …
As it is just a fresh install I will do it all again from scratch and test
1 Like
thanks for the hint - but yes, tried with blackman and this works (however it seems to be veeery time consuming to compile all the software one by one)
Or did I miss a point here ?
I would not recommend that.
While blackarch does provide a lot of repositories. You might find that some of them have reached an end of life or are no longer being developed.
It is better to know what you specifically want rather than install all the junk that comes with blackarch.
In short figure out the particular forensic tool you wanna try, see whether its actively developed then install it. Better than having a lot of python2 packages that are no longer being maintained .
3 Likes
thanks for pinting that out.
Honestly I did not really research the status of all the software in the blackarch-repo. Looked quite convenient and thus my idea to install it that way.
Anyway - I tried e.g. testdisk as shown by SGS and it worked…
I will go on as suggested and select exactly the tools I need!
Thanks to all who replied!
Just throwing in an idea: docker containers are a thing, and e.g. distrobox is very well integrated with the OS. Might be an alternative to get the tools without cluttering the OS.
3 Likes
Maybe you could try deleting you pacman cache
sudo pacman -Scc
and retry
1 Like
i probably should have noted that it works, but is particularly buggy. I new to black-arch but I like it a lot. tried installing defensive tools with black-man and it turns out that it’s very new in production. so it will take a long time to install everything with black-man unless you are set up properly for it. I think I would also second what others have said and either 1. install only what you need or 2. Use a container (Distro box is a form of containers that will work perfect with black-arch.) or a separate machine and install with an ISO.
No it’s not a point really to missed. You are understanding the fact is that it’s needed to be rewritten atm and it is to be used at your own risk. As with many of the tools that will exist within blackarch, I am sure you are aware of this already. So, just use blackman for what you need to use. Also if you ran into a conflict with jre-openjdk I recommend you read this Arch Linux news article. incoming changes in jdk-jre-21 packages may require manual intervention I am still trying to fix that one myself.