Aller au contenu principal

Password/Encryption don't seem to work

Thread needs solution

Hi,

I upgraded to 2017 from a 30 day trial version yesterday. Everything seems to be working fine except password protection and backup.

During the trial I set up 3 drives with password plus ARS256 encryption. Early on in the trial I did a few restore tests and I'm pretty sure I had to supply my password.

However since yesterday I found that I could restore folders and files without having to supply the pasword. I recovered the data and it was unencryted. 

I even created a new backup today with pasword and encryption but still didn't have to supply password - not even on deletion!

Thanks

 

 

 

 

 

0 Users found this helpful

Keith, welcome to these user forums.

Please see post: 128812: No password when restoring encrypted backups in build 8029? where this issue has already been reported by a number of users, myself included.  This is an issue that has been introduced with build 8029.

Keith,

It may help set your mind at ease a little to know that the encryption IS working. The issue is that the updated user interface now remembers your passwor so when you restore from within that interface it will no longer ask you for credentials. If you tried to open the backup file from within Explorer or on another computer, it will not work without the password. 

Despite this, I'm hoping this behavior will be changed as I'm not comfortable with ATI storing encryption passwords locally on the computer. 

Philip.

Steve & Philip - thanks for the responses.

Good to know that I've not screwed up although rather disconcerting regarding the local password storage.

Keith

 

 

Guys, as I've thought about this more, I realized that some type of local password or key storage is a requirement for unattended incremental or differential backups to function. If the local engine couldn't decrypt the existing base backups it wouldn't be able to add to them and validate them in the background. So I'll retract my concerns about key storage, but I still think the product should require a password for user-initiated actions on the backups or their schedules/settings. 

Philip, I was asked for further information on my Support Case for this issue yesterday which I provided, so the developers are still working on it plus the Customer Central person could also reproduce the issue too.

Seve & Philip,

I have followed your posts here and also those on the earlier thread and am a bit puzzled. It seems that TI 2017 build 8029 purposefully updated the UI such that any process within the TI app on password-protected backups set up by the same user no longer requires access credentials.  I also follow the parts where access outside of the app and by different users still require the password. 

So is the issue now that this functional amendment could present a security risk and therefore requires a mod?

Thanks

Keith

 

 

 

 

KeithM wrote:

Seve & Philip,

I have followed your posts here and also those on the earlier thread and am a bit puzzled. It seems that TI 2017 build 8029 purposefully updated the UI such that any process within the TI app on password-protected backups set up by the same user no longer requires access credentials.  I also follow the parts where access outside of the app and by different users still require the password. 

So is the issue now that this functional amendment could present a security risk and therefore requires a mod?

Thanks

Keith

Cloud backups still require passwords for any changes - local backups, from within Acronis are accessible by anyone with admin access.  This seems to be a security flaw (or function) of 8029 - that's what's under investigation as I don't think it was done purposefully, but if it was, would also like it returned to the previous method.  

However, as it stands with 8029 at the moment, if you have a password protected encrypted backup .tib file, without physical access to the computer and the ability to launch Acronis with an admin account, the backup is still protected up to that extent (if someone does have an admin account on that particular pc and laucnhes Acronis, they could modify the backup task or restore files from it).  Then again, someone with admin access to yoru computer could just as easily take ownserhip of your user profile and get access to your data that way too so in that regard, it's no less safe.

But, the good news, is you can't take a backup .tib and move it to another computer and access it if it has an encrypted password on it.  This behavior is not in the NG6116 version but appeared in the 8029 standard version which, we're assuming is a bug (and potential security issue) that is being investigated.  

I got a mail yesterday from the support and they told me the following:
"I would like to inform you that if any one will change the file/ folder for the encrypted backup task it will ask for the backup encryption password  and with the backup encryption password no one can harm your backup task."

I don´t know how this new feature is actually supposed to work, but i can without being promted to type the password for a local file and folders backup job easily remove files from the backup and add other files and then perform the backup. I am never promted to type the password.

So today a person with access to the computer can easily destroy an existing, encrypted, backup job.

 

Roger, as Rob said earlier, this is a security bug in the latest build 8029 - I have an open Support Case for this and have had no conclusion suggested to me for this issue - I certainly will object to the current behaviour if they try to suggest that this is now the new 'normal' usage!

Keith, please see my comment on the matter at https://forum.acronis.com/forum/128812#comment-407476

Regards,

Slava