codahale

6 ms·

1.
by codahale 8y ago
Shamir’s is one of my favorite little crypto schemes. I’ve implemented it over GF(256) in a bunch of different languages just for fun: Haskell: https://github.com/codahale/hs-shamir Go: https://github.com&#x
2.
by codahale 8y ago
XML parsing is notably an even larger minefield: https://www.owasp.org/index.php/XML_Security_Cheat_Sheet
3.
by codahale 8y ago
Those safeguards were added by Travis CI folks as one of their remediation action items: https://github.com/DatabaseCleaner/database_cleaner/pull/521
4.
by codahale 11y ago
"You know the law: two men enter, one man leaves."
5.
by codahale 11y ago
While it’s definitely the case that there are more concise domain-specific examples, as you’ve pointed out, the article’s point stands: in Clojure, a Strategy is simply passing a function as an argument to another function.
6.
by codahale 11y ago
Obviously, those are monoliths in dire need of decomposition.
7.
by codahale 11y ago
3.1.x is a development branch and not intended for production use. When they release 3.2, MongoDB will support it.
8.
by codahale 11y ago
MongoDB doesn't track this information, unfortunately.
9.
by codahale 11y ago
And that 'nice' used to mean 'foolish'? http://www.etymonline.com/index.php?term=nice And that 'fizzle' used to mean 'fart quietly'? http://www.etymonline.com/index.ph
10.
by codahale 11y ago
Taubes breezily dismisses the Hall paper, which is, methodologically speaking, pretty conclusive. If you're curious about the paper and its implications for Taubes's obesity-insulin hypothesis, I'd recommend these two blog po
11.
by codahale 11y ago
800-273-8255 National Suicide Prevention Lifeline 24 hours a day, 7 days a week or www.suicidepreventionlifeline.org
12.
by codahale 11y ago
If you want your reads to ever work, then they need to be synchronized. Reading from an unfenced address during concurrent writes is undefined behavior for any CPU architecture you can think of, which means you’ll get stale reads _in a best
13.
by codahale 11y ago
It’s worth noting that not only do you need to synchronize access to the singleton, you need to synchronize access to the singleton’s state as well. And even if you manage that at a fine-grained layer, you’re still setting yourself up for a
14.
by codahale 11y ago
Two things: First, you're describing RSA signatures. "Encrypt X with your private key" means "X^D mod N" which is how RSA signatures work. In the context of RSA-based cryptosystems, it's clearer to just say &qu
15.
by codahale 11y ago
I really really really don't recommend outsourcing your security architecture to interested passers-by if that's going to be a core feature of your project.
16.
by codahale 11y ago
Apparently so. It uses DTLS, but I'm not sure where the certificates for that would come from or how their authenticity is verified. If it's all self-signed, then your best solution is TOFU (trust on first use). Otherwise your con
17.
by codahale 11y ago
* No confidentiality. All communications are sent plaintext. They plan to "add support in the future when solid approaches emerge". * Non-repudiable. Everything you send is signed with the public key on your GitHub account. * Uses
18.
by codahale 11y ago
Postgres: https://aphyr.com/posts/282-call-me-maybe-postgres
19.
by codahale 11y ago
That said, the ergonomics of the mutex design and the ownership system would probably eliminate most of the race conditions I've seen. Lock ordering can be effectively established by nesting mutexes: e.g. `Mutex<(X, Mutex<Y>)&
20.
by codahale 11y ago
Use bcry—ah, fuck it.
21.
by codahale 12y ago
I didn't do this in my spare time. I did this in rough a week and a half of full-time work.
22.
by codahale 12y ago
That was not the path taken by Amazon as they made their nearly 40 different APIs. Engineers from there could certainly speak to the circumstances behind their choices. As for aws-go, I had some APIs I needed to use and a machine-readable d
23.
by codahale 12y ago
The irony here is that your jaded insight is a retread of Fukuyama's 1992 framing of liberal democracy as a Hegelian end-state in _The End Of History_.
24.
by codahale 12y ago
(Apologies for the self-promotion, but it's at least on-topic.) I just opened up this repo yesterday: https://github.com/stripe/aws-go . It's really raw, but it uses the JSON API descriptions from botocore to
25.
by codahale 12y ago
Some LinkedIn job titles from current GitHub employees: * VP, Business Development & Services * Head of Technology Partnerships * CIO * VP, HR * Vice President, Strategy * Vice President, Marketing * VP Communications
26.
by codahale 12y ago
Marc's definitely the best.
27.
by codahale 12y ago
> I think it is funny that the author manages to blame everything and everyone except bad software. What would that accomplish? It's an article about the CAP theorem, not safety engineering or Byzantine fault tolerance.
28.
by codahale 12y ago
It's almost as if bad experimental design makes a blog article not worth reading.
29.
by codahale 12y ago
You separate your load generation tools from your system under test to eliminate confounding factors of shared resources like CPU, thread scheduler, memory allocator, disk, etc. This benchmark doesn’t do that, which means it’s impossible to
30.
by codahale 13y ago
I'm not here for debate club, Johnonymous. Like I said before, I'm here for the pearl-clutching.

More ›