I have been tasked with throwing together a small web app that will hold the passwords to different projects for my company.
I would like to use seaside to do this, but the biggest requirement is that we need to be able to either:
– encrypt the entire database, so that if the machine was compromised physically, the data would be useless.
– encrypt the username and password fields to facilitate the above, also.
i am thinking that the first option might be easiest to implement.
any ideas on how i would pull this off with pharo?
Have a look at the ApplicationSecurity package:
The NativeBoost version of my SQLite library supports SQLcipher which adds
transparent full database encryption to SQLite. It is not in the UFFI version
If it help I’m using NaCl to do secure the passwords. You should not store the passwords of your users, not even encrypted.
For securing the passwords I use Sha-512 over the salted password.
salt := (Nacl randomBytes: 16)
hashedPassword := Nacl hash: (salt , aPassword asByteArray)
^ hashedPassword asByteArray = (Nacl hash: salt asByteArray , aPassword asByteArray)
1) I have a different salt for each password, if a bad guy want the passwords he is going to need a different rainbow table for each user.
2) I do not store the password. I do not even store the hash of the plain password.
3) Still I’m able to validate the password.
* Note that I’m using Nacl>>randomBytes: to generate a cryptographically safe random value. Here is not really necessary, BUT you should use it if you are creating Session-IDs or Tokens.
Encrypting the database is *tricky*. You not only have to encrypt the database, but also secure the key. First you need to know how much security you want:
1) Be secure if someone hack into the user running pharo.
3) Be secure if someone steal the server.
4) Be secure if someone has physical access to the running server. (All your keys are in RAM)
2) Be secure if someone hack root. (I doubt anything is going to save you here)
For most projects/business (unless working with really sensitive data, such as medical data) securing the OS (users and root) and encrypting the hard-disk should be enough. Also do not forget to encrypt the connections. If everything is on the same server just use https. But you may need more if you use Load Balancers, multiple servers and databases.
Coincidentally, I’ve just updated my SHA256/512 password hashing library, which
wraps a C library of the same. The salt is variable length between 8 and 16
octets long, and the output is in the informally standard md5crypt format
This is speculation without knowing your scope and architecture,
but perhaps part of the puzzle is two factor authentication
via a $20 Yubico FIDO U2F Security Key.
BSD licensed C library for server-side..
P.S. It might be cool to link the yubico client-side libraries (LGPL)
into the VM for Iceberg to authenticate via U2F to github.