On Tue, Sep 20, 2016 at 12:38:43PM -0400, Steve Kinney wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On the downside, it makes denying that you wrote something all but
> impossible - "somebody stole my signing key and its pass phrase" is
> not what someone who is trying to avoid emb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/20/2016 02:19 PM, Georgi Guninski wrote:
> On Tue, Sep 20, 2016 at 12:38:43PM -0400, Steve Kinney wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On the downside, it makes denying that you wrote something all
>> but impossible -
On Tue, Sep 20, 2016, 14:58 Steve Kinney wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 09/20/2016 02:19 PM, Georgi Guninski wrote:
> > On Tue, Sep 20, 2016 at 12:38:43PM -0400, Steve Kinney wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> >>
> >> On the downside,
On Tue, Sep 20, 2016 at 05:57:59PM -0400, Steve Kinney wrote:
> > and to debian, who memset() what they read from /dev/random.
>
> Sounds like a personal issue to me...
>
I deny this and actually use debian. Their disclaimer cover their asses.
Still criticizing publicly OS vendors for major screw
On Tue, Sep 20, 2016 at 05:57:59PM -0400, Steve Kinney wrote:
> > search the interwebz for references.
>
> TL;DR
>
Here are some links of the more important screwups IMHO.
Suspect zero or more of (spec) backdoors, social engineering, gross
incompetence:
https://lists.gnupg.org/pipermail/gnupg-a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/21/2016 03:56 AM, Georgi Guninski wrote:
> On Tue, Sep 20, 2016 at 05:57:59PM -0400, Steve Kinney wrote:
>>> search the interwebz for references.
>>
>> TL;DR
>>
>
> Here are some links of the more important screwups IMHO.
Below: The kind
