Support

Hello,

long story short: don't worry, it was just a minor change in default archive name. You can safely ignore it.

Longer version: we made this change to make backup archives harder to guess, in the very very very (and let me say it again) very remote scenario where your output folder is readable.
Why is that so unlikely?
First of all you should have a broken server that does not respect .htaccess directives, since we put in every folder a file to block public web access. This means that you can't simply surf to any folder and download a file.
Then you should have ignored Akeeba Backup fatal errors about your output folder being web accessible, moreover Akeeba Backup will refuse to work if we detect that such folder is readable from the outside.
Finally, an attacker should know your backup name. Even if it had a default pattern, such name changes every time you take a backup, because the timestamp is included in the archive name.

Nevertheless, we still have "security" professionals that still contact us, claiming that our software is "insicure" since they could download site backups.
So we finally decided to get rid of those complains and we're adding a random string at the end of the archive.