> Once the simple variant works, try a more complicated one... > > Great idea. Just to see if I was being crazy, I created a new AppVM and GPG key to test with. No 'qubes-gpg-client', '--trusted-key', etc.
Like @unman had been suggested, I continued to try: gpg -r New_Key -e '/home/user/Test Encryption' -o /home/user/Final.asc I would get errors like: usage: gpg [options] --encrypt [filename] Like you suggested, I switched to something simpler I would normally use: gpg --encrypt --armor -r UserID InFile This worked perfectly, so I tried to bring this back over to the split-GPG setup. qubes-gpg-client --encrypt --armor -r C2C60E279E86F10D5697782535CE0FE6C2141823 '/home/user/Documents/Test_Encryption.txt' Unfortunately, resulted in the error discussed previously: gpg: 0xF07FADF4DCD92D53: There is no assurance this key belongs to the named user (This is my encryption subkey) gpg: cannot open '/dev/tty': No such device or address So, I tried @unman's suggestion the last time this came up: qubes-gpg-client --encrypt --armor -r robertspig...@protonmail.ch --trusted-key C2C60E279E86F10D5697782535CE0FE6C2141823 '/home/user/Documents/Test_Encryption.txt' Gives me the error: gpg: 'C2C60E279E86F10D5697782535CE0FE6C2141823' is not a valid long keyID But I know that it is correct :( -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3947582a-ad46-46dd-8600-9b5a8a2dd029o%40googlegroups.com.
