Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
josephcsible
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
1497 ms
·
8371.
▲
by
josephcsible
6y ago
There's actually a third certificate for "USERTrust RSA Certification Authority", also using the same key pair, signed by a different root called "AAA Certificate Services". It looks like the intended replacement fo
8372.
▲
by
josephcsible
6y ago
If you're rotating a self-signed certificate, then how do you suppose that clients securely trust it? Or if you just mean replacing it when it expires, then this could instead be tied to the underlying public key alone, which can be re
8373.
▲
by
josephcsible
6y ago
They said "certificates should never expire or should expire daily". Roots already can't be revoked, so they should never expire. Intermediates and leaves should expire daily. Since currently, OCSP responses are often valid f
8374.
▲
by
josephcsible
6y ago
IMO, there's a bit of a design flaw with curl here. There should be an easy flag to say "trust the particular certificate with this hash, no matter what's wrong with it", but there isn't, so people instead use the o
8375.
▲
by
josephcsible
6y ago
Exactly. Certificate expiration has never really been about security. It's purely for practicality, so that CRLs won't grow without bound. This is especially true now that we have OCSP stapling. From a security perspective, a shor
8376.
▲
by
josephcsible
6y ago
For anyone unaware of the details of this, here's the gist of it: if you run Oracle in a VM, you need to pay for Oracle licenses for every CPU of every host in the entire VM cluster, even if you know for sure it will never run on most
8377.
▲
by
josephcsible
6y ago
But even assuming the high end of your estimate, Postgres + PostGIS would still be less than 1/10 of the size of a baseline Oracle installation.
8378.
▲
by
josephcsible
6y ago
Yes to both, and doing so also makes it non-free per the FSF. Here's what they say about the Anti-996 license [1], as well as about this concept in general [2]. Caveat to the second point: while it is indeed incompatible with copyleft
8379.
▲
by
josephcsible
6y ago
Rust is probably the most mainstream language that uses affine types. Once you call a function that takes ownership of a value (e.g., `drop`), the compiler won't let you use it anymore after the function call.
8380.
▲
by
josephcsible
6y ago
Using classes and objects for laziness is a hack to work around the limitations of OOP. In more functional languages, there are better ways to accomplish that. For example, in Scala, you can just use "lazy val", and in Haskell, ev
8381.
▲
by
josephcsible
6y ago
You only lose deferred execution in this case because it didn't go far enough away from OOP and toward FP. For example, since Haskell is a pure functional language, it can be lazy by default, meaning the function-only version translite
8382.
▲
by
josephcsible
6y ago
That's actually an argument in favor of linear or affine types. In your example, you'd still get a new Wallet from that function, but the compiler would keep you from accidentally using the old one afterwards. That way, you can&#x
8383.
▲
by
josephcsible
6y ago
I don't think Rust really makes NULL dereferences any better. In practice, a NULL dereference in C is almost always "just" a crash that can't be turned into something worse (unlike the rest of these kinds of bugs), and R
8384.
▲
by
josephcsible
6y ago
Not a Firefox issue. The same happened to me in Chrome.