On 18 Jun 2015, at 11:03, Thomas Gazagnaire wrote:
>> This reminded me (as I mentioned yesterday) that we've made several
>> breaking API changes recently, and it would be very nice if there were
>> a page on the web-site listing breaking API changes, saying:
>>
>> 1. What the change is.
>> 2.
> This reminded me (as I mentioned yesterday) that we've made several
> breaking API changes recently, and it would be very nice if there were
> a page on the web-site listing breaking API changes, saying:
>
> 1. What the change is.
> 2. What error you are likely to see.
> 3. How to update your co
On 20 May 2015 at 14:56, Thomas Leonard wrote:
> On 20 May 2015 at 14:40, Amir Chaudhry wrote:
>> Hi folks,
>>
>> The TLS work is proceeding well and you might have noticed that
>> https://mirage.io is working, which is using the TLS stack. Since we’re on
>> the brink of doing some releases, i
> On 20 May 2015, at 17:11, Anil Madhavapeddy wrote:
>
> On 20 May 2015, at 17:01, Mindy wrote:
>>
>> Good news or bad news, depending on how you slice it: running the extremely
>> naive test script below:
>>
>> ```
>> for i in `seq 1 2000`; do curl -1 -k
>> https://secure-web.cisco.com/1g-
Thinking similarly, I tested whether it crashes serving over cohttp
without TLS, and it seems not to; I'll check that next. Also just made
an issue: https://github.com/mirage/mirage/issues/406
On 05/20/2015 05:17 PM, Hannes Mehnert wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
On 05
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
On 05/20/2015 17:01, Mindy wrote:
> Good news or bad news, depending on how you slice it: running the
> extremely naive test script below:
>
> ``` for i in `seq 1 2000`; do curl -1 -k https://192.168.3.2
> >/dev/null; done ```
>
> against a uniker
On 20 May 2015, at 17:01, Mindy wrote:
>
> Good news or bad news, depending on how you slice it: running the extremely
> naive test script below:
>
> ```
> for i in `seq 1 2000`; do curl -1 -k https://192.168.3.2 >/dev/null; done
> ```
>
> against a unikernel generated with mirage-seal results
Good news or bad news, depending on how you slice it: running the
extremely naive test script below:
```
for i in `seq 1 2000`; do curl -1 -k https://192.168.3.2 >/dev/null; done
```
against a unikernel generated with mirage-seal results in the following:
```
[192.168.3.1:59481] TLS ok
[658] s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
sure, great idea.. now at
https://github.com/hannesm/mirage-www/blob/tls-tools/tmpl/wiki/tls.md
hannes
On 05/20/2015 15:20, Anil Madhavapeddy wrote:
> I can edit this with some improvements about where to get keys
> from. However, instead of a blog
I can edit this with some improvements about where to get keys from.
However, instead of a blog post, could we make this into a docs page
on the site so that we can make ongoing edits? Then the blog post
could just reference the wiki page as a
permalink.
(In the medium term, I intend to remove
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hey,
I briefly wrote up what is the current set of tools available:
https://github.com/hannesm/mirage-www/blob/tls-tools/tmpl/blog/using-tls
.md
It would be great to extend this with things I forgot and with more
detailed instructions how to use t
On 20 May 2015 at 14:40, Amir Chaudhry wrote:
> Hi folks,
>
> The TLS work is proceeding well and you might have noticed that
> https://mirage.io is working, which is using the TLS stack. Since we’re on
> the brink of doing some releases, it’s important that we get a few more
> actual deployme
On 05/20/2015 02:48 PM, Amir Chaudhry wrote:
On 20 May 2015, at 14:43, Richard Mortier wrote:
Happy to give it a go, not sure how soon I'll be able to get to it. (I
have several related TODOs about my website though, so perhaps on
Friday.)
Thanks and Friday would be fine :)
ISTR there was ta
> On 20 May 2015, at 14:43, Richard Mortier wrote:
>
> Happy to give it a go, not sure how soon I'll be able to get to it. (I
> have several related TODOs about my website though, so perhaps on
> Friday.)
Thanks and Friday would be fine :)
> ISTR there was talk of producing step-by-step instru
Happy to give it a go, not sure how soon I'll be able to get to it. (I
have several related TODOs about my website though, so perhaps on
Friday.)
ISTR there was talk of producing step-by-step instructions for how to
handle the keys, certs etc required -- did that happen yet? Got a
pointer?
On 20
Hi folks,
The TLS work is proceeding well and you might have noticed that
https://mirage.io is working, which is using the TLS stack. Since we’re on the
brink of doing some releases, it’s important that we get a few more actual
deployments out there to gather more feedback and highlight any is
16 matches
Mail list logo
