Live data from Hacker News

The Bitcoin Piñata

ownme.ipredator.se

71–80 of 112 posts

Re: The Bitcoin Piñata

#71
post #68
post #66

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?

DDoS

edit: now back

Re: The Bitcoin Piñata

#76
post #10

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!

Exactly, so if there is a breach, then we've learned about something we need to secure better (win). If there's no breach — and provided people did try to break in — then we're only incrementally more confident in the stack (kind of a cautious win).

Re: The Bitcoin Piñata

#77
post #65
post #63

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

Are the DNS requests used only to scale up in anticipation of more traffic, or is a steady stream of DNS requests required to keep the instances running once they are started? I see that there is an expiration TTL, but what happens if there is a download in progress for longer than the VM expiration time?

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?

Re: The Bitcoin Piñata

#78
post #39
post #17

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.

Bitcoin has a separate schema for signing textual messages with a special magic prefix ('\x18Bitcoin Signed Message:\n'), which would prevent such an attack.

Edit: here's a JavaScript implementation I wrote that does that, if anyone is interested in details: https://github.com/cryptocoinjs/coinmsg/blob/d2cb985dd9994f1...

Re: The Bitcoin Piñata

#79
post #68
post #66

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?

Back up for me!
Post reply on HN