I have never used amsamba, i only use dd and tar type backups.
If you change my encryption script to write its arguments and errors to a file
it might be easier to see what is going wrong or if amsamba uses it differently
somehow.
echo "$@" > /tmp/encryptparams
/usr/bin/openssl enc -pbkdf2 -e -aes-256-ctr -salt -pass fd:3 3< "${PASSPHRASE}"
2> /tmp/encrypterrors
Anton "exuvo" Olsson
[email protected]
On 2022-05-06 11:03, Stefan G. Weichinger wrote:
Am 04.05.22 um 16:46 schrieb Exuvo:
Ah yes my RANDFILE was probably already created long ago when i initially set
up encryption.
From what i have read the random file is not really on most systems as it is
only there to help with low entropy systems (ie server that does nothing most
of the time).
Each time openssl runs it uses that file (if specified) for random seeds and at
command end it replaces the file with 256 new bytes of randomness for the next
invocation.
It is not needed for decryption.
From the man page the digest is only used to create the real encryption key
from the text key you supply. It should not affect speed at all.
The default digest is sha-256, sha-512 just has more bits. The only thing you
would gain is more protection against brute force attacks i think.
Thanks, great.
As mentioned on Github, I still see issues with your crypt-script when combined with
amsamba: that leads to dumps with "missing size line from sendbackup". Would be
great to get that fixed as well.
I will try to streamline and cleanup my config and report the actual dumptype
definition.
