No, it’s not resolved. I can create my own GPG key locally on the NVIDIA Jetson Nano B01 and sign with it but I need sudo. However, I can’t sign it with the GPG key from my computer. I have imported the public key to the NVIDIA Jetson Nano B01, and can see the key using $ gpg --list-key and $ gpg --list-secret-keys. However, the trust level is unknown, unlike the gpg key that I create locally, the trust level is ultimate. So I am not sure what’s wrong.
Yes. I created the GPG key on the host PC and then copied to the Jetson. It’s the public key. I did gpg --export <your-key> > ~/.gnupg/publickey. Then, send it to the Jetson device and do gpg --import ~/.gnupg/publickey
If I use RemoteForward on ~/.ssh/config, when I do gpg --list-secret-keys I can see my secret key, but I can’t sign with it.
Let me start by asking what the “01” is in the above? Normally this is “<user>:<group>”, which in turn is either the name of the user/group, or the numeric ID. “01” does not correspond to anything I know of. If your user name is “ubuntu”, and the group is “ubuntu”, and if the UID and GID are both 1000 (this is the default first admin user), then things would be set something like this (and I’m using a “.” instead of “:” since that is what I’m used to): sudo chown -R ubuntu.ubuntu ~ubuntu/.gnupg/
If you are actually logged in as user “ubuntu”, then this is equivalent:
sudo chown -R ubuntu.ubuntu *
(note that user root has his own directory, but using sudo in the above manner is correct in that context)
On your host PC, what is the result of “id”? On the Jetson, what is the result of “id”? Note that it is ok if you want to substitute a dummy name like “ubuntu” in place of your actual login name. The point is to compare numeric IDs.
Then, what was your exact method of copying the keys and putting them on the Jetson?