Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
remembered credentials for NAS
#11
where do I find it in v5?

JD
Reply
#12
I just found a bug with the credential feature unfortunately. I'm using the latest v5.0.0 beta_241125 version.

When you click on "Remember my credentials" the credentials are saved for the current Windows session.
But after a reboot or when you restart the HasleoBackupSuiteService service, credentials are lost.

Also: I didn't see any errors from the scheduled task or in the notification center (entries were cleared, why?), it just didn't backup anything.

Log shows this:

[Image: GhrYZCY.png]

When trying to manually backup, the credential window shows up again:

[Image: B7qatE9.png]

--
*Edit 1*

Ok, some more details for this bug:
- If you setup your user and password in the main program's "Settings" (after specifying a default location for the backups), credentials are saved correctly.
- If you instead setup your user and password in the popup that shows when clicking "Backup" manually, credentials are saved for the current session only.
- So maybe the credentials for the individual jobs are not saved correctly but there's a fallback to the default location credentials? Are credentials saved per job? Don't know exactly how that works.

So the workaround for this is to set your credentials via the default location setting.
You might also need to remove the current settings in registry:
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Hasleo\Backup Suite\ -> DefaultImageStoragePassword

--
*Edit 2*
Individual job credentials are still saved in NetConnect.db and the default credentials are saved in registry it seems.
I opened NetConnect.db, passwords are not stored as far as I can tell. Seems like a bug:

[Image: ey1WzQu.png]

--
*Edit 3*
Ok, sometimes the password is saved in that file and sometimes it isn't.

What I did:
- I created a new backup job after HBS installation. The default location was not yet set at this point.
- Then I created a new backup job with a network share and entered credentials for that job. NetConnect.db now holds that password.
- Now I set the default location to the same network share, HBS doesn't prompt for new credentials.

Result:
- Registry value for DefaultImageStoragePassword is now empty.
- The password in NetConnect.db is deleted.

Now you can still backup but after a reboot or service restart the credentials are missing and can't be saved permanently unless you set them again via default location.

No big deal but maybe for the future credentials should only be saved in NetConnection.db and not be mixed up with settings in registry. Then maybe implement a list in the GUI to see/delete saved credentials? Just a thought  Shy

--
*Edit 4*
Sorry for all the edits, but something else I just saw:
- I set default location to a local folder and created a job with a network share.
- I just closed HBS, restarted the HasleoBackupSuiteService service and reopened HBS.
- There's a chance the password in NetConnect.db is now gone. Doesn't happen all the time though but eventually will after some restarts.

Something is broken, I just don't know exactly where. But passwords get deleted from NetConnect.db somewhere...  Huh

So, bottom line is: Currently there's only 1 workaround afaik:
- Make NetConnect.db write protected. If it can't change, passwords are kept.
Reply
#13
Essentially found Al3x's finding are what I see also.

I had thought that the implementation would have an option associated
with each job so it could be enabled/disabled as needed rather than being
associated with the credentials dialog. I would like an option
that allows me to change my mind after the backup job is/was
created.

JD
Reply
#14
(11-27-2024, 03:16 AM)al3x Wrote: I just found a bug with the credential feature unfortunately. I'm using the latest v5.0.0 beta_241125 version.

When you click on "Remember my credentials" the credentials are saved for the current Windows session.
But after a reboot or when you restart the HasleoBackupSuiteService service, credentials are lost.

Also: I didn't see any errors from the scheduled task or in the notification center (entries were cleared, why?), it just didn't backup anything.

Log shows this:

[Image: GhrYZCY.png]

When trying to manually backup, the credential window shows up again:

[Image: B7qatE9.png]

--
*Edit 1*

Ok, some more details for this bug:
- If you setup your user and password in the main program's "Settings" (after specifying a default location for the backups), credentials are saved correctly.
- If you instead setup your user and password in the popup that shows when clicking "Backup" manually, credentials are saved for the current session only.
- So maybe the credentials for the individual jobs are not saved correctly but there's a fallback to the default location credentials? Are credentials saved per job? Don't know exactly how that works.

So the workaround for this is to set your credentials via the default location setting.
You might also need to remove the current settings in registry:
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Hasleo\Backup Suite\ -> DefaultImageStoragePassword

--
*Edit 2*
Individual job credentials are still saved in NetConnect.db and the default credentials are saved in registry it seems.
I opened NetConnect.db, passwords are not stored as far as I can tell. Seems like a bug:

[Image: ey1WzQu.png]

