Earlier quoted context omitted.
I'm part of the Mirage team but when I say 'authors' I'm specifically referring to the people who wrote the Piñata code.
The site is down now. Any idea why? Too much traffic, or DDos, or other hack?
edit: now back
71–80 of 112 posts
Update: DDoS, SYN flood. Stay tuned...
Earlier quoted context omitted.
The site is down now. Any idea why? Too much traffic, or DDos, or other hack?
Syn flood...
Earlier quoted context omitted.
> "and want to find out/demonstrate how secure it is" As the page (and my post) emphatically state, this contest cannot prove anything about how secure it is. That distinction is really important.
But it can demonstrate how insecure it is!
I'm more interested in the OS they hosted their site on. Mirage, developed in OCaml for the cloud. The part that really interested me: "If a sudden spike in traffic occurs, the web-servers can be configured to create and deploy copies of themselves to service the demand. This auto-scaling happens so quickly that an incoming connection can trigger the creation of new server and the new server can then handle that requ…
Yup, this is work in progress. The first part of this is Jitsu, which is a DNS server that can spin up Unikernels on an incoming request. https://github.com/MagnusS/jitsu
Also how well does this work with persistent HTTP connections (and TLS handshakes)? i.e. will the browser keep a persistent connection to the jitsu proxy and the actual requests might be served by different VMs?
Suggestion: add an endpoint on the piñata that proves it has the private key. You can do this using Bitcoin's sign message method.
And then I just make it sign a message sending all the btc to my address, then broadcast that publicly. Very bad idea to sign everything that comes your way, kind of like `eval` on text input.
Edit: here's a JavaScript implementation I wrote that does that, if anyone is interested in details: https://github.com/cryptocoinjs/coinmsg/blob/d2cb985dd9994f1...