Hacker Newsnew | past | comments | ask | show | jobs | submit | oskarkk's commentslogin

It's usually kerosene + O2, not H2O2. But H2 + O2 is another classic liquid rocket fuel that has higher specific energy (energy per mass), but lower energy density (energy per volume) than kerosene, and is used mostly as a 2nd stage fuel (where mass is most important). Its lower density and the need to keep it very cool mean heavier tanks, and it's also hard to work with due to being such a small molecule that likes to leak, which causes development costs to be higher.


Is a data center satellite really that different from a communications satellite? Starlink sats must have some significant processing power and nontrivial control system, and they work without physical maintenance. One data center sat is like one server rack, if it fails, it's fully lost and you just deorbit it, as it's done with Starlink sats. They sent 12443 Starlink sats to space, deorbited 1684. The thing that matters is failure rate, and the economics resulting from that. And also the cost of specialized resilient hardware.


Communications satellites don't have nearly as much long-term rewritable storage needed.


Taking a 10% stake in a company is far from nationalization. And the big increase in Intel's stock price happened months after that.


It is literally partially nationalising though, isn’t it?

This is how the UK government got the banks through the 2008 financial crisis.


They bought the shares on the open market. They didn't seize the company at gunpoint.


No they didn’t. After Trump started making noise about their CEO, Lip-bu Tan, being Chinese they then took the shares at a “…discount to the current market price.”[1]

And the money for this _deal_ was primarily from the CHIPS act funds they were already awarded but had not been sent to them yet

> Of the total, $5.7 billion of the government funds will come from grants under the CHIPS Act that had been awarded but not paid, and $3.2 billion will come from separate government awards under a program to make secure chips.[1]

This was at gunpoint from the government’s monopoly on violence.

[1] https://www.cnbc.com/2025/08/22/intel-goverment-equity-stake...


???

The government had passed a law appropriating funds to subsidize semiconductor manufacturing in the US and spent some of it buying intel stock. How is that the government seizing Intel at gunpoint? I mean aside from the libertarian argument that the taxation necessary to raise those funds is theft?


Did you miss the part where it was already awarded to them, but the Trump admin then made it conditional?


Why would you think nationalising is a violent process?

As soon as the nation owns enough stock to profit from government decisions (and to compound the influence of those decisions) you essentially have a partially nationalised business.

10% of OpenAI might easily be enough to reach a meaningful "partially nationalised" threshold, once you factor in any holdings in federal pension plans and the active level of government policymaking.

It is very clear Sam Altman wants this, too, because this whole "take 10%" thing in Trump's mind was his idea back in early 2025, and OpenAI have been following up on it recently.

They want the US government to be the bag holder.


So if USgov bought 51% at market value you’d be ok with that?

Time to fire up the printers I guess.


Taking any % is partially nationalizing it and there was no negative capital flight. And 10% is a pretty significant portion.


You're commenting under an article about politics, not about diabetes research.


NASA mostly runs on SpaceX, so it depends if you consider ISS to be critical. But I wouldn't say it would be mind boggling.


Cool, nationalise SpaceX, reintegrate its costs into NASA, done.

The US would never let its access to space be cut off.


The US actually did just that when it retired the shuttle program. We had to rely on Russia to get to the space station.


Watch lmao.


> a technology that already deeply struggles to find customers

As far as I know it's the opposite, Anthropic struggles to satisfy demand, they have tons of paying customers and their customer base is growing fast.


Wow as far as you know? That settles it then! Just ignore this:

https://www.flyingpenguin.com/wheres-ed-anthropic-told-court...


So, your link shows that they probably have like $1 billion in sales per month (but they publicly overstated this by 30%), and that's the struggle to find customers?

There are tons of posts and reporting about Anthropic's problems with meeting demand, usage limits (on paid plans, especially during peak hours), fast growth (your link confirms that), and problems with infrastructure.

Some links:

https://uk.finance.yahoo.com/news/anthropic-throttles-claude...

https://techcrunch.com/2026/03/28/anthropics-claude-populari...


So the takeaway here is that they scaled to just over $5bn instead of $6.6bn in revenue in just a few years…? Still sounds like plenty demand exists?


Starship V2 heat shield was good enough to allow the ship to perform a landing on the ocean in one piece, in a precise spot. But a safe landing is not enough, the ship needs to be in a good enough condition to be flown again, with low refurbishment costs. We still don't know what condition Starship is in after landing (they need to actually land it on land first). I wouldn't say the heat shield is failing, it didn't cause any failure of the ship, it protected it successfully to the sea level.

But the heat shield is just not mentioned in this article. They actually made significant changes to it in the new version. They added added new seals between the tiles, improved attachment points, and redesigned the shielding in specific areas.