--
*Edit 3*
Ok, sometimes the password is saved in that file and sometimes it isn't.

What I did:
- I created a new backup job after HBS installation. The default location was not yet set at this point.
- Then I created a new backup job with a network share and entered credentials for that job. NetConnect.db now holds that password.
- Now I set the default location to the same network share, HBS doesn't prompt for new credentials.

Result:
- Registry value for DefaultImageStoragePassword is now empty.
- The password in NetConnect.db is deleted.

Now you can still backup but after a reboot or service restart the credentials are missing and can't be saved permanently unless you set them again via default location.

No big deal but maybe for the future credentials should only be saved in NetConnection.db and not be mixed up with settings in registry. Then maybe implement a list in the GUI to see/delete saved credentials? Just a thought  Shy

--
*Edit 4*
Sorry for all the edits, but something else I just saw:
- I set default location to a local folder and created a job with a network share.
- I just closed HBS, restarted the HasleoBackupSuiteService service and reopened HBS.
- There's a chance the password in NetConnect.db is now gone. Doesn't happen all the time though but eventually will after some restarts.

Something is broken, I just don't know exactly where. But passwords get deleted from NetConnect.db somewhere...  Huh

So, bottom line is: Currently there's only 1 workaround afaik:
- Make NetConnect.db write protected. If it can't change, passwords are kept.

V5.0 Beta 1 has been released, please check to see if the issue still persists?

For more information about V5.0 Beta 1, please refer to:
https://www.easyuefi.com/forums/showthre...54#pid6554
Reply
#15
(11-27-2024, 09:18 AM)JayDee Wrote: Essentially found Al3x's finding are what I see also.

I had thought that the implementation would have an option associated
with each job so it could be enabled/disabled as needed rather than being
associated with the credentials dialog. I would like an option
that allows me to change my mind  after the backup job is/was
created.

JD

I'm sorry that Windows doesn't provide a mechanism to establish a separate network share connection for a task, in fact any task will be able to access the network share once a task is connected. We'll add a feature to manage network connections in the future.
Reply
#16
(11-27-2024, 09:19 PM)admin Wrote: I'm sorry that Windows doesn't provide a mechanism to establish a separate network share connection for a task, in fact any task will be able to access the network share once a task is connected. We'll add a feature to manage network connections in the future.

Will you still have a look at that password loss problem before the next official release, though?
Reply
#17
(11-27-2024, 09:19 PM)admin Wrote:
(11-27-2024, 09:18 AM)JayDee Wrote: Essentially found Al3x's finding are what I see also.

I had thought that the implementation would have an option associated
with each job so it could be enabled/disabled as needed rather than being
associated with the credentials dialog. I would like an option
that allows me to change my mind  after the backup job is/was
created.

JD

I'm sorry that Windows doesn't provide a mechanism to establish a separate network share connection for a task, in fact any task will be able to access the network share once a task is connected. We'll add a feature to manage network connections in the future.

Is it possible to back up multiple NAS (Network Drive)?
Reply
#18
(11-27-2024, 10:43 PM)kammy Wrote:
(11-27-2024, 09:19 PM)admin Wrote: I'm sorry that Windows doesn't provide a mechanism to establish a separate network share connection for a task, in fact any task will be able to access the network share once a task is connected. We'll add a feature to manage network connections in the future.

Is it possible to back up multiple NAS (Network Drive)?

Do you mean backing up files located in multiple mapped network drives? Yes, of course you can.
Reply
#19
(11-27-2024, 10:18 PM)al3x Wrote:
(11-27-2024, 09:19 PM)admin Wrote: I'm sorry that Windows doesn't provide a mechanism to establish a separate network share connection for a task, in fact any task will be able to access the network share once a task is connected. We'll add a feature to manage network connections in the future.

Will you still have a look at that password loss problem before the next official release, though?

Does the problem still persist?
Reply
#20
(Yesterday, 10:25 AM)admin Wrote:
(11-27-2024, 10:18 PM)al3x Wrote: Will you still have a look at that password loss problem before the next official release, though?

Does the problem still persist?

Yes, I tried the current Beta 1 version, still a problem unfortunately.

Steps:
  1. Set default location to a local drive (probably not required).
  2. Create a new job with a network drive, enter credentials when prompted for (current Windows user should not have access by default).
  3. Do one backup, should work the first time.
  4. Close HBS, restart services.
  5. Open HBS again, try to "Restore". If it still works, repeat from step 4.

This works a few times but eventually credentials will be lost.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)