Hacker News Reader

Encrypt multiple times with multiple encryption methods?

Including an in-house built cipher (task assigned to intern).

If there's reason to believe your team is better at cryptography implementation than the people behind the libraries you'd otherwise use, maybe. (This probably applies to the US national security establishment, not some random internet product).

If encryption is a core business function, you need as a prerequisite to having a business at all a couple of folks who know encryption well enough to roll their own.

> How does this apply to the types of programming like encryption where it is oft advised to not roll-your-own?

It basically doesn't apply to widely-used open source software.

Or to put it another way, you can always maintain an internal fork that currently has zero changes from upstream.