HNHacker News
TopNewBestAskShowJobs

hannob

16,731 karma · joined March 7, 2014

See https://hboeck.de/ and https://industrydecarbonization.com/
submissionscomments
hannob··on So you want to build a browser engine
Rust does not give you protection against speculative execution attacks. Entirely different beast than memory safety errors.
hannob··on Sam Altman-backed nuclear startup signs major data center contract
So your solution is to power these datacenters for another 1-2 decades with coal power while you wait for new nuclear plants? Because that's the realistic timeframe for any new nuclear. Vogtle 3 took 14 years to build.

Of course, any "advanced nuclear" that doesn't even have a prototype yet will take longer than that. If it will ever happen.

hannob··on Sam Altman-backed nuclear startup signs major data center contract
Gosh am I annoyed by these bullshit energy startups.

They want to sell a PPA? For a technology for which they don't even have a working prototype? That has never produced a single kwh of energy? That's like... step 200 before step 0.5.

hannob··on Microsoft PlayReady – Complete Client Identity Compromise
DRM schemes never worked, and it has been speculated that the people building them always knew it, but had other goals.

Backn in the days it was: Of course you can break DVD copyprotection schemes. But you cannot build a legal opensource DVD player software. Today it's: Of course every Netflix series can be found on the pirate bay. But you're not legally allowed to build an alternative netflix player frontend.

hannob··on Microsoft employees spent years fighting the tech giant's oil ties
Do you know that comic? https://thenib.com/mister-gotcha/ That's you.
hannob··on As solar capacity grows, some of America's most productive farmland is at risk
If you're worried about energy, land use, and competition with farmland for food, there's one thing you should worry about: bioenergy. If you worry about solar energy and land use, you haven't looked at the numbers.
hannob··on Quantum Algorithms for Lattice Problems
QKD does not solve the problem that quantum computers create, and cannot replace public key cryptography. That's a common misconception that the marketing departments of QKD research tries to keep alive.

Even under ideal conditions (whether these can exist is debatable), the best QKD gives you is a securely encrypted channel only when you already have a securely authenticated channel. The latter is extremely important, makes the whole thing mostly useless, and is often omitted by QKD advocates.

hannob··on Kobold letters: HTML emails are a risk
When efail came out, I wrote a blogpost about the security risks of HTML mail.

It is really amazing how problematic all of this is, despite its widespread use. The HTML mail spec is really old, and contains almost no security considerations.

HTML in emails can only be a subset of HTML to be secure. But nobody has ever defined what exactly that subset is, so everyone does whatever they think. And unsurprisingly, this leads to an endless stream of security flaws.

See: https://blog.hboeck.de/archives/894-Efail-HTML-Mails-have-no...

hannob··on A deep dive into email deliverability in 2024
This is something I'm still trying to find someone who understands it in detail and can explain it to me.

Because as you say, you break SPF if you don't touch the envelope from. There's SRS to fix this. But if you do that, you break DMARC alignment.

So... something is always broken? It appears to me there's no way to make mail forwarding that works with full SPF/DKIM/DMARC setups.

hannob··on Expat is understaffed and without funding
Also check the corresponding blogpost: https://blog.hartwork.org/posts/expat-2-6-2-released/
hannob··on Germany's solar panel industry, once a leader, is getting squeezed
> If there is less energy, someone will have to use less energy. As far as I can tell that means either compromising living standards or giving up some heavy manufacturing.

That's total nonsense, I guess you never heard the word "energy efficiency".

hannob··on When 'open core' projects reject contributions for competing with the EE
Without putting blame on anyone, this does show a fundamental issue with the open core model. It is built on the premise that your "open" product will not be as good as possible, so you can still have the higher priced "enterprise" product.

I think it's fair to point that out. Usually, you expect that developers want to create software that is "as good as possible". They may have a different idea what exactly "good" means, but you usually don't expect that an open source project will actively want to be worse than it could be. But "open core" is exactly that: It's a software trying to be worse than it could be.

hannob··on Ice-free summers in Arctic possible within next decade, scientists say
> Especially on climate, it's known for alarmist articles. Search their site for other headlines on an ice-free arctic and I bet you'll find similar doom predictions going back a long time with dates that are now in the past.

> A random example I found: https://www.theguardian.com/environment/2009/mar/12/global-w...

Now if anyone gets a wrong impression here: I checked the linked article. It does not talk about an ice-free arctic. It doesn't even mention the word "arctic". It also does not make any predictions for a date that is now in the past.

It essentially explains that extreme temperature increases would make parts of the world uninhabitable due to the wet bulb temperature. Which is, well, not particularly controversial, as it is a fact that can be derived from very basic physics, and was as true in 2009 as it is today.

hannob··on Use KeePassXC to sign your Git commits
In Gentoo, I believe we already reject pushing unsigned commits.
hannob··on Ask HN: Did you encounter any leap year bugs today?
I know I'm late to the party, but I have a Python script that creates a security.txt for one of my own project, and it sets the "Expires" date to one year in the future.

Old code:

expires = datetime.datetime.now(tz)

expires = expires.replace(year=expires.year + 1)

It broke yesterday, throws an exception ("ValueError: day is out of range for month"). It's kinda obvious that it does.

Fixed version code:

expires = datetime.datetime.now(tz) + datetime.timedelta(days=365)

expires = expires.isoformat(timespec="seconds")

Now we're just going 365 days into the future. Of course, this has a slightly different meaning and outcome, we are not always ending up on the "same date next year". But in this use case it doesn't really matter.

hannob··on iMessage with PQ3 Cryptographic Protocol
I know that thinking, but learning more about RSA, I came to realize that there's a flipside of this.

