Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Feature REQUESTS
I can confirm this new build is working now. The one thing I did differently, after updating to the same build last night, was to confirm that no HBS services or processes were running before I installed this new version. Everything seems fine now.
Reply
One thing I was thinking about is, why not add password protection to the entire task? That way the task cannot be edited or changed without the password. Is it needed? No. But it would be something good to have? Yes.
Reply
Deleting an encrypted backup through the program interface requires a password.
Deleting the same encrypted backup in Windows Explorer does NOT require a password. What's the point of this option?
There are two doors, one wide open, the other locked with a large padlock, but you don't go through the open door, you try to pick the lock.
In this form, it only makes sense for teenagers to play spy. It's not even close to MIG from Macrium, since the goal is to protect backups from ransomware, not to play with a password that's useless when deleting a backup.
Reply
I agree. I've been saying the same things for a long time; that HBS needs a driver-based protection solution. That will come, I've been told. But not yet. But does that mean that we can't have either one until we get both. In the meantime, you can use something like HideFolders to secure the directory. That's what I'm doing.

https://fspro.net/hide-folders/
Reply


Forum Jump:


Users browsing this thread: 39 Guest(s)