News for hackers. Stuff that matters.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Tuesday February 06, 2018 @10:43PM (#16322096)
Maybe a better question is how to prepare in advance. You can design your systems to avoid retaining user data. Or you can do business from a jurisdiction that doesn't recognize NSLs. Or perhaps from an unknown jurisdiction.
Re:A Developer’s Guide to Responding to National Security Le... by nolok on Wednesday February 07, 2018 @07:20AM (#16323927)
> Or perhaps from an unknown jurisdiction.

Good luck with that, unless your vision of doing business doesn't involve ever charging customers, especially for b2b.

Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @03:52PM (#16327900)
Yes, it's certainly not a viable option for mass-market business. But there are niches where such OPSEC is standard practice. Some, such as drugs and arms dealing, were huge well before Bitcoin. Also hosting services for spam and botnets.

What Silk Road and Bitcoin demonstrated is the huge popularity of dark markets for retail drug sales. With product authenticity and seller reliability attested through customer reviews. And without risk of meatspace violence (except if busted, of course).

And sure, that stuff is still widely illegal. However, when laws are ignored by substantial minorities, their legitimacy becomes questionable. African Americans didn't end segregation in the US through petitioning legislatures. They broke the laws, creating a crisis, and forcing the federal government to act. Lesbian and gay activists did much the same, at least initially.

Re:A Developer’s Guide to Responding to National Security Le... by wyager on Wednesday February 07, 2018 @09:48AM (#16324702)
This is one of the primary use cases Bitcoin was invented to address.
Re:A Developer’s Guide to Responding to National Security Le... by nolok on Wednesday February 07, 2018 @11:31AM (#16325584)
Given that even payment processors like Stripe are removing it because the verification time is too long, it is sadly not satisfying solution in any way.

Also, again, good luck getting any b2b when you tell them they need to pay in bitcoin only.

Re:A Developer’s Guide to Responding to National Security Le... by wyager on Wednesday February 07, 2018 @11:14PM (#16330123)
Stripe removed it primarily because they got almost no adoption (most merchants I know using stripe weren’t even aware they offered it; merchants had to opt in).

Verification times are clearly an engineering problem, not a fundamental issue. Long-term solutions are currently under experimentation (lightning, DAG currencies, etc.)

Re:A Developer’s Guide to Responding to National Security Le... by linuxps2 on Wednesday February 07, 2018 @02:19PM (#16327194)
Luckily that's no longer an issue now that interest has faded and the mempool has cleared. Also, reducing on-chain transactions (and thus keeping the mempool clear, on-chain fees low, and verification times low) is pretty much the main use case of Lightening Network. The massive rise in fees and tx congestion was caused by the massive interest in BTC at the end of 2017. Something tells me if you are doing B2B in a shady jurisdiction, the companies you are doing work with would be more than willing to jump through hoops to deal exclusively in BTC
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @03:37PM (#16327784)
Yes, that's been a benefit of the collapse in speculative interest. Now transactions are affordable again. And regardless of Bitcoin's eventual fate, I'm rather confident that something like it or better will be available ongoingly.
Re:A Developer’s Guide to Responding to National Security Le... by Feniks on Wednesday February 07, 2018 @10:16PM (#16329906)
You still have to buy crypto with real money. Real money CAN be traced.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @10:46PM (#16330026)
Not necessarily. One can earn cryptocurrencies. That's especially so for coders and such. But yes, conversion with "real money" is problematic.

For small amounts, meatspace trades are doable using LocalBitcoins.com etc. For huge amounts, I suspect that expert assistance is available. It's the middle ground that's nontrivial.

Re:A Developer’s Guide to Responding to National Security Le... by totalZero on Wednesday February 07, 2018 @11:11PM (#16330119)
> You still have to buy crypto with real money

False. You can mine it, you can receive it for free from someone else, and you can exchange goods/services for it.

Re:A Developer’s Guide to Responding to National Security Le... by jebeng on Wednesday February 07, 2018 @10:20AM (#16324955)
I'm interested to see if the US is able to do anything to Bitfinex now as a litmus test to see how wide their reach is in 2018. As far as I know they have zero US presence, and don't offer services to US customers.

BTC-e went down hard for example. But they had some much more obvious links with criminal enterprise.

Although even if it is possible to stay outside of the reach of the US, losing access to the international banking system is quite the handicap for any business.

Re:A Developer’s Guide to Responding to National Security Le... by jonnybgood on Wednesday February 07, 2018 @03:09AM (#16322935)
> Or you can do business from a jurisdiction that doesn't recognize NSLs. Or perhaps from an unknown jurisdiction.

That means not doing business in the US at all.

Re:A Developer’s Guide to Responding to National Security Le... by wyager on Wednesday February 07, 2018 @09:52AM (#16324730)
If you sell physical goods, maybe not. If you’re a middleman or you sell digital goods, you still can do business with people living in the US.
Re:A Developer’s Guide to Responding to National Security Le... by dboreham on Wednesday February 07, 2018 @11:18AM (#16325444)
Not if you want to get paid.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:47PM (#16329002)
There are many ways to get paid. Even before Bitcoin etc.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:29PM (#16328935)
You can do business with US customers. It's not uncommon. Maybe they need some OPSEC, but hey.
Re:A Developer’s Guide to Responding to National Security Le... by JetSpiegel on Wednesday February 07, 2018 @03:17AM (#16322961)
Which makes it fair game for direct targeted attacks by the NSA.
Re:A Developer’s Guide to Responding to National Security Le... by MertsA on Wednesday February 07, 2018 @07:51AM (#16324050)
The NSA has made direct targeted attacks at US companies in the past. Just look at Google, they got NSLs and had to cooperate with PRISM yet at the same time the NSA still dug up their fiber and tapped it.

With the NSA's twisted logic that a search is not a search unless it matches and it's fine to search data so long as there's a chance it involves a non-US citizen I think jurisdiction is largely irrelevant for attacks other than the necessity of one seeing as the NSA has access to a secret court that has a history of never siding against them.

I'd view eliminating tyrannical government orders as a plus.

Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:33PM (#16328954)
Indeed. The NSA has also intercepted device shipments, in order to install backdoors. And some US firms have resorted to shipping through more-or-less anonymous intermediaries to circumvent that.
Re:A Developer’s Guide to Responding to National Security Le... by cesarb on Wednesday February 07, 2018 @07:21AM (#16323930)
For someone outside the USA, a targeted attack by the NSA is no different than a targeted attack by anyone else. They are breaking the law, and you are allowed and supposed to defend against them. If you are within the USA, however, they can use things like these National Security Letters which you are not allowed to go against.
Re:A Developer’s Guide to Responding to National Security Le... by geofft on Wednesday February 07, 2018 @07:32AM (#16323983)
This is incorrect for a few reasons: you can certainly defend against NSLs, even those that you can't defend against are targeted (see the ones Twilio received), they're from the FBI and not the NSA, and as hackers the NSA is more skilled and more well-funded than most other attackers you're defending against.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:40PM (#16328981)
The NSA does have lots of skilled hackers. But so do other national TLAs. And there are many freelance hackers.
Re:A Developer’s Guide to Responding to National Security Le... by Feniks on Wednesday February 07, 2018 @10:20PM (#16329914)
Most countries will happily throw anyone under the bus if the US intelligence services ask them too. Besides if you're doing something the NSA doesn't like local law enforcement probably won't like it either.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @11:33PM (#16330194)
Most countries, yes. But some countries, clearly no. Snowden is still in Russia, for example. And China typically doesn't cooperate with the NSA and its friends.
Re:A Developer’s Guide to Responding to National Security Le... by bpanon on Wednesday February 07, 2018 @04:52AM (#16323343)
The entire universe is fair game for the NSA.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:36PM (#16328962)
Right. They pretty much do whatever they want, and lie as necessary to frustrate oversight, and protect operational methods. They are, after all, a branch of the military.
Re:A Developer’s Guide to Responding to National Security Le... by jonnybgood on Wednesday February 07, 2018 @03:25AM (#16323010)
You can still be targeted if you’re a foreign business operating in the US.
Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:38PM (#16328970)
Yes, you can and will be targeted. So if you go that route, you'd better know what you're doing.
Re:A Developer’s Guide to Responding to National Security Le... by dboreham on Wednesday February 07, 2018 @11:27AM (#16325529)
>You can design your systems to avoid retaining user data.

This helps for data from the past, but TLAs can order you to change your code such that it will in future retain data they want to see.

Re:A Developer’s Guide to Responding to National Security Le... by mirimir on Wednesday February 07, 2018 @06:46PM (#16329000)
Right, that's why Lavabit shut down. And that's why ProtonMail operates from Switzerland, and CounterMail from Sweden. But the best hardcore option is not being vulnerable to coercion.