A big problem with their work on the heat shield is that they lost the ship before reentry multiple times for various reasons. They were making changes to the heat shield on previous versions, but couldn't test them as they were repeatedly losing the ship before the heat shield was actually used.

Also, from their description of the planned launch of Starship V3:

> The Starship upper stage will target multiple in-space and reentry objectives, including the deployment of 22 Starlink simulators, similar in size to next-generation Starlink satellites. The last two satellites deployed will scan Starship’s heat shield and transmit imagery down to operators to test methods of analyzing Starship’s heat shield readiness for return to launch site on future missions. Several tiles on Starship have been painted white to simulate missing tiles and serve as imaging targets in the test.

> For Starship entry, a single heat shield tile has been intentionally removed to measure the aerodynamic load differences on adjacent tiles when there is a tile missing.

https://www.spacex.com/launches/starship-flight-12

So they're still working on the heat shield. Things like space data centers may be economical only if Starship is fully reusable, otherwise the idea is dead on arrival.


14.3 seems to come from some Red Hat-specific GCC version, which can be reported as "gcc (GCC) 14.3.1 20250617 (Red Hat 14.3.1-2)". See these random examples I found by googling:

https://github.com/anthropics/claude-code/issues/40741 (gcc version "Red Hat 14.3" included in system version at the bottom)

https://docs.oracle.com/en/database/oracle/tuxedo/22/otxig/s...


Strange that it's not classified as "high", which specifically includes "local root privilege escalations".

> High: A significant problem, typically exploitable for nearly all users in a default installation of Ubuntu. Includes serious remote denial of service, local root privilege escalations, local data theft, and data loss.


It is high now, someone at canonical is paying attention it seems


In TFA: https://copy.fail/#mitigation

> Before you can patch: disable the algif_aead module.

> echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf

> rmmod algif_aead 2>/dev/null || true

Edit: and I can confirm that on my system with kernel 6.19.8 the above fixes the exploit.


Weirdly, the mitigation does not seem to work under WSL2 (at least in Ubuntu 24.04).

    Linux wsl2 6.6.87.2-microsoft-standard-WSL2 ...
`modprobe algif_aead` errors out, but if I run the POC, it succeeds.

Outside of WSL2, the mitigation does appear to work though.


It's possible that the WSL kernel has that code compiled-in rather than as a loadable module. If they ship the kernel config somewhere, you could verify with

  zgrep CRYPTO_USER_API_AEAD /proc/config.gz /boot/config-*
It should show =m if it's a loadable module, and =y if it's compiled in.


It's a loadable module:

    CONFIG_CRYPTO_USER_API_AEAD=m
Using bpftrace to watch calls to module_request, openat, etc., it looks like when the kernel calls modprobe, it doesn't even look at the disable-algif.conf file:

    [module_request] pid=3648 comm=python name=algif-aead
    [umh_setup] pid=3648 comm=python path=/sbin/modprobe argv0=/sbin/modprobe argv1=-q argv2=-- argv3=algif-aead argv4=
    [openat] pid=3688 file=/etc/ld.so.cache
    [openat] pid=3688 file=/lib/liblzma.so.5
    [openat] pid=3688 file=/lib/libz.so.1
    [openat] pid=3688 file=/lib/libgcc_s.so.1
    [openat] pid=3688 file=/lib/libc.so.6
    [openat] pid=3688 file=/etc/modprobe.d
    [openat] pid=3688 file=/lib/modprobe.d
    [openat] pid=3688 file=/lib/modprobe.d/dist-blacklist.conf
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.softdep
    [openat] pid=3688 file=/lib/modprobe.d/systemd.conf
    [openat] pid=3688 file=/etc/modprobe.d/usb.conf
    [openat] pid=3688 file=/proc/cmdline
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.dep.bin
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.alias.bin..
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.symbols.b..
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.builtin.a..
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.builtin.b..
    [openat] pid=3688 file=/sys/module/algif_aead/initstate
    [openat] pid=3688 file=/sys/module/af_alg/initstate
    [openat] pid=3688 file=/sys/module/algif_aead/initstate
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/kernel/crypto/alg..
    [finit_module] pid=3688 comm=modprobe fd=0 flags=0
    [module_load] pid=3688 comm=modprobe name=algif_aead
Restart WSL2, run the bpftrace, and try `sudo modprobe algif-aead`, and that shows it looking at (or I guess opening) other files in /etc/modprobe.d, including the new one.

The mystery is why.


In wsl, each distro you have runs in a container (with lot of permissions), you'd need to apply the modprobe change inside wsl "hypervisor" rootfs


The only way to solve this issue in WSL is to rebuild your kernel:

~ uname -r

6.18.20.3-microsoft-standard-WSL2+


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: