You are not logged in.
I've installed Volatility3. When running, it oftentimes requires writing to /usr/lib/python3.12/site-packages/volatility3/symbols/. What's the best way to do it without sudo? Should I change the ownership? Should I give writing permission to "other"? Or maybe should I just run it with sudo every time?
Last edited by notadaughter (2024-11-30 12:16:55)
Offline
None of the above. User-run processes should never write to system directories.
How did you install this software?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
sudo pacman -S volatility3
How did you install this software?
Offline
Online
So, as far as I understand, the best way is just to install Volatility3 locally via git clone?
Offline
By altering the symbols_basepath constant you can put a user writable directory first, that would still be used by the installed system. This can also done by adding -s <path> manually to each invocation of the CLI.
Just create a folder ~/.config/volatility and setup a shell alias that adds -s ~/.config/volatility to the command used to start volatililty .
For bash read https://wiki.archlinux.org/title/Bash#Aliases .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Thanks!
Offline