btrask

26 ms·

271.
by btrask 11y ago
It's on HTTPS, but it's also a Wiki that anyone can edit. This is the most recent change: https://help.ubuntu.com/community/VerifyIsoHowto?action=diff...
272.
by btrask 11y ago
Debian is already outstanding in this regard (and others)! One minor suggestion would be to provide ISO hashes over HTTPS. It's just as secure as using GPG with fingerprints sent over HTTPS, and it's a lot easier. The fingerprints
273.
by btrask 11y ago
Thanks! Fedora was one I didn't try (to install; I use it all the time). However there's still no way to use RPMFusion: http://rpmfusion.org/keys Maybe there's something I'm missing?
274.
by btrask 11y ago
I was trying to download Linux securely a month or so ago. It's actually embarrassingly difficult to do. The only two distros that did it right (that I could find) are Debian and Alpine Linux. The rest (including Mint and Ubuntu) had h
275.
by btrask 11y ago
32-bit hashes are not useful for content addressing pretty much at all. If you look at the table here: https://en.wikipedia.org/wiki/Birthday_problem#Probability_t... (50% chance of collision with only 77,000 resources
276.
by btrask 11y ago
I'm not sure I understand your criticism, but I should've clarified "content addressing using long, cryptographically secure hashes". Most of the major projects are using SHA-256.
277.
The “L” word – latency and digital audio systems (2003)(whirlwindusa.com)
4 points by btrask 11y ago|0 comments
278.
by btrask 11y ago
Lots of comments are asking what problem this solves. First, content addressing is the best general solution to exactly-once message delivery in a distributed system. Examples of distributed message protocols include (ahem) email, HTTP and
279.
by btrask 11y ago
Sure, directories can be used badly (and the Java and Ruby projects I've seen are often very difficult to navigate because so much is the structure of the language, rather than the structure of the project). But they can also be used w
280.
by btrask 11y ago
Ran into this recently. It's not open_memstream but same idea: https://github.com/NimbusKit/memorymapping
281.
by btrask 11y ago
I tried suggesting this directly on GitHub. Here was the response: > There's an old idea of unsafe fields that would come up for datatypes. It can be emulated with a Unsafe<T> wrapper that has unsafe methods to get references
282.
by btrask 11y ago
Perhaps a quick fix would be to allow variables themselves to be tagged as unsafe, so they could only be changed from unsafe blocks.
283.
by btrask 11y ago
I recently wrote a similar article ("C Programming Substance Guide")[1] which made the rounds here[2]. I've updated and improved it quite a bit since then too. It seems like we agree on the major points but it might be a good
284.
by btrask 11y ago
I wouldn't say it's the exact same problem, because at least the address gives you something to go on (you can verify whatever data against the hash to make sure it's correct and unaltered). But the problem of resolving has
285.
by btrask 11y ago
Adding layers of indirection isn't going to give us a permanent addressing system. This service just adds new points of failure: the service itself, or the creator of an identifier who fails to update it or changes it maliciously. The
286.
by btrask 11y ago
This isn't what I expected from the headline (i.e. notetaking software), and it's not something I could ever see myself using, but I really do like the design (and your answers here). The human-readable (Markdown) database format
287.
by btrask 11y ago
This sounds like a very practical lesson that more programmers should understand.
288.
by btrask 11y ago
The problem is UBSan is still kind of a pain to use. Just turn all of these optimizations directly into warnings and the problem would be solved--if you want to optimize them, the warnings will let you do it yourself.
289.
by btrask 11y ago
Those are all factors, but I think there's a deeper one: the same pressure to create a temporary solution also tends to keep it in place. On the other hand, when you are at your leisure to search for an ideal permanent solution, you pr
290.
by btrask 11y ago
Wow, I'll remember this the next time someone tells me memory allocations can't fail. Seems like a great design overall, but I'm not sure how I feel about the fixed 512MB limit. That's too high in almost all cases, and t
291.
by btrask 11y ago
And thus, the 10X programmer.
292.
by btrask 11y ago
You can't simply hash the whole page, because for most sites the hash will change constantly due to any varying content (e.g. rotating ads, new comments, random messages, A/B testing...). I wrote up a proposal for using a CSS rule
293.
How to solve the abstraction inversion and shrink the attack surface of browsers(bentrask.com)
1 points by btrask 11y ago|0 comments
294.
by btrask 11y ago
GitHub's fork management is lacking, but as it is now, forks are a symbol of popularity, so authors have no incentive to prune them. Plus it would be like saying "you're not a real contributor" to fans (which, while prob
295.
by btrask 11y ago
This is the total opposite of those futuristic meal pills, isn't it?
296.
Warning Signs in Experimental Design and Interpretation (2007)(norvig.com)
4 points by btrask 11y ago|0 comments
297.
by btrask 11y ago
While on a flight recently, I realized... Why doesn't Google sponsor free in-flight WiFi? It would be much easier than Google Fiber or Project Loon, and it would let them deliver more ads to a fairly wealthy group of people.
298.
by btrask 11y ago
Advocate something you do: cynical self-interest Advocate something you don't do: hypocrite
299.
List of secure websites(code.google.com)
23 points by btrask 11y ago|10 comments
300.
by btrask 11y ago
The ideas is to use it against outright squatters, not against other businesses that have the same name. You're right that it doesn't help with personal sites. The "Uniform Domain Name Dispute Resolution Policy"[1] seems

More ›