Recent submissions

Comment · 11 years ago
Maybe it is a cure for ADD?
Comment · 11 years ago
How many production servers have you been responsible for in your lifetime?

"There is no difference to running an executable. "

... There are these following differences.

1. That url, assuming no malicious 3rd-party/nation-state is spoofing the response, could return any different version of the installer resource at any given time.

2. That url might not always be available, for any number of reasons, and how is someone who wants to "discover" this software when they are looking through their available package list?

3. Who knows what that url is "suppose to do" ... there is no signing process, peer review process, nothing, you get whatever the apache server on the other side of that HTTP request wants to give you, and your gonna send that right into your root shell...

4. Unlike a package, sitting in my personal safe, self host, audited, self-verified debian package repository mirror ... this URL might not work tomorrow, it might not work at 3:35am when my primary server took a shit and i need to rebuild the whole stack... who knows what this URL will do in between subsequent runs... it could return 2 different things when I am trying to build a cluster of this product.

Comment · 11 years ago
"Nobody in their sane mine should curl a script into bash to install a product"

This, so much this.

I was actually extremely excited over a similar product "flynn"... but they have also lost their mind when it comes to installation: https://flynn.io/docs/installation

> sudo bash < <(curl -fsSL https://dl.flynn.io/install-flynn)

Seriously?

How is that any easier than just providing a package for any given distro?

I mean, for fucks sake, just give me the URL to a tarball with a fucking Makefile in it. I can handle the rest, thank you very much.

The security concerns alone should force any sane system engineer to never pipe curl to sudo'ed bash process.

Comment · 11 years ago
... running a financial institution on servers you don't have physical access to, What is the worse that could happen?

Isn't physical access security like OpSec 101?

Comment · 11 years ago
What about the laws the operators of the exchange broke by running un-audited code to handle financial transactions?
Comment · 11 years ago
Exactly... From my perspective, their plan worked perfectly.

1. Open an exchange. 2. Collect real money in exchange for fake money. 3. "Get hacked" losing all the fake money and keeping all the real money.

Comment · 11 years ago
"Do they not plan on there being an official investigation?"

How do you officially investigate someone stealing your monopoly money?

Where is the FDIC insurance? Exactly what are they suppose to tell the police? The FBI? ... oh thats right, nothing, because they are not a bank, and the only thing "stolen" was some ones and zeroes off a hard-drive.

Seriously though... where is the police report on this? Or any of the other hacked bitcoin exchanges for that matter?

Comment · 12 years ago
I like to refer to depression as a cliff that is always one step behind you.
Comment · 12 years ago
In today's climate I would be extremely weary of npm installing any core bitcoin tech without a serious line by line audit of the source.
Comment · 12 years ago
Looks like they built their NSA spy module out of coffeescript, neato
Comment · 12 years ago
The story here is: "we have to post bitcoin related articles everyday to keep the price of BTC up"
Comment · 12 years ago
Comment · 12 years ago
More like, "Dropbox is like NFS for desktops"
Comment · 12 years ago
Good luck with those stale NFS file handles...

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton