(Since this has taken a turn for the GnuPG-specific, I have migrated
this thread to GnuPG-Users. It was originally found on the IETF OpenPGP
working group page.)
even though it's not default, you can change your gpg.conf(5) to
use a specific hashing algorithm
In particular, set the
On 10/08/14 20:48, Hauke Laging wrote:
Am So 10.08.2014, 20:39:26 schrieb da...@gbenet.com:
david@laptop1:~$ gpg-agent --daemon
GPG_AGENT_INFO=/tmp/gpg-6uIYXp/S.gpg-agent:1874:1; export
You obviously have not set
use-standard-socket
in the config file gpg-agent.conf
Hauke
Hauke,
Hi,
[94 lines of full quote deleted - pretty please strip quote to what is
needed. I nearly missed your question]
On Sat, 9 Aug 2014 22:52, bra...@majic.rs said:
Skimming through the description, does it mean that users with OpenPGP
cards should be impervious to this attack? Can the attack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For some of us relatively new Ubuntu Linux users installing the latest
gnupg can be a challenge. I usually end up putting Ubuntu into some
strange state before everything works. I propose a method to help us
newbies. Successful installation steps
On 10/08/14 09:13, da...@gbenet.com wrote:
Hi All,
Am at a loss now. I've Thunderbird 31 and Enigmail 1.7
Since this upgrade I've had various issues - unable to sign unable to encrypt
- I get an
error message from Enigmail Error - bad passphrase - when I've not even
entered it at the
On Mon, 11 Aug 2014 06:56, mac3...@gmail.com said:
close to succeeding. npth requires LDAP that requires something
called BerkelyDB that seems to be satisfied by sudo apt-get install
npth has no dependencies except for the system's native thread library
(i.e pthread).
Shalom-Salam,
A few weeks ago on -devel I made a proposal for a FAQ change. So far
I've received feedback from three people, all of it fairly positive, all
suggesting mild changes. The following represents a final draft, which
I'm now presenting on -users to get the most visibility/feedback. If
the
On 11-08-2014 8:49, Robert J. Hansen wrote:
On Enigmail, I recently had a frustrating
experience helping a user who was trying to use GnuPG to exchange
traffic with a PGP *2.6* user... a codebase which is about 20 years old now.
Fixing the packet order when --pgp2 or --rfc1991 are used would
For some of us relatively new Ubuntu Linux users installing the
latest gnupg can be a challenge.
The latest GnuPG is in the Ubuntu repositories, last I checked.
Ubuntu's normally pretty good about keeping current.
With respect to GnuPG 2.1, it's still in progress and hasn't yet been
released.
On 11/08/14 21:05, Robert J. Hansen wrote:
For some of us relatively new Ubuntu Linux users installing the
latest gnupg can be a challenge.
The latest GnuPG is in the Ubuntu repositories, last I checked.
Ubuntu's normally pretty good about keeping current.
I'm also a new Ubuntu user
Hi,
please remove us from the mailing list. We are not longer using GnuPG in our
company.
Mit freundlichen Grüßen / Kind regards
__
Ing. Roman Höller, MSc
Informationstechnologie
Information Technology
Kommunalkredit Austria AG
1092 Wien, Türkenstraße 9
Tel.: +43 (0)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you Werner, you are right about npth. The dependency call came
when ./configure of Gnupg-2.1 was attempted. Then comes the message
*** You need a LDAP library to build this program.
I am getting closer! After sudo apt-get install libdb-dev
On Mon, 11 Aug 2014 19:31, joh...@vulcan.xs4all.nl said:
Fixing the packet order when --pgp2 or --rfc1991 are used would help a
Too complicated and breaks too much.
lot. And now I assume that pgp 2 will not pass away before the
It is quite funny that some people here demand a ban of SHA-1
On Mon, 11 Aug 2014 13:21, e...@kommunalkredit.at said:
please remove us from the mailing list. We are not longer using GnuPG in our
company.
What about visiting the URL shown as last line of each mail send through
this mailing list? Or looking into the list mail headers?
Shalom-Salam,
On Aug 11, 2014, at 1:31 PM, Johan Wevers joh...@vulcan.xs4all.nl wrote:
On 11-08-2014 8:49, Robert J. Hansen wrote:
On Enigmail, I recently had a frustrating
experience helping a user who was trying to use GnuPG to exchange
traffic with a PGP *2.6* user... a codebase which is about 20
Rather than fixing RFC-1991 support, why not go in the other
direction and make it clear that it isn't supported, and won't work?
Sounds like an excellent plan to me.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
16 matches
Mail list logo
