kbolino

29 ms·

451.
by kbolino 2y ago
Logical Block Addressing (LBA) by its very nature provides no hard guarantees about where the blocks are located. However, the convention that both sides (file systems and drive controllers) recognize is that runs of consecutive LBAs gener
452.
by kbolino 2y ago
Do you think the problem that is addressed by offheap could also have been addressed with a generational garbage collector?
453.
by kbolino 2y ago
This means it's not GNU/Linux, but that's not the only flavor of Linux. Alpine uses busybox and musl instead of GNU userland and glibc, but few would say it's not a Linux distribution.
454.
by kbolino 2y ago
It took me awhile to dig up evidence for this, but the closest I can find is that subordinate CA certificates will no longer be allowed to have id-kp-clientAuth EKU [1], however this restriction does not apply to leaf certificates. [1]:
455.
by kbolino 2y ago
This is partly why SSDs just lie nowadays and tell you they only have 75-90% of the capacity that is actually built into them. You can't directly access that excess capacity but the drive controller can when it needs to (primarily to e
456.
by kbolino 2y ago
The biggest limitation of Go's static type system vs. Python's type hints system that I can think of would be the lack of union types, with nullability a close second (and it's just a specialized application of union types in
457.
by kbolino 2y ago
I think preventing alarm fatigue is a very good reason to fix issues. But 5% free is very low. You may want to use every single byte you feel you paid for, but allocation algorithms really break down when free space gets so low. Remember th
458.
by kbolino 2y ago
There are some alternatives. Certificate pinning is probably the most widely known way to get a certificate out there without relying on live PKI. However, certificate pinning just shifts the burden of trust from runtime to install time, an
459.
by kbolino 2y ago
That was a bit tongue-in-cheek, sorry. I've worked in mTLS shops and it's definitely not practical for the public Internet. Ultimately, I think the practical solution to homoglyphs is in the presentation layer, whether it be disp
460.
by kbolino 2y ago
I see it useful as part a layered strategy: X.509 certificates establish the authenticity of the server for that domain, while the SRP/PAKE would establish the authenticity of the legal entity you're actually trying to reach. In t
461.
by kbolino 2y ago
The security situation with SSH is actually kind of dismal. You're right that standard SSH server configurations are generally equivalent to self-signed certificates but the trust model often used there is known as TOFU ("trust on
462.
by kbolino 2y ago
It does not have to be perfect to be better. It's not great that 13% of revoked certificates would still be there (and get trusted by CRL-ignoring clients) but significantly smaller CRL files may get us closer to more widespread CRL ch
463.
by kbolino 2y ago
I just downloaded one of DigiCert's CRLs and it was half a megabyte. There are probably thousands of revoked certificates in there. If you're not checking CRLs, and a lot of non-browser clients (think programming languages, softwa
464.
by kbolino 2y ago
If there was no IP/DNS ownership verification, how would you even know you had been MITMed? You think the attacker is going to set a flag to let you know the certificate is fake? The only real alternative to checking who signed a certi
465.
by kbolino 2y ago
Also anecdotal, but it seems that RadioShack in that era was a particularly awful place to work. I applied around that time (might have been that exact year, or else it was 07-08). I was weeded out by the online personality test. My dad was
466.
by kbolino 2y ago
This is misleading at best. The JVM only exposes multibyte values to ordinary applications in such a way that byte order doesn't matter. You can't break out a pointer and step through the bytes of a long field to see what order it
467.
by kbolino 2y ago
I think there's two layers to the typed vs. untyped nil issue (which is really about nil pointers in an interface value vs. the zero value of interface types). The first is simple confusion, such as trying to handle "all nils&quot
468.
by kbolino 2y ago
I don't think the state of the art ca. 2007 was the same as it seems today. For one thing, Go took a number of forward-thinking stances (or ones which were, at least, somewhat unusual for its time and target audience), like UTF-8 strin
469.
by kbolino 2y ago
I would actually say even in 2012 the observation was probably wrong already, but notably Pike actually made it in the mid-aughts and was simply relaying it in 2012. However, being wrong about what was good for the future of C++ isn't
470.
by kbolino 2y ago
I think both C and Go (the former is relevant due to Thompson's involvement in both and the massive influence it had on Go) are very "practical" languages, with strict goals in mind, and which delivered on those goals very we
471.
by kbolino 2y ago
Rob Pike is not a PL theoretician, but that doesn't make him not an expert in creating programming languages. Go was the third language he played a major part in creating (predecessors are Newsqueak and Limbo), and his pedigree before
472.
by kbolino 2y ago
I too like it, in fact I find myself missing it in other languages. I will say that anonymous interfaces are kind of rare in Go, and more generally interfaces in my experience as used in real codebases seem to lean more on the side of being
473.
by kbolino 2y ago
Nil is IMO far and away Go's biggest wart, especially today with a lot of the early language's other warts filed off. And there's really no easy way to fix this one. I think this article on channels suffers from "Seinfel
474.
by kbolino 2y ago
Go's designers were experts. They had extensive experience building programming languages and operating systems. But they were working in a bit of a vacuum. Not only were they mostly addressing the internal needs of Google, which i
475.
by kbolino 2y ago
Farmers don't work in perfect isolation and do have to interact with other economic sectors that keep to clock hours. However, I don't think the misalignment between civil time and solar time has ever been so severe (nor would it
476.
by kbolino 2y ago
The Sony-Toshiba-IBM alliance had much grander plans for the Cell architecture, which ultimately came to naught. The PS3 wasn't just a console, it was supposed to be a revolution in computing. As a console, it did alright (though it&#x
477.
by kbolino 2y ago
It's probably both. Browsers now have built-in DoH so they usually do their own resolving. Only if you disable "secure DNS" (or you use group policies) will you fall back to the system resolver anymore.
478.
by kbolino 2y ago
Notably, assuming conformance to this standard, a browser might still not treat localhost domains as trustworthy if it has reason to believe they can be resolved remotely. However, I'm not sure in what environments this is likely to be
479.
by kbolino 2y ago
It was definitely 1. There were ways to demonstrate the issue without involving goroutines, such as by creating a list of closures in a loop, one at each iteration, and then invoking them synchronously after the loop exits. They would all h
480.
by kbolino 2y ago
The RFC defining them says they're the same and has since the earliest draft I can find, also from 2002. You should offer more explanation when you take a stance contrary to what is well documented.

More ›