We had some requests about possible professional collaborations with our core team and to answer you all we remember that a part of us work in the private sector, in law enforcement, as lawyer (expert in cyber security) and as freelance DFIR expert.
As you guess, earn money is not the goal of our open source project, but feel free to drop us an email if you need and we will answer to you if we are able to help you or if we can suggest to you some good friends in the field/Country of your interest.
Here below will be published any known issue on latest releases, with suggestions about possible workarounds waiting for new updates:
The last release needs more ressources (CPU,RAM,...) and if those are less than the specified hardware requirements there is the risk that the user is not able to open the session and a password (that is not present) is asked.
In case of installation instead, when the ressources are lower when the system is started in Legacy MBR mode, the installer process could crash at the end when the bootable partition is created. We are aware about this topic and we will improve fix this problem in the next release. As workaround boot the system in UEFI mode if supported.
On some VMware Hypervisors you could have some error messages during the OVA import. You can edit the OVA fixing with the right hardware information or use VirtualBOX waiting for the new release
Using Gparted tool, to manipulate devices/partitions, can produce an error because each time Gparted do a refresh, the device is automatically locked in Read-Only mode by the forensic kernel.
If you need to create a partition, for example, try instead to use "mkfs*" commands
Is not possible to mount encrypted volumes (Bitlocker, LUKS,...) in Read/Write mode because the device locker at kernel level always puts the loopback interfaces in Read Only mode
Feel free to drop us an email if you have this need