Help me!GPG private key import problem

ZH_Y · 02-28-2020, 01:02 AM

My computer system :ubuntu 16.04
My arm board system :buildroot 2019.02 +busybox
1. I generate a pair of GPG keys on my computer, export the private key and copy it to the ARM board.The prompt for importing the private key is as follows: it stops at the last line.Break with CTRL +c,discovery key already exists.

Code:

# date -s "2020-03-15"
Sun Mar 15 00:00:00 UTC 2020
# gpg --import private-key.txt
gpg: key BF22FFF087CCC6AE: public key "xyz<xyz@163.com>" imported

gpg: signal Interrupt caught ... exiting

# gpg --list-keys
//.gnupg/pubring.kbx
--------------------
pub   rsa2048 2020-02-27 [SC]
      EA8457B2DF77088146FA5B19BF22FFF087CCC6AE
uid           [ unknown] xyz<xyz@163.com>
sub   rsa2048 2020-02-27 [E]

2.My ultimate goal is to burn the file system with a private key to the ARM circuit board.This private key can be imported or ready to be imported, is there a better way to operate?

ondoho · 02-28-2020, 01:39 AM

Why are you setting a future date?

does gpg have some sort of verbose switch to give you more info?

berndbausch · 02-28-2020, 04:35 AM

Quote:

Originally Posted by ondoho

does gpg have some sort of verbose switch to give you more info?

According to the man page, it has a verbose option and even debug flags. There is also a fast-import option which leaves the building of the trust DB to a separate command.

I wonder what "importing" entails. If some cryptographic function is involved, it might take a long time on a slow CPU.

I would observe CPU usage (does Busybox include top or similar commands?). strace is probably not an option with a development board like this.

Another question: Rather than importing, what prevents you (OP) from generating the key on the board directly?

ZH_Y · 03-03-2020, 07:57 AM

Quote:

Originally Posted by ondoho

Why are you setting a future date?

does gpg have some sort of verbose switch to give you more info?

Because my initial system date was 1970, and it was earlier than I generated the key

ZH_Y · 03-03-2020, 08:00 AM

Quote:

Originally Posted by berndbausch

According to the man page, it has a verbose option and even debug flags. There is also a fast-import option which leaves the building of the trust DB to a separate command.

I wonder what "importing" entails. If some cryptographic function is involved, it might take a long time on a slow CPU.

I would observe CPU usage (does Busybox include top or similar commands?). strace is probably not an option with a development board like this.

Another question: Rather than importing, what prevents you (OP) from generating the key on the board directly?

I can only do everything through a serial port.I want to know if there is a way to import the private key directly into the file system, rather than as a private key file, and then generate the rootfs compression file and burn it to the circuit board.

berndbausch · 03-03-2020, 08:22 AM

Quote:

Originally Posted by ZH_Y

I can only do everything through a serial port.I want to know if there is a way to import the private key directly into the file system, rather than as a private key file, and then generate the rootfs compression file and burn it to the circuit board.

The verbose and debug options should work over a serial port. If your OS has screen or tmux, you can create additional shell prompts and check CPU usage while the gpg command is running.