There is a way. If you use older NW your password is using old XOR method to hide password. You can xor it again then and obtain value of the password (if you have such code). I used this couple of time In recent versions this is more secure, but not sure what they use it (you can find xored value in device properties or wherever they place it these days).
Correct. If you look at nsrdb you will find password. Grep for any NSR device for example and you will see the value. If this is short value, then it is old xored value. If longer one, then not sure what it is used and perhaps official support can decrypt it back (if using xor then can do that for sure).
mkeil
68 Posts
1
October 6th, 2016 22:00
Hi,
there is no way to obtain the current password.
It depends on the software used for DDBoost access.
For example in NetWorker you've to change the user/password in the device properties and on the VBA.
Regards
mkeil
ble1
4 Operator
•
14.4K Posts
0
October 7th, 2016 07:00
There is a way. If you use older NW your password is using old XOR method to hide password. You can xor it again then and obtain value of the password (if you have such code). I used this couple of time
In recent versions this is more secure, but not sure what they use it (you can find xored value in device properties or wherever they place it these days).
ble1
4 Operator
•
14.4K Posts
1
October 12th, 2016 01:00
Correct. If you look at nsrdb you will find password. Grep for any NSR device for example and you will see the value. If this is short value, then it is old xored value. If longer one, then not sure what it is used and perhaps official support can decrypt it back (if using xor then can do that for sure).
mkeil
68 Posts
0
October 12th, 2016 01:00
In the device properties are only some *:
remote user: test;
password: *******;
mkeil
68 Posts
0
October 12th, 2016 02:00
Thanks.
dirkbucket
1 Rookie
•
29 Posts
0
October 12th, 2016 05:00
Thanks for replies.
I modified the ddboost password and then changed in Avamar gui.
mkeil
68 Posts
0
October 12th, 2016 05:00
Ok, works now?