BenTheElder

Joined 12 years ago

Karma
242
Submissions
94
Member since
Nov 21
https://elder.dev
View on Hacker News

Recent submissions

Comment · 3 years ago
> Unfortunately, if you've used Google Takeout or other systems that can both downsample your photos and videos, as well as actually deleting _or changing_ metadata, deduplicating becomes a big wad of heuristics.

I thought takeout exported the original files? (alongside metadata entered into the application)

Comment · 5 years ago
Thanks!
Comment · 5 years ago
> Uber built a remote kill switch for their tax docs in canada, this isn't unprecedented for them.

Do you have a pointer to more on this? Naive searching doesn't seem to turn up anything for me.

Comment · 5 years ago
Comment · 5 years ago
Ok but the premise of physical harm in person comes from the parent comment, not mine:

"Most of those dependencies represents at least one human being who can be threatened with a crowbar and forced to ship an exploit, which can then infect vast numbers of production applications."

Comment · 5 years ago
Good points.

I suspect for a lot of projects reproducible builds are themselves a bit of a hurdle and not being verified in the rarer case that they already exist, but the point of reproducible + signed builds as indirect source-signing stands.

Comment · 5 years ago
Those are interesting points / possible approaches, however is there any indication that this particular project enables any of that?

This seems focused on signing binaries / build artifacts.

IMHO it seems like if you have the threat model of "crowbared maintainer forced to insert backdoor" you probably don't trust sources let alone binaries and need to vet your dependency sources and then compile your own binaries from them.

Many open source dependencies will not have a jurisdictionally diverse review team, or any review team at all (single maintainer).

Comment · 5 years ago
Why can't they be "threatened with a crowbar" to sign the exploit?
Comment · 5 years ago
Comment · 5 years ago
Comment · 5 years ago
Comment · 5 years ago
Is what appears to be less than 2,000 lines including detailed comments etc. "quite a lot"?

This seems like a manageable amount to very carefully maintain and not at all like writing something entirely in C.

Comment · 5 years ago
this seems like a pretty trivial amount of C, by comparison, and a pretty solved problem now.
Comment · 5 years ago
FWIW Google did this ("letting go" of an asset) with Kubernetes / the CNCF.

I work on this at Google, but Google no longer owns this since 2015.

Comment · 5 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton