On 12/04/2014 01:23 AM, Werner Koch wrote:
> On Tue, 11 Nov 2014 18:35, m...@monaco.cx said:
>> Does anyone have gpg-agent forwarding working with SSH's recent generic
>> socket
>> forwarding? Does it still require socat on one end, because I've only been
>> able
>> to specify a socket path on th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/02/15 20:40, Werner Koch wrote:
> Since the start of the funding campaign in December several thousand people
> have been kind enough to donate a total of 25 Euro to support this
> project. In addition the Linux Foundation gave a grant of $
On Thu, 12 Feb 2015 00:25, 2014-667rhzu3dc-lists-gro...@riseup.net said:
> If GnuPG 2.1.x finds an existing secring.gpg, that is used. If not,
> the new file format secring.kbx is used.
Nope. You will never find a secring.kbc. 2.1 uses secring.gpg only in
this ways:
If secring.gpg exists and t
On 12/02/15 13:10, Peter Lebbing wrote:
> On 11/02/15 20:40, Werner Koch wrote:
>> > Since the start of the funding campaign in December several thousand people
>> > have been kind enough to donate a total of 25 Euro to support this
>> > project. In addition the Linux Foundation gave a grant o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I recently got a new Nexus 5, with NFC. Supposedly it supports ISO
7816-4. Is there any possibility of, for instance, porting gnuk to
android? I'd love to use my smartphone as a smartcard. Of course, the
smartphone wouldn't have as many anti-tamp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.02.15 20:40, Werner Koch wrote:
> Hello!
>
> The GnuPG Project is pleased to announce the availability of the
> third release of GnuPG modern: Version 2.1.2.
The "usual" installer for Mac OS X is now available from
https://sourceforge.net/p/
Hi!
I introduced a regression in 2.1.2 which may lead to a non working
pinpad reader. If you experience problems, please try the attached
patch.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
>From 07a71da479daaac43b8c5b1034a1e66f96bdbc48 Mon Sep 17 0
On Thu, 12 Feb 2015 18:31, patr...@enigmail.net said:
> The "usual" installer for Mac OS X is now available from
> https://sourceforge.net/p/gpgosx/docu/Download/
I just added the URL to the download page.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
in my quest of the perfect setup, I am asking myself what is the
prefered way to sign a message: inline (like this one) or using a MIME header ?
Is there a big thumb rule to respect ?
Regards
- --
Sent with my mu4e
-BEGIN PGP SIGNATURE-
Hi Stephan,
On 12/02/15 22:46, Stephan Beck wrote:
> Hi, Philip,
>
> Am 11.02.2015 um 22:35 schrieb Philip Jackson:
>> On 11/02/15 21:16, Daniel Kahn Gillmor wrote:
>>> On Wed 2015-02-11 14:02:49 -0500, Philip Jackson wrote:
On 11/02/15 14:59, Brian Minton wrote:
>
> [snip]
>
> In synapti
Hi, Philip,
Am 11.02.2015 um 22:35 schrieb Philip Jackson:
> On 11/02/15 21:16, Daniel Kahn Gillmor wrote:
>> On Wed 2015-02-11 14:02:49 -0500, Philip Jackson wrote:
>>> On 11/02/15 14:59, Brian Minton wrote:
[snip]
> When I try your way from the command line, I get :
>
> $ apt-cache policy gnup
> in my quest of the perfect setup, I am asking myself what is the
> prefered way to sign a message: inline (like this one) or using a
> MIME header ?
>
> Is there a big thumb rule to respect ?
https://www.gnupg.org/faq/gnupg-faq.html#use_pgpmime
smime.p7s
Description: S/MIME Cryptographic Si
On Thu 2015-02-12 18:14:14 -0500, Robert J. Hansen wrote:
>> in my quest of the perfect setup, I am asking myself what is the
>> prefered way to sign a message: inline (like this one) or using a
>> MIME header ?
>>
>> Is there a big thumb rule to respect ?
>
> https://www.gnupg.org/faq/gnupg-faq.
Hello,
Let me record a bit of history.
On 02/13/2015 01:19 AM, Brian Minton wrote:
> I recently got a new Nexus 5, with NFC. Supposedly it supports ISO
> 7816-4. Is there any possibility of, for instance, porting gnuk to
> android? I'd love to use my smartphone as a smartcard. Of course, the
On Thu, 12 Feb 2015 23:46:33 +0100, Xavier Maillard stated:
> Hello,
>
> in my quest of the perfect setup, I am asking myself what is the
> prefered way to sign a message: inline (like this one) or using a MIME
> header ?
>
> Is there a big thumb rule to respect ?
Inline totally destroys a "si
> I don't know if this is true for PGP-Basics, but it is certainly not
> true for enigmail or gnupg-users. Please update the FAQ!
It's still true for PGP-Basics; Enigmail's been bit by it within the
last year, if memory serves, but it's been generally accepted; GnuPG's
been AFAIK stable for it.
Zitat von Xavier Maillard :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
in my quest of the perfect setup, I am asking myself what is the
prefered way to sign a message: inline (like this one) or using a
MIME header ?
Is there a big thumb rule to respect ?
Regards
- --
Sent wit
Jerry writes:
> On Thu, 12 Feb 2015 23:46:33 +0100, Xavier Maillard stated:
>
>> Hello,
>>
>> in my quest of the perfect setup, I am asking myself what is the
>> prefered way to sign a message: inline (like this one) or using a MIME
>> header ?
>>
>> Is there a big thumb rule to respect ?
>
> In
Robert J. Hansen writes:
>> in my quest of the perfect setup, I am asking myself what is the
>> prefered way to sign a message: inline (like this one) or using a
>> MIME header ?
>>
>> Is there a big thumb rule to respect ?
>
> https://www.gnupg.org/faq/gnupg-faq.html#use_pgpmime
THank you for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> Maybe I cannot offer a big rule for THE preferred way. Jerry is
> right, but maybe we HAVE to deal with recipients who have no
> influence to take a mail client which is capable to handle PGP/MIME
> sigbatures properly. Then it is also MY problem.
FWIW, Mac Mail marked this message as spam. Not sure if it universally does
that for all inline sigs, but ... FYI.
Chris
> On 12 Feb 2015, at 23:46, Xavier Maillard wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hello,
>
> in my quest of the perfect setup, I am asking my
21 matches
Mail list logo
