> I have used Enigmail since its inception and have never knowingly
> submitted a log or answered a survey and have always assumed Enigmail
> does not phone home.
It does not.
> Here we disagree. I believe that existing software is not that
> difficult to use. The problem, if there is one, is
> i am not able to follow your documentation and get Gnugp up and running
> locally. I have already tried to download missing dependencies and
> libraries and move them into the right directory, but that is not
> working as i am getting the same error message over and over again.
You will almost
On Mon, 14 Oct 2019 20:43, Kristian Fiskerstrand said:
> was suggested by Kristian and Andre: talking to SCDaemon (scd) with IPC.
> Details need to be discussed, but it would be an optional solution, that
Given that TB already has smartcard support it would be easy if the new
code just makes use
... yes
checking build system type... x86_64-apple-darwin18.7.0
checking host system type... x86_64-apple-darwin18.7.0
configure: autobuild project... gnupg
configure: autobuild revision... 2.2.17
configure: autobuild hostname... anastasias-mbp.hamburg.de.ibm.com
configure: autobuild timestamp...
On 14.10.2019 18:54, Juergen Bruckner via Gnupg-users wrote:
> Hello to all,
>
> well it's a good thing, that openPGP shall be included to TB directly.
>
> But ... as the Mozilla wiki [1] states in the FAQ-Section the following:
>
>
> Q: Will OpenPGP cards be supported for private key storage
Hello to all,
well it's a good thing, that openPGP shall be included to TB directly.
But ... as the Mozilla wiki [1] states in the FAQ-Section the following:
Q: Will OpenPGP cards be supported for private key storage ?
A: Probably not, because we don't use the GnuPG software that's usually
On Mon, 14 Oct 2019 10:54, Phillip Susi said:
>> encryption protocol is S/MIME and the last time I checked S/MIME (well,
>> CMS for the nitpickers) does not supoport any kind of authenticated
>> encryption. In contarst OpenPGP provides this nearly for 2 decades.
>
> What do you mean? S/MIME
Werner Koch via Gnupg-users writes:
> Still, TB is still subject to those attacks because their primary
> encryption protocol is S/MIME and the last time I checked S/MIME (well,
> CMS for the nitpickers) does not supoport any kind of authenticated
> encryption. In contarst OpenPGP provides
On 10/14/19 3:40 AM, Binarus wrote:
>
> On 13.10.2019 22:27, Jeff Allen via Gnupg-users wrote:
>> On 10/13/19 2:21 AM, Patrick Brunschwig wrote:
>>> The vast majority of users of Enigmail (somewhere around 98%) don't use
>>> external built keys.
>>
>> How do you know this?
>>
>
> I don't know
On 14.10.2019 09:17, Patrick Brunschwig wrote:
> Binarus wrote on 13.10.2019 18:27:
> [...]
>> 1) The schedule
>>
>> We have all been educated to update our applications (notably, "internet
>> applications" like browser and email clients) as soon as updates are
>> available; at least, this is
On 13.10.2019 22:27, Jeff Allen via Gnupg-users wrote:
> On 10/13/19 2:21 AM, Patrick Brunschwig wrote:
>> The vast majority of users of Enigmail (somewhere around 98%) don't use
>> external built keys.
>
> How do you know this?
>
I don't know either, but perhaps it is in the debug logs the
Binarus wrote on 13.10.2019 18:27:
[...]
> 1) The schedule
>
> We have all been educated to update our applications (notably, "internet
> applications" like browser and email clients) as soon as updates are
> available; at least, this is true for security updates.
>
> Despite release plans, I
alejandro Cortez wrote:
> gpg: public key decryption failed: Invalid ID
This means that something goes wrong in your private key file for
your token, I suppose.
> Can anyone help debug this?
You can see more information, by following command line:
$ gpg-connect-agent "KEYINFO --list" /bye
13 matches
Mail list logo
