Mobile device forensics & digital investigation

We released version 2 of PiRogue on October 24, 2024. If you installed a PiRogue between October 24, 2024 and October 31, 2024, the package manager’s configuration might be incorrect. For affected systems, that means packages are downloaded from the development PPA instead of the production PPA.

We have deployed an updated pirogue-base package versioned 2.0.5, in both PPAs, that corrects this mistake automatically. Upgrading your system as usual should be sufficient to ensure a correct configuration:

Upgrade your PiRogue
sudo apt update
sudo apt dist-upgrade

After upgrading your system, you can compare the current configuration against the expected one.

  • On all systems expect the Pi 5, you should get the following:
pi@pirogue ➜ # Check if you are using the production PPA (all systems except Pi 5)
pi@pirogue ➜ cat /etc/apt/sources.list.d/pirogue.list
deb https://pts-project.org/debian-12/pirogue ./
deb https://pts-project.org/debian-12/pirogue-3rd-party ./
pi@pirogue ➜ |
  • On the Pi 5, you should get the following instead (note the extra, last line):
pi@pirogue ➜ # Check if you are using the production PPA (Pi 5)
pi@pirogue ➜ cat /etc/apt/sources.list.d/pirogue.list
deb https://pts-project.org/debian-12/pirogue ./
deb https://pts-project.org/debian-12/pirogue-3rd-party ./
deb https://pts-project.org/debian-12/pirogue-3rd-party-pi5 ./
pi@pirogue ➜ |

If the output is not the same as above, please contact us on Discord or by email at esther[at]defensive-lab.agency.

We sincerely apologize for the inconvenience.