Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mnordhoff
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
mnordhoff
13y ago
Hypothesis: They don't say which "[r]ecent press coverage". They could be referring to some badly-worded rehash of the Reuters story.
92.
▲
by
mnordhoff
13y ago
> Well, they're clearly claiming that the "secret contract" as reported did not exist. Crap. They're only denying a carefully-worded strawman. They leave open: 1.) Adding support for a known-flawed PRNG for free and t
93.
▲
by
mnordhoff
13y ago
You can afford dozens of $10 domain names, but dozens of $10 SSL certs would break the bank?
94.
▲
by
mnordhoff
13y ago
Security FYI: This situation concerns RSA keys, not 128-bit symmetric keys; our problem is "factoring a really big number", not "guessing a really big number". A 128-bit RSA key can be broken in seconds. RSA keys are com
95.
▲
by
mnordhoff
13y ago
Yes. They can already do this more reliably by disabling your domain name, though (not to mention your hosting). Edit (T+16 minutes): I said "more reliably" because not all TLS clients perform CRL or OCSP checks -- as mentioned in
96.
▲
by
mnordhoff
13y ago
Oh god, yes it is. Especially when you realize halfway through that the iPad cannot type "`". (You can copy and paste it, though.)
97.
▲
by
mnordhoff
13y ago
I don't have experience with mock, but I've used object() -- literally -- as a sentinel. _sentinel = object() def print_now(now=_sentinel): if now is _sentinel: now = time.time() ...
98.
▲
by
mnordhoff
13y ago
I hope "now" is never 1970-01-01 00:00:00. Edit: if now is None: now = time.time()
99.
▲
by
mnordhoff
13y ago
Using RC4 in TLS isn't entirely crazy. People started doing it due to the BEAST vunerability, which was a mistake in how AES was used in older TLS versions. https://en.wikipedia.org/wiki/Transport_Layer_Security#BE
100.
▲
by
mnordhoff
13y ago
https://en.wikipedia.org/wiki/FRA_law .se, huh?
101.
▲
by
mnordhoff
13y ago
Was that credit card number used anywhere else? Given Linode's size, it's not surprising for a few customers to have had coincidental CC compromises recently.
102.
▲
by
mnordhoff
13y ago
Malicious traffic doesn't make routers burst into flame. Customers get compromised on a daily basis at any large provider due to bad SSH passwords or WordPress vulnerabilities or whatever. Assuming the virtualization system is trustworthy (
103.
▲
by
mnordhoff
14y ago
> Also some hypervisors (for example VMware) only executes a VM when they have as many cores as the VM has cores available for execution. So having many logical cores in your VM can negatively influence CPU scheduling. Good thing Linode
104.
▲
by
mnordhoff
16y ago
Eleven! https://secure.wikimedia.org/wikipedia/en/wiki/List_of_oldes...
105.
▲
by
mnordhoff
16y ago
It's really a toss-up. Dallas is the second-closest, obviously. London might give you a westward route across Eurasia instead of eastward through the US. I think I'd probably do Newark or London, avoiding Dallas in case most of North Americ
106.
▲
by
mnordhoff
16y ago
Reliability and uptime are not subjective questions. Linode uses good data centers. None of them are particularly better than the others. All data centers occasionally experience downtime; Fremont was just unlucky this time. The only thing
107.
▲
by
mnordhoff
16y ago
Old post, but... FYI, it uses the epoch of caker -- i.e. the birthday of caker, Linode's founder.
108.
▲
by
mnordhoff
17y ago
FWIW, Linode pro-rates billing to the day, crediting unused funds back to your account, which is usually flexible enough when you only want a VPS for a few days.
109.
▲
by
mnordhoff
17y ago
What's the difference? The data center employees handle physical stuff. It's not like the Linode HQ is close to Atlanta, Dallas or Fremont, either.