Trisquel 9 doesn't have mvn-debian but has mvn instead.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

This uses spaces everywhere instead of mixing spaces and tabs.

In addition it also fix a line over 80 characters.

This should contain no functional changes.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Reviewed-by: Fil Lupin <fillupin@protonmail.com>

As we got report of data corruption in the package.xml file with
that script, it is better not to run it at each boot.

The corruption probably comes from having the device being shut
down precisely between the 5 seconds in which it modifies the
packages.xml files, which leaves a temporary file and an empty
packages.xml.

To keep the code simple, we will do two releases: one that doesn't
run this script automatically and one that does.

This way users will install the one that does the migration and once
done they will install the final image.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

These scripts enable users to cleanly shutdown and reboot the
device from the shell.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Wipe comes from wipe 2.3.1 from http://wipe.sourceforge.net/.

As there doesn't seem to be any git repository, the tarball
was imported in git the subsequent commit added support for
Android.

Wipe is strongly needed as without it it's not very convenient
to securely delete files from the internal storage.

Without wipe, one would have to port GNU/Linux to the device
if it's not already done, or reuse the Replicant 11 kernel
otherwise, and run a distribution like Parabola to securely
erase files.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

Signed-off-by: belgin <belginstirbu@hotmail.com>
Acked-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

The gen_key_migration_script script was modified to generate a
key-migration.sh script that can run multiple times.

In addition, prints were added to inform the user of the script
success of failure.

So we need to update the generated script as well for the changes
to be taken into account.

This modified version was generated with the following command in
the top directory of the replicant-6.0 source code:
    $ ./vendor/replicant-scripts/images/gen_key_migration_script/gen_key_migration_script.py \
      gen-script \
      vendor/replicant/prebuilt/common/bin/key-migration.sh \
      vendor/replicant-data/distros/releases/certificates/ \
      vendor/replicant-security/

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

The calls to otasigcheck.sh have already been removed in the build
repository with the following commit:
    57b200aeb4af062d2c7714de34fafe9b5d6e201c
    57b200aeb Recovery: Remove check for matching application signatures with their data

So it is not needed anymore. Removing otasigcheck.sh also makes sure that
it's not possible to call it anymore.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

The applications built from Replicant are signed with a key that is
generated during the build procedure The issue is that the data of an
application becomes inaccessible to it if the application signature change.
This affects all the applications built during and signed during the build
of Replicant images, which includes all system applications.

This is why, during the installation of a new Replicant version, the
otasigcheck.sh is run: it verifies if the application signatures expected
by the applications data match the signatures of the new applications
that are part of the new Replicant image being installed.

Without this check, users installing a new Replicant minor version (like
Replicant 6.0 0004) and keeping the data from the previous minor version
(like Replicant 6.0 0003) with a key that change will make at least some
system applications like the launcher crash as they will not be able to
access their data.

If the check detects an incompatibility, on a Galaxy SIII (GT-I9300), we
end up the installation aborting and the following message being displayed
on the screen:
  detected filesystem ext4 for /dev/block/mmcblk0p12
  Can't install this package on top of incompatible data. Ples
  se try another package or run a factory test
  E:Failed to install /sideload/package.zip
  E:Please take note of all the above lines for reports.

This design has several issues:
- You cannot upgrade between Replicant minor versions if the keys signing
  applications shipped in the new version changed. This is really
  problematic as to upgrade, users need to delete all their application
  data and restart creating them from scratch which is very time consuming.
  With frequent updates that would becomes too much time consuming to do.
- It is also very fragile: if the data partition is encrypted,
  otasigcheck.sh cannot do the check, and the check is skipped completely,
  with the consequences explained before (the system applications end up
  not being able to access their data).

To fix that:
- This patch adds a new script (key-migration.sh) to this repository.
  It takes care of migrating the applications data to the new keys during
  the first boot (so after the data partition will have been mounted).
- The call to otasigcheck.sh during the installation of new Replicant
  versions will be removed in the build repository.
- otasigcheck.sh will be removed in this repository in the next commit.
- A python script generating this key-migration.sh script will be added
  to the vendor_replicant-scripts repository to enable users and developers
  to generate a key-migration.sh script with the keys they want. This
  should make downgrade easier as the key-migration.sh could also be run
  manually in the recovery and make the migration to self-built images much
  easier.

Also, the otasigcheck.sh script has already been removed in LineageOS 17.1
by the following commit in vendor/lineage:
  commit 95621f3c73b94a87ca4528748535bb114ae1613f
  Author: Michael Bestas <mkbestas@lineageos.org>
  Date:   Sat Aug 4 17:46:35 2018 +0300

      Revert "ota: Validate any installed data's signature against our own"

      * otasigcheck doesn't work on encrypted devices and makes
        the zip installation fail since oreo.
      * The build part of this was never ported to oreo.

      This reverts commit aff5e54c4ef5fec7e67e830f83ee64424005d07c.

      Change-Id: I411f33c1db64844091c1692ef4706ae541925d4f

This key-migration.sh script has been generated by the following command in
the Replicant source code directory:
    $ ./vendor/replicant-scripts/images/gen_key_migration_script/gen_key_migration_script.py \
      gen-script \
      vendor/replicant/prebuilt/common/bin/key-migration.sh \
      vendor/replicant-data/distros/releases/certificates/ \
      vendor/replicant-security/

This work is based on the following commit from the android_vendor_cm
repository[1]:
    2f7c7decc Add startup script to update the package signatures
    commit 2f7c7decc4cd5b42f044a7841a74468e4cacd694 (refs/changes/27/156327/3)
    Author: Gabriele M <moto.falcon.git@gmail.com>
    Date:   Fri Jan 13 17:03:45 2017 +0100

        Add startup script to update the package signatures

        This allows to jump straight to LineageOS without wiping
        userdata first.

        Change-Id: I208bcada9380cbd69f3bec6c64e3c9e0eb1104c8

[1] https://github.com/LineageOS/android_vendor_cm.git

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>