Lee: Actually, I don't think there's an explicit intention:

> Why are we doing this? A year ago we started to develop a TLS
implementation from scratch. Now, we want to boost our confidence in the
TLS implementation we've developed and show that robust systems software
can be written in a functional language.

Also: Pinyata!

Peter: Great point. I hadn't seen it before, but seems it would be great if
it became a security trend, like having a warrant canary has. Your
improvement makes a ton of sense.


--------------------------------------------
Q: Why is this email [hopefully] five sentences or less? | A:
http://five.sentenc.es

*NOTE* that my incoming emails are delayed from arriving in my inbox until
9am daily. If you need to reach me sooner, please use other means of
getting in touch. #slowwebmovement
<http://www.musubimail.com/gmail_timer.html>

On Wed, Feb 11, 2015 at 3:59 AM, Peter Todd <[email protected]> wrote:

> On Tue, Feb 10, 2015 at 01:38:52PM -0500, Patrick Connolly wrote:
> > https://news.ycombinator.com/item?id=9027743
> >
> > Would this be an interesting thing to put on a duplicate (...or
> > production?) system and publicize?
>
> Doesn't look like the site actually proves that the "Piñata" actually
> has the private key in question; it should be willing to sign a message
> on demand proving it does. Bitcoin Core has a well-known
> feature/standard way of signing and validating messages that they could
> use for this called signmessage.
>
> > Might be an interesting practise for creating a form of canary,
> especially
> > for projects that perhaps can't afford full and constant audits.
>
> Lots of people leave BTC on important servers in unencrypted wallets in
> well-known formats (e.g. Bitcoin Core's ~/.bitcoin/wallet.dat) to detect
> intrusions.
>
> --
> 'peter'[:-1]@petertodd.org
> 0000000000000000027c4628700f9b75f421c74af987df9b389e0d063d8b63df
>
_______________________________________________
List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
To unsubscribe, email:  [email protected]

Reply via email to