People think "RSA is easy", because someone gave them a lecture of a simplified/wrong/insecure version of RSA. Pretty much all "simple introductions to RSA" you can find out there are wrong.

The truth is: RSA isn't that simple. If you want to have RSA, and want to have it secure, there's a whole bunch of things to consider. But RSA looks simple.

So lots of people go ahead and implement their RSA. And then you end up with, hey, I can break almost a third of the top 100 webpage's RSA implementations. (I'm not kidding, I did that -> https://robotattack.org/ .)

I think the fact that crystals-kyber is obviously not that simple may actually protect us. Because hopefully most peopple will end up using some hopefully well audited optimized free implementation, because they won't even have the idea that they could do this on their own.

hannob··on The Ute Tribe will construct one of the largest solar farms in the US
> A lot of bitcoin miners use stranded power, which would otherwise go to waste.

Often claimed, rarely supported by evidence or numbers.

It's also unlikely to be very practical, because that'd essentially mean running bitcoin miners in load-balancing mode, and not running them most of the time. Given that bitcoin hardware tends to loose value quickly, as the next generation of mining hardware comes to the market, this is unlikely to be a feasible model.

hannob··on The Matrix Trashfire
I feel the "clickbait" accusation has a tendency to be overused.

I mean, when I hear "clickbait", I think "the headline makes me think there's something interesting that isn't really backed up by the content". But here? The headline says "Matrix Trashfire", the content delivers exactly that.

hannob··on New Linux glibc flaw lets attackers get root on major distros
I mean, I don't disagree, but it probably would not have helped in this case.

This is based on a buffer overflow in glibc itself. It is my understanding that rust still calls into libc for many lowlevel system functions. And if you call C code from rust, well, it's still C code with C code bugs.

Ultimately, if you want to get rid of those, you'd have to rewrite the libc in Rust.

hannob··on The Retro Web – Database, Docs, BIOS, Drivers, etc. for old PC Hardware
Hard to tell exactly, both because of course it was a process (still running DOS some time while having Windows as a GUI for other uses), and I don't remember everything exactly.

I think the later Running-on-top-of-DOS-Windows-versions - the last one was Windows ME I believe - where trying to hide their DOS-based roots, and you had to use some hacks to actually boot into DOS. I can tell you that I used those hacks.

I never migrated to the "native" (non-DOS-based) Windows versions (I believe XP was the first consumer-not-dos-based version), but switched to Linux around that time.

hannob··on The Retro Web – Database, Docs, BIOS, Drivers, etc. for old PC Hardware
Oh this brings some memories.

I was one of the people who still ran DOS when this wasn't really very common any more, and was constantly looking for things like drivers that would bring proper vesa or sound support to newer hardware on DOS. I ended up starting a webpage dedicated to collecting those drivers for DOS, which by now must've been decades ago.

It never grew very big, but I also never took it down. I wonder if it helped some people over the years.

https://dosdriver.de/

hannob··on Proposed top-level domain string for private use: ".internal"
Counterpoint: .internal is much easier to understrand, .intra sounds like a reference to "intranet" as opposed to "internet". That's terminology networking people would use, but .internal is likely something both non-tech and tech people would intuitively understand.
hannob··on The FCC Is Taking Steps to Wind Down the Affordable Connectivity Program
It's hard to see a case to be made to block IPs with a "bad reputation" from accessing sites that are essentially text documents.

I can see that blocking IP ranges is part of a strategy to protect service signups, logins, or contact forms. But a gov agency publishing a piece of text? What's the risk that is mitigated by blocking IPs here?

hannob··on Forging signed commits on GitHub
Sorry, if that's your security process, it's broken. If you're microsoft and that's your security process, you have no excuse and should be embarrassed. However, I heard such stories about Microsoft's security process plenty of times before, so I guess that's what it is.
hannob··on Forging signed commits on GitHub
It's wild that we're in 2024, and there's a security issue that is essentially "we parse data in an ad-hoc format with an ad-hoc parser based on regexps, and we got that wrong". And the solution is "we tweaked the regexp", and not "we properly specified/documented the format (or replaced it with something properly specified), and wrote a parser that correctly implements the specification".
hannob··on Backing up the power grid with green methanol
The key argument of the paper this is based on is that storing H2 is difficult if you don't have salt caverns. Then you need H2 pressure tanks, and that is expensive and also requires a lot of energy. And you don't have salt caverns everywhere.

The authors compare this in an energy model, and come to the conclusion that methanol comes out on top if you don't have cheap (aka salt cavern) h2 storage. But of course, there are a lot of assumptions going into this.

Nice bonus: It's an open source model, so others can test it with different assumptions.

hannob··on Backing up the power grid with green methanol
FWIW, I had also written about this paper: https://industrydecarbonization.com/news/should-we-burn-meth...
hannob··on Future gigantic solar farms might impact solar power elsewhere in the world
Entirely reasonable to research it.

Not reasonable to write an article that sounds like this is an actual problem, only to tell people in the third last paragraph that it is largely a hypothetical scenario and in all likelyhood not going to matter for any real-world scenario.

hannob··on Python3 is removing crypt.crypt and not replacing it with anything
But it does not have a function to use libc-style password hashes, so that doesn't help.
hannob··on Python3 is removing crypt.crypt and not replacing it with anything
The PEP is not accurate, probably outdated.

Linux distros are converging towards using libxcrypt with yescrypt, which is a modern password hashing function. If you have a crypt function that wires back to libxcrypt's crypt, you can use that.

It's a bit unfortunate that people seem to be unable to agree on a modern password hash (other places tend to use scrypt or argon2), but well, I think yescrypt is fine, and having a way to generate and verify crypt-compatible hashes is certainly useful functionality.

← PreviousPage 5 of 34Next →