748 karma · joined November 2, 2014
IMHO, the danger of a PKGBUILD itself doing something nasty is small--it would be limited to things like recording `uname -a`, listing all your installed packages: the things mentioned in the article.
The real danger is that the PKGBUILD is installing some software, which you will later run with full user privileges. If you don't notice that the Git repo listed in the PKGBUILD file is wrong, you won't notice that you're actually installing a backdoored version of the package.
Of course, if you're ultimately going to run the program, the binary set up by the PKGBUILD has a lot of control. But the PKGBUILD itself is limited in what it can do (to things like listing your installed packages, getting `uname -a`--the stuff mentioned in the article).
Of course, it would be more interesting if we could scan or survey the AUR to get a percentage of suspicious packages. I've long been under the impression that some popular AUR packages (e.g. Google Chrome) are pretty safe from tampering. For anything else, I glance over the PKGBUILD to make sure it's not doing anything obviously fishy, and I've never noticed anything.
The only downsides were that I had a Mexican phone number (I use Google Voice anyway, so just needed the data) and, more importantly, that all the customer support was in Spanish...
I ended up ditching the SIM after about a year when the data stopped working when I bought a new tariff. Not sure how much this was due to my inability to navigate the Spanish customer interface vs. ATT cracking down on people doing exactly this.
Crossing my fingers they added jokes about Stallman and muh freedums.
There are separate debug queues for smaller development and test jobs that prioritize latency over throughput, and this is a main source of inefficiency (but, as someone who develops on supercomputers, trust me, it's necessary to make them usable).
As for the efficiency of the codes--there are a lot of barnacle-encrusted Fortran codes in astrophysics, chemistry, and elsewhere. Some of them probably contain plenty of inefficiency, but the cost of re-writing them is high. Oftentimes either the people writing the codes aren't interested in maintaining good software quality (because they're focused on the science) or the incentives aren't aligned to re-write code that's already established, but from the 80s (re-writing old code is generally not how one gets a Ph.D.). But they do very important things, like simulate nuclear fusion or the interaction of chemicals in the atmosphere that create weather patterns and storms, so it's very important to run them.
I thought Ghost in the Shell was in Japan.
Added ten bucks of credit to my Google account, then feverishly dialed the number... "You are about to be connected to a random French." Ooh, how charming. Upbeat hold music, then silence. "Hello?" I call out. Then, my call is dropped. DISAPPOINT.
North Korea's intranet has its own DNS system, and they also (contrary to the article) assign a bunch of IP blocks not in RFC 4192 internally.
People who do have access to the outside Internet do so through an HTTP or SOCKS proxy with login credentials.