Why the software is crap

[david at gbenet.com]

On 14/11/14 13:11, NdK wrote:
> Il 14/11/2014 13:24, david at gbenet.com ha scritto:
> 
>> I have cooled. You can export your private key - you can export your public key. You can
>> import your private key you can import your public key. In 20 years I have always had the
>> same problem - the same error message and have each time created a new set of keys. I have
>> done this 4 times.
> If all four times you did the same wrong thing, then it's obvious that you got the same
> wrong result.
> 
> Just to prove it's your error, I copied my .gnupg from one system (str957-142) to another
> (str957-004), with the most basic method I ould think of. I'm not an expert (probably I
> transferred more than what was needed!), but as you can see I succeeded at the first try!
> 
> diego at str957-142:~$ gpg --list-secret-keys
> /home/diego/.gnupg/secring.gpg
> ------------------------------------------------
> sec   2048R/F9B9D307 2014-11-14
> uid                  Diego <test at example.com>
> ssb   2048R/3A4AD1C0 2014-11-14
> 
> diego at str957-142:~$ tar cvfz GnuPG-backup.tar.gz --exclude random_seed .gnupg
> diego at str957-142:~$ gpg --clearsign GnuPG-backup.tar.gz
> 
> È necessaria una passphrase per sbloccare la chiave segreta
> dell'utente: "Diego <test at example.com>"
> 2048-bit chiave RSA, ID F9B9D307, creata 2014-11-14
> 
> diego at str957-142:~$ ls GnuPG-backup.tar.gz*
> GnuPG-backup.tar.gz  GnuPG-backup.tar.gz.asc
> diego at str957-142:~$ scp GnuPG-backup.tar.gz diego at str957-004:/home/diego
> 
> Then on the other PC:
> 
> diego at str957-004:~$ tar xvfz GnuPG-backup.tar.gz
> .gnupg/
> .gnupg/gpg-agent-info
> .gnupg/pubring.kbx
> .gnupg/gpg.conf
> .gnupg/private-keys-v1.d/
> .gnupg/reader_0.status
> .gnupg/pubring.gpg~
> .gnupg/secring.gpg
> .gnupg/scdaemon.conf
> .gnupg/gpa.conf
> .gnupg/trustdb.gpg
> .gnupg/pubring.gpg
> diego at str957-004:~$ gpg --clearsign GnuPG-backup.tar.gz
> 
> È necessaria una passphrase per sbloccare la chiave segreta
> dell'utente: "Diego <test at example.com>"
> 2048-bit chiave RSA, ID F9B9D307, creata 2014-11-14
> 
> diego at str957-004:~$ gpg --verify GnuPG-backup.tar.gz.asc
> gpg: Firma eseguita in data ven 14 nov 2014 14:07:57 CET usando RSA, ID chiave F9B9D307
> gpg: Firma valida da "Diego <test at example.com>"
> 
>> I notice that no one on this list - for all the talk of "oh I've done it" can offer no
>> practical information has to HOW. No one. No one. No one knows how to do this simple task.
>> In all my 20 years I have never found out how. Perhaps things are different under a Windows
>> O/S but on Linux there is NO SOLUTION.
> Done just now in Ubuntu. So there's an error on your side.
> 
> BYtE,
>  Diego.
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
I have a clean install of 64 bit LXD - all programmes are working 100 per cent. My keys get
imported perfectly - every programme including Enigmail knows they are there. But when I try
to sign or sign and encrypt I get the error referred too. No amount of copying no amount of
backups no amount of anything will change that fact.

David


-- 
“See the sanity of the man! No gods, no angels, no demons, no body. Nothing of the
kind.Stern, sane,every brain-cell perfect and complete even at the moment of death. No
delusion.” https://linuxcounter.net/user/512854.html - http://gbenet.com