News for hackers. Stuff that matters.
Re:Cryptkeeper sets the same password “p” independently of u... by 3pt14159 on Monday January 30, 2017 @08:56AM (#13521153)
That's true in theory, but in practice most Ruby developers don't know how to use C or the FFI well enough to build a library out of a C or C++ library.

It's reasonable to shell out sometimes. It's what Github did when they were first starting. It's what 500px did when they were first starting. Trying to do everything the right way early on is just going to slow you down.

Re:Cryptkeeper sets the same password “p” independently of u... by deong on Monday January 30, 2017 @09:45AM (#13521527)
I think with security-related software in particular, the proper answer there is "tough". If you can't figure out how to call a C function, you should probably just not write critical software.
Re:Cryptkeeper sets the same password “p” independently of u... by wildmusings on Monday January 30, 2017 @10:58AM (#13522197)
One of the important lessons that the profession has yet to fully internalize is that there is very little software that is NOT security-related.
Re:Cryptkeeper sets the same password “p” independently of u... by Kalium on Monday January 30, 2017 @11:17AM (#13522384)
It's very, very difficult to get product managers to internalize that there are real security restrictions on how they can enable users to make things pretty.

Almost everything is security-related. Almost nobody is willing to work with this.