Size and weight
It's just a description. It's like if we said it had some heft to it.
C.
3533 publicly visible posts • joined 21 Sep 2011
...in which the people who did the survey chose not to make a distinction between Angular and AngularJS.
C.
Hey thanks for the feedback. We've taken your points onboard, with a few tweaks to the piece and also for food for thought in future.
The thrust of our argument was that more and more traffic is going into the hands of a smaller number of network owners, which isn't great for resilience, for one thing.
Also, if we end up in a situation where 90%+ of traffic ends up in Google, Cloudflare, Amazon, Microsoft, Akamai, etc, pipes, what happens with standards? Might be a bit less IETF and a lot more GAMCA. Maybe we're worrying about nothing, maybe it's worth putting it out there. We went with the latter.
Also, re: CDNs. Sure, you don't have to use one or you could build your own. Much like if you don't like using DHL or FedEx, you could ship something literally yourself. Or if you don't want to fly BA or AA, you could get your own plane, pilot's license, and fly. There comes a point where you need a site-protection service that's cost prohibitive for you to build.
You mentioned other anti-competitive stuff, which is valid, but beyond the intended scope of this article.
It's a comment piece on this particular part of the industry.
C.
Yeah, the i was for internet, among other things, if you follow the history.
C.
I could lie here in an attempt to make you all return on Friday
But no, we brought BOFH forward for those who want to do other things in an Easter break other than check out IT news and the internet
But hey you're welcome to drop by tomorrow anyway, half of us will still be working ;-)
C.
Two things. One, the IRS demands you report ill-gotten gains as income. The IRS doesn't care if you robbed a bank - that's another agency's problem - it wants that income tax from your heist. If you ripped off Apple and you under-declare your income, you'll have the IRS to answer for. So - if the allegations are true - he may have tried to declare some of the scam money as income to avoid the IRS poking around.
Second thing, examples of Apple pay are on levels.fyi FYI.
C.
130nm is OK for low-volume simple devices and microcontrollers. Academic studies, first-time tape-outs, one-off silicon, weird mixed-signal stuff, etc. No one expects it to be advanced. Depending on how much money you have, the 130nm is virtually free (or free if qualifying with Google), so you get what you pay for.
Skywater does 90-350nm (and seems to be trying out 65nm) and if you need something else, like 65nm and below, there are other foundries.
BTW one of the reasons why you want a high transistor count (and therefore a dense node) is to fit a decent amount of cache on the die. If you don't need a lot of cache, and you're not doing an SoC with a lot of complex things on it, well, why do you need a small node?
But hey, don't let me stop you. If you want something super dense, knock yourself out. Just cough up the six or seven figures rather than ten large.
For instance, take SiFive: their first chips were in the 16-14nm range, and it's had hundreds of millions of dollars in funding, and sales on top of that.
C.
There are some others. Eg,
MOSIS – this takes the same multiple-designs-per-wafer approach and works with TSMC, Intel, and GF. These have been around for ages.
Europractice is another broker for access to foundries
IC Alps often pops up
Minimal Fab Nederland is gauging interest
There is a choice. If there's an interest in low-volume chip making, we'll explore the area more and speak to others. I dream of having the time and budget to design and make a simple vulture chip for an article series.
C.
As an aside, Cafepress's quarterly revenue was $15m in 2018, on which it made a $1.5m loss. That year it was acquired and taken private by Snapfish for $25m, got hacked in 2019, and was sold to PlanetArt in 2020.
Those are the final financial figures we have for it.
C.
Well yeah, that's why we used the words "ended up," as in: one way or another, they put performance before security.
It could have been intentional, it could have been accidental. I've heard anecdotally in the Valley that some CPU designers had an inkling that speculative execution left a trace in the cache that could be used to leak data but thought it was either theoretical or not worth worrying about.
C.
It's just an interesting way to get threads on GPU cores to talk direct to NVMe SSDs to get the data they need in a fine-grained, software-cached manner that specifically suits the access patterns of GPU-bound applications.
Yeah it involves DMA and all that. It's not claiming to have reinvented or come up with DMA; it's an application of it specific to GPU workloads.
C.
The 'X hours' string is generated using client-side JavaScript running in your browser.
The webpage contains the exact time and date, and the code on the page converts that into 'X hours ago' based on the local time of your device. So the time on your device was out.
To me, it says your comment was posted an hour ago.
C.
FWIW your now-deleted previous post made what looked like a baseless accusation of criminal activity so a moderator removed it.
Also FWIW Cloudflare's pretty open about the position it takes: it doesn't want to decide what's right or wrong on the internet. It doesn't want to be the arbiter of what is allowed to be hosted. Eg:
Cloudflare: We dumped Daily Stormer not because they're Nazis but because they said we love Nazis
Cloudflare speaks out amid allegations it safeguards banned terror gangs' websites
If you report spam or malware-based abuse to Cloudflare, feel free to CC us in (news@theregister.com) and we'll take a look at the same time.
C.
No, they're not supposed to contain arbitrary code.
What happens is, with these kinds of bugs, is that there is a payload of instructions carefully placed within the multimedia file that is otherwise just data. When the file is parsed, the vulnerability in the parser is exploited to allow the payload to eventually execute.
There are steps in between to get around the OS's security defenses.
C.
"How big would the article be for a Windows vuln that let any fucker get admin privileges?"
For a Windows vuln for which patches are already out? Typically a few sentences: there are EoP holes in every Windows Patch Tuesday.
If we write a whole article about an EoP it's usually because a patch isn't out yet (it's a zero day) or it's being actively exploited or that the bug is particularly interesting, or that someone on the team was at a loose end and had enough time and material to write a whole article.
"C'mon El reg, there was a time when you weren't afraid to put the boot into ANY OS, even Linux. Are you really that frightened of a load of pissy comments?"
No. We often assign stories based on how much time and scribes we've got available. For Dirty Pipe, we wanted to get it out as soon as possible as the next lead item on the weekly roundup.
In fact think of it as a Dirty Pipe story with bonus material, as the DP section is quite a lot more than a couple of paragraphs.
We'll look at the Android angle next (it's also mentioned in the article).
Good news is that we've hired two writers this month to cover security, so expect more security stories sooner rather than later.
"Step the fuck up."
Sigh, why this angry?
C.
If you overwrite an entry in /etc/password so that the password field is blank, no password is needed. (If there's an x, use the shadow file.)
So, just blank out root's password entry with the DirtyPipe overwrite and everyone can get root.
PS: Another example would be to pick a root-owned setuid binary and overwrite it so that it simply spawns a root shell, and then restore the binary to normal.
C.
I guess the point of this is that - a la SolarWinds - you modify some popular software in a supply chain attack, and the code is deployed all over the world.
In order to target specific labs, you get them to process a sample with an IP address and port in it so you know which lab you're breaking into.
It's very theoretical, we thought it was interesting, and we think readers will understand the threat. We'll keep the feedback in mind for future.
C.