Many of these services are unauditable and should not be used for secure communications. Security is opt-in in cases, and there are even warnings in the article that certain things are not end-to-end encrypted.
1,719 karma · joined January 26, 2016
american west coast / singapore / 東京
the opinions expressed here are my own and not the opinions of my employer. they might not even be my own professional opinions. they are also subject to a lot of change, as they have through the years.
Many of these services are unauditable and should not be used for secure communications. Security is opt-in in cases, and there are even warnings in the article that certain things are not end-to-end encrypted.
Critical voices from where? Outside the United States?
+1 to FBI on this being pretty well targeted; you had to have had a successful login for them to be attempting this in the first place. It's about as precise as they can get; you're only going after users that are active members of the service. They are at least being reasonable in who they are targeting. I can't really think of how they can be more targeted in attempting to deanonymize people in the network.
I don't like this whole NIT garbage because I'm afraid this will lead to fishing expeditions, where you just root everyone on an .onion that happens to visit it, and then clean up with a multitude of search warrants later and hope you get something. I also don't believe it's the FBI's (or America's) job to play world police.
-1 to the FBI, at least: they were (once again) actively serving CP on a compromised server again, which seems like something you shouldn't be doing as an LEA fighting the distribution of the content. Illegal actions shouldn't be taken to fight crime. Distributing the thing you are fighting is the definition of the abyss having gazed into you.
OK, now you have an IP. Now what? You get a warrant and search the place. What do you find? A computer, maybe an amnesic virtual machine. No actual access to the website/onion in question. IMO Tails promotes better opsec when using Tor - you don't leave any traces behind of your browsing activity, and you can't gain persistence on the victim without a sandbox escape, since the Tails VM wipes itself. It is still a defense, but maybe not a good enough one.
Sure, but we can't get TBB rewritten overnight to work instantly with Chromium, and I'm sure there'd be a lot of push back on that.
If you're going to be actively targeted by exploits like this, then you shouldn't give a damn about some of these tradeoffs. If you have journalists/activists willing to go to information war with a nation-state, they shouldn't be surprised when their adversaries have the resources to pwn them. If David wants to fight goliath, they will need to take this into account. The guys with guns and power want their heads.
If the activists/journalists/whatever don't want to take the necessary precautions to use computers to talk to people in a way in which they are protected from capable adversaries, then I'm not sure what it is that they are expecting.
Also, I was recommending these users simply defending in depth by using Tails as a sandbox for a leaky browser, to require a chain of expensive exploits (browser 0day + VM escape 0day). Training someone to install VirtualBox or VMWare and run an ISO from it doesn't really disrupt too much workflow and defends in depth against the browser issues, then again I am likely wrongfully assuming VT-x/VT-d and a lot of RAM on the activists' computers.
There are Windows "sandboxes" like Bromium, and as stated, IIRC EMET will stop the stack pivot here.
PS, if you're ever on the US West Coast or in Singapore, drop me a DM. I'll buy you a drink someplace.
My guess? Some darknet market.
* Sure, this could be some type of awkward false flag, but it seems unlikely to my gut.
This is neither the first nor is the last 0day in Firefox that will affect TBB.
IMO the best practical mitigation against these attacks is sandboxing with an amnesic system like Tails, as even as a VM it will leak a lot less information about the machine it is running on and requires burning both a Firefox 0day and a VM escape to get any real information outside of the real IP address of the user and some basic things out of /proc (although Tails may protect against the latter now). Also, as the whole VM goes away when it's closed, you're not getting persistence on that machine if you just pop the browser.
A 30 second glance at the source code makes it looks like this exploit pivots to attacker-controlled memory on the heap, and spawns a thread using kernel32.dll. As EMET has hardening against attacks like this, I am curious if this exploit works at all on EMET-enabled Windows systems.
You run a custom repo with two packages, your compiled linux-grsec kernel, and a package that contains paxd and paxd exceptions for your typical binaries. Once you find a stable grsecurity kernel config you don't really have much to worry about.
When new updates are released, test them on your test tier with your existing PaX rules and exemptions, and if they pass tests push them into prod. Worst case scenario you disable PaX (and its memory protections) in emergency cases or rollback to the known good version. If you are running "unattended-upgrades" or something else and letting your tiers autopatch themselves, well, that's dangerous to stability in and of itself.
I run -grsec-patched kernels on all of my personal workstations as well. That's when grsec can be a pain.
Yes, I'm being facetious, because that purist approach is impractical in the job market. When I left college C/C++ was what I had done the majority of my development in. I wrote some C yesterday. But nearly all of the development I have done since then has been in a higher-level language like Java, C#, Perl, PHP, Python, or Ruby, all of which I had to pick up and learn for some job somewhere outside of work. And the answer is that learning these things did help me, as I had practical experience with these languages. It's just way worse for front-end these days.
The thing is that the "cool job" job market for front-end guys seems to want people that know the new hotness, and the hotness changes a lot. If you want a job at Facebook or Google etc, it is easy: learn the framework they use in house (React/Angular/etc.) But what if you aren't capable of running the Facebook/Google interview gauntlet, as many are?
You just want a job using the skills you have and are willing to learn. You know JS/HTML/CSS/jQuery. You know how the underlying core concepts work. However, that job posting says you need AngularJS or React or Vue or whatever experience, and your last job was all Knockout.js since the company was older. When you go for the interview, they will take the person with proven experience in the trendier framework. So your job market is fragmented, and if you want mobility between companies -- a big deal when working with startups that might be uncertain -- you have to keep up on all of them to some degree.
I went to a "front end" meetup with some friends that work in typical dev shops not too long ago, and the amount of arguing over frameworks and JS tooling was terrible. Lots of spouting off the opinions of your favorite opinionated framework and a good amount of contempt for the wrong team. I shared a similar opinion as you -- none of them will last and all is old is new again -- and I was practically ignored as an old man unless I was talking about websec concepts.
I don't understand what logic there is in blaming Comey for actions Clinton made. Her and her staff decided to run the server. The FBI did not fabricate something here that needed to be investigated.
I'm going to assume that this pun was intentional by Strano, and sadly I think it's gone past everyone who's in awe of the actual finding.
You're right, and the better term would be something along the lines of "the American capitalist system", or "the American economic system", but those seem too specific. It is a form of capitalism that has found its way through most of Western-style representative democracy and economic planning in its various forms through the 20th century. Usually that's what we call a capitalist system in any definition outside of economics or fringe political science.
Technological progress may be an issue that contributes to this so-called empathy vacuum, but all industries that cause negative externalities (in cyclical or permanent unemployment, or pollution, or wealth disparity, etc) are just as much a problem.
If we want to have this debate, that's great. It needs to happen, especially as our economy ends up with an increasing human labor supply as it's automated away or sent to places where labor is cheaper. The track we are on now will likely end up with massive Gini coefficients worldwide, a ruling class and a noted underclass based upon who was able to achieve capital accumulation while their labor was still worth something.
The problem I have here is that the New Yorker isn't even going for this debate in this article. They are complaining about something and pointing a finger at but a sliver of an issue that they are also a part of.
There is nothing about Silicon Valley that has any less "empathy" than many non-tech organizations. If the financial incentive structure runs against this ideal of "empathy", it happens and is bound to happen. End of story.
The empathy vacuum is real in finance, politics, health insurance, petroleum, pharmaceuticals, law, law enforcement, and virtually any other large bureaucracy in which individual actions are rewarded in spite of impersonal behavior. At the end of the day, people are rewarded for what they bring to the economy, not the mental happiness of a populace, which is not always quantifiable or captured by the market.
What's going to happen with HoloLens? The team doesn't appear to be very large, and it's been stuck in research-land for a while now.