Confusion about identity_file

[AG7GN]

The documentation for identity_file states:

Description: Path to a file containing the private key (64 hex characters). If null, a new identity is generated on first run.

When I create a new node key with my desired prefix, the result is a private key of 128 hex characters, not 64. The public key is 64 hex characters. Pasting that 128 character private key into a text file and setting identity_file to that file location results in the program auto-generating a key in /var/lib/pymc-repeater/.config/pymc-repeater/identity.key. That auto-generated file looks like a base 64 version of a key and not the key itself. How to I get the program to recognize the key I created?

[rightup]

I have created a tool you can use

https://github.com/rightup/pyMC_Repeater/blob/dev/convert_firmware_key.sh

[AG7GN]

Thank you! Your tool worked as expected.

[mkwillis]

What am I doing wrong with this tool?

I enter sudo python3 convert_firmware_key.sh <followed by 128 char prv key>

and I get:

File "/home/gymreps/pyMC_Repeater/convert_firmware_key.sh", line 40
if ! [[ "$FULL_KEY" =~ ^[0-9a-fA-F]+$ ]]; then
^
SyntaxError: invalid decimal literal

[mkwillis]

Disregard... I realised I am running a forked Dev branch and the tool works fine when running main branch