InvertedParallax

joined 1 year ago
[–] InvertedParallax@lemm.ee 12 points 2 months ago

To absolute morons who make sure it comes with a bed cover they never take off.

[–] InvertedParallax@lemm.ee 26 points 2 months ago

2 things:

  1. This seems to be a specific attack for their IM protocol if the entry node was compromised, and could be placed nearby the client. To make this much easier, you'd want to compromise both the entry and exit nodes (in this case exit node is TOR native, so it's more like internal node).

This has never been unknown, this is one of the fundamental attack vectors against TOR, the IM protocol seemed to make correlation easier due to its real time nature.

They added a protection layer called Vanguard, to ensure the internal exit nodes were fixed to reduce the likelihood that you could track a circuit with a small number of compromised internal exit nodes. This seems like it would help due to reducing likelihood of sampling.

  1. TOR has always been vulnerable, the issue is the resources needed are large, and specifically, the more competition for compromising nodes the more secure it is. Basically now the NSA is probably able to compromise most connections, and they wouldn't announce this and risk their intelligence advantage unless there was an extremely valuable reason. They definitely wouldn't do so because a drug dealer was trying to make a sale. Telling normal law enforcement basically ends their advantage, so they won't.

Other state actors might try, but they're not in the same league in terms of resources, IIRC there are a LOT of exit nodes in Virginia.

tl;dr - The protocol is mostly safe, it doesn't matter if people try to compromise it, the nature of TOR means multiple parties trying to compromise nodes make the network more secure as each faction hides a portion of data from the others, and only by sharing can the network be truly broken. Good luck with that.

[–] InvertedParallax@lemm.ee 1 points 2 months ago

Well, it can't run multithreaded jobs at full speed.

Exhibit A: The latest AMD patch for multicore scheduling across NUMA.

[–] InvertedParallax@lemm.ee 5 points 2 months ago (1 children)

improvements to quality of life;

Native Americans: "Beg your pardon?"

[–] InvertedParallax@lemm.ee 1 points 2 months ago (2 children)

Meh, not nearly as configurable as linux, some things you can't change.

NFS beats SMB into a cocked hat.

You start spending more time in a terminal on linux, because you're not dealing with your machine, you're always connecting to other machines with their resources to do things. Yeah a terminal on windows makes a difference, and I ran cygwin for a while, it's still not clean.

Installing software sucks, either having to download or the few stuff that goes through a store. Not that building from source is much better, but most stuff comes from distro repos now.

Once I got lxc containers though, actually once I tried freebsd I lost my windows tolerance. Being able to construct a new effective "OS" with a few keystrokes is incredible, install progarms there, even graphical ones, no trace on your main system. There's just no answer.

Also plasma is an awesome DE.

[–] InvertedParallax@lemm.ee 2 points 2 months ago

Let's be fair, Ms was vastly outrunning Intel for a long time, it's only slowed down recently, and now the problem isn't single-thread bloat so much as it is an absolute lack of multicore scaling for almost all applications except some games, and even then windows fights as hard as it possibly can to stop you, like amd just proved yet again.

[–] InvertedParallax@lemm.ee 1 points 2 months ago

Yes, mostly the applications aren't there, if you need real cpu power (or gpu for that matter), you're running linux or on the cloud.

But we are reaching a point where the desktop has to either be relegated to the level of embedded terminal (ie ugly tablet, before it's dropped altogether), or make the leap to genuine compute tool, and I fear we're going to see the former.

[–] InvertedParallax@lemm.ee 5 points 2 months ago (4 children)

Single-thread is really hard, we've basically saturated our l1 working set size, adding more doesn't help much. Trying to extend the vector length just makes physical design harder and that reduces clock speed. The predictors are pretty good, and Apple finally kicked everyone up the ass to increase OOO like they should have.

Also, software still kind of sucks. It's better than it was, but we need to improve it, the bloat is just barely being handled by silicon gains.

Flash was the epochal change, maybe we have some new form of hybrid storage but that doesn't seem likely right now, Apple might do it to cut costs while preserving performance, actually yeah I see them trying to have their cake and eat it too.

Otherwise I don't know, we need a better way to deal with GPUs, there's nothing else that can move the needle, except true heterogenous core clusters, but I haven't been able to sell that to anyone so far, they all think it's a great idea, that someone else should do.

[–] InvertedParallax@lemm.ee 4 points 2 months ago (4 children)

Even beyond that, short of something like blender, Windows just can't handle that kind of horsepower, it's not designed for it and the UI bogs down fairly fast.

Linux, otoh, I find can eat as much CPU as you throw at it, but often many graphics applications start bogging down the X server for me.

So I have a windows machine with the best GPU but passable cpu and a decent workstation gpu with insane cpu power on linux.

[–] InvertedParallax@lemm.ee 17 points 2 months ago (13 children)

I'm considering it, but only just, my 5800x is good enough for most gaming, which is GPU bound anyway, and I run a dual xeon rig for my workstation.

zen 2-4 took care of a lot of the demand, we all have 8-16 cores now, what else could they give us?

[–] InvertedParallax@lemm.ee 1 points 2 months ago

They probably moved it to somewhere under /usr or /var/lib.

[–] InvertedParallax@lemm.ee 4 points 2 months ago

They're working on HK.

Xi thought he had HK under control and could move directly on to Taiwan. His navy explained to him they were decades away from actually trying to invade.

view more: ‹ prev next ›