Hello.
I'm using GNU/Linux (distro: Ubuntu), not FreeBSD - sorry, I forgot to
inform this. But, anyway, I did what you instructed:
> $ gpg --version
> gpg (GnuPG) 1.4.20
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Home: ~/.gnupg
> Supported algorithms:
> Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
> Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256,
>               TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256
> Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512,
>                    SHA224
> Compression: Uncompressed, ZIP, ZLIB, BZIP2
And:
> $ ls -lh /usr/bin/gpg*
> -rwxr-xr-x 1 root root 985K Aug 18 08:54 /usr/bin/gpg
> -rwxr-xr-x 1 root root 896K Apr  8  2016 /usr/bin/gpg2
> -rwxr-xr-x 1 root root 345K Apr  8  2016 /usr/bin/gpg-agent
> -rwxr-xr-x 1 root root 137K Apr  8  2016 /usr/bin/gpgconf
> -rwxr-xr-x 1 root root 139K Apr  8  2016 /usr/bin/gpg-connect-agent
> -rwxr-xr-x 1 root root  27K Apr  8  2016 /usr/bin/gpgparsemail
> -rwxr-xr-x 1 root root  59K Aug 18 08:54 /usr/bin/gpgsplit
> -rwxr-xr-x 1 root root 364K Aug 18 08:54 /usr/bin/gpgv
> -rwxr-xr-x 1 root root 3,3K Aug 18 08:54 /usr/bin/gpg-zip
So, I have both gpg and gpg2. I can't create a symlink because gpg
really exist, it's used for the VPN (when I uninstalled gpg yesterday,
the VPN, I could not login anymore, and when I reinstalled the VPN
today, it installed gpg too).

Here's gpg2:
> $ gpg2 --version
> gpg (GnuPG) 2.1.11
> libgcrypt 1.6.5
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Home: ~/.gnupg
> Supported algorithms:
> Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
> Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256,
>               TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256
> Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
> Compression: Uncompressed, ZIP, ZLIB, BZIP2

Should then I use /gpg2 --gen-key/? Maybe /gpg2 --full-generate-key/?

Em 15/02/2017 10:53, LeRoy escreveu:
> On 02/14/2017 06:47 PM, Anders Bateva wrote:
> > Hello. I've been plagued, on the last months, by the impossibility
> > of creating a key pair for me. I had given up, but as I continue to
> > use e-mail, I still feel the need to encrypt it, but I can't!
>
> > I opened "enigmail configuration assistant"->"standard
> > configuration", and, as always, this process progressed a little on
> > the first 20 minutes (1 tick on the progress bar). Then, it stopped
> > for 1 hour. I already tried before letting it alone for more than 4
> > hours, and no progress was made. It simply can't generate the keys.
> > The same happens by the way "enigmail key manager -> generate ->
> > new key par".
>
> > I already uninstalled gnupg, and I'm sure I have gnupg2. I have
> > Thunderbird 45.7.0 with Enigmail 1.9.6.1.
>
> > What to do?
>
>
> I noticed that you are using free BSD from the headers so I assume
> that you know how to use a terminal.
>
> Open up your favorite terminal an enter:
> gpg --version
> gpg (GnuPG) 2.1.18
> libgcrypt 1.7.6
> Copyright (C) 2017 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <https://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Home: /home/leroy/.gnupg
> Supported algorithms:
> Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
> Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
>         CAMELLIA128, CAMELLIA192, CAMELLIA256
> Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
> Compression: Uncompressed, ZIP, ZLIB, BZIP2
>
> You should get a response something like above.  If you do not get a
> response maybe you should see if gpg is installed on your system.  My
> favorite way is:
>
> ls -lh /usr/bin/gpg*
> lrwxrwxrwx 1 root root    4 Jan 23 19:00 /usr/bin/gpg -> gpg2
> -rwxr-xr-x 1 root root 989K Nov  2  2015 /usr/bin/gpg1
> -rwxr-xr-x 1 root root  59K Nov  2  2015 /usr/bin/gpg1split
> -rwxr-xr-x 1 root root 364K Nov  2  2015 /usr/bin/gpg1v
> -rwxr-xr-x 1 root root 3.3K Nov  2  2015 /usr/bin/gpg1-zip
> -rwxr-xr-x 1 root root 930K Jan 23 19:00 /usr/bin/gpg2
> -rwxr-xr-x 1 root root 360K Jan 23 19:00 /usr/bin/gpg-agent
> -rwxr-xr-x 1 root root 143K Jan 23 19:00 /usr/bin/gpgconf
> -rwxr-xr-x 1 root root 149K Jan 23 19:00 /usr/bin/gpg-connect-agent
> -rwxr-xr-x 1 root root  27K Dec 28 01:45 /usr/bin/gpg-error
> -rwxr-xr-x 1 root root 2.2K Dec 28 01:45 /usr/bin/gpg-error-config
> -rwxr-xr-x 1 root root 4.8K Oct 27 12:05 /usr/bin/gpgme-config
> -rwxr-xr-x 1 root root  68K Oct 27 12:05 /usr/bin/gpgme-tool
> -rwxr-xr-x 1 root root  23K Jan 23 19:00 /usr/bin/gpgparsemail
> -rwxr-xr-x 1 root root 190K Jan 23 19:00 /usr/bin/gpgscm
> -rwxr-xr-x 1 root root 455K Jan 23 19:00 /usr/bin/gpgsm
> -rwxr-xr-x 1 root root 141K Jan 23 19:00 /usr/bin/gpgtar
> lrwxrwxrwx 1 root root    5 Jan 23 19:00 /usr/bin/gpgv -> gpgv2
> -rwxr-xr-x 1 root root 405K Jan 23 19:00 /usr/bin/gpgv2
> -rwxr-xr-x 1 root root 3.4K Jan 23 19:00 /usr/bin/gpg-zip
>
> As you can see I have both versions of gpg installed and /usr/bin/gpg
> is actually a symlink to gpg2.  I think that enigmail requires this
> symlink since it probably calls /usr/bin/gpg.  If you have
> /usr/bin/gpg2 without a symlink gpg pointing to it then I would create
> a symlink manually.
>
> If there is no response from the ls command then you need to install
> using the bsd pkg command.
>
> If you have a symlink gpg > gpg2 why not attempt to create a key using
> gpg on the command line.
>
> gpg --gen-key
> gpg (GnuPG) 2.1.18; Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Note: Use "gpg2 --full-generate-key" for a full featured key
> generation dialog.
>
> If the gpg symlink points to gpg1 then the newer versions of enigmail
> probably would not work.  You need the gpg symlink to point to gpg2.
>
> ...
>
> If you can generate a key manually then the problem is with enigmail.
>  If you cannot generate a key manually then the problem is with gnupg.
>
> I hope that this rambling from a paranoid old man helps :-)
>
> > _______________________________________________ > enigmail-users
mailing list > [email protected] > To unsubscribe or make
changes to your subscription click here: >
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to