From f61fd571e03f006fee7f5e95e2cac66c99d07f6b Mon Sep 17 00:00:00 2001 From: Chris Renshaw Date: Thu, 22 Feb 2024 14:20:10 -0400 Subject: [PATCH] README: clarify caveat for format migration from cross-forks --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5159877..b18c3ca 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ You can fill out the included template [example.pif.json](https://raw.githubuser As a general rule you can't use values from recent devices due to them only being allowed with full hardware backed attestation. -Older formatted custom.pif.json files from cross-forks and previous releases will be automatically migrated to the latest format. +Older formatted custom.pif.json files from cross-forks and previous releases will be automatically migrated to the latest format. Simply ensure the filename is custom.pif.json and place it in the module directory before upgrading. A migration may also be performed manually with `sh migrate.sh` and custom.pif.json in the same directory, or from a file explorer app that supports script execution.