Missing openssl package in the container image

[hugochinchilla]

The backup encryption as documented in the examples is broken since the new Dockerfile does not include the openssl package.

Related to #123

[deitch]

Hmm, that is a good point. That example was created back when this was script based, the container had lots in it (include mysqldump); now it is a compiled binary. Then again, the container image remains alpine based, not FROM scratch, so it is possible to add things.

I see 2 possible approaches, although they aren to exclusive:

• Put openssl back in the container. It is a bit messy, in that you can get caught up in versions, and what happens if you run outside the container (it is meant to be run in both modes equally).
• Build encryption into mysql-backup itself.

Compiling it in is not as complex as it appeared at first glance. Most of the crypt packages already are included to support remote config (if enabled and used), so it won't increase the size in a noticeable way.

The downside is that it limits encryption to compiled in algorithms, but there only are so many people will use. I figure we can cover it with just a few:

• smime with aes256 with provided public key file (like the example)
• plain aes256 with provided symmetric key file
• pbkdf2+aes256 with provided passphrase file
• something else based on curve25519 (age?)