Dedicated server, Azure: "2022-10-03 18:19:29.235 ERROR NET: Failed to decode network.vault:" Any ideas how to fix?

[fargo007]

2022-10-03 18:19:29.235 ERROR   NET: Failed to decode network.vault: either hardware ID or OS username are different. Saved login data will be reset.

 

We get this error on our Azure hosted dedicated server whenever the server is started and used.  It's only fired up for missions and testing, so it's not kept running all the time.

 

The effect is that saved username/password and auto-login do not work, and a manual login must be conducted each time.

 

Just wondering if anyone has found a way around it.

 

Thanks y'all!

[HC_Official]

because you are using Azure the hardware ID will change from time to time, nothing you can do about this (There is not work around except go for a different hoster)

[c0ff]

Mmm, we can add an option to have login/password in the open. Either via the command line or via a file.
I think the file solution is better because it won't expose the data in the process list.

What do you think?

[shagrat]

vor 22 Minuten schrieb c0ff:

Mmm, we can add an option to have login/password in the open. Either via the command line or via a file.
I think the file solution is better because it won't expose the data in the process list.

What do you think?

Do NOT store any login/password in clear text, please. This is horrible  practice, from a security point of view. Even if there is no critical information connected to the specific login.

Some people still use no unique passwords, may use their normal DCS account login for the server, etc.

A file is at least better, but everyone storing a file with login credentials on a server, need to be very aware of the potential risk and take measures to secure them.

Specifically for Azure cloud Key Vault could be an option:

https://learn.microsoft.com/en-us/azure/key-vault/general/basic-concepts#authentication

Edited November 4, 2022 by shagrat

[c0ff]

Agreed on plaintext storage.

We definitely won't implement any vendor-specific auth management.

However, we can, for example, add support for reading login/password from lua, where you can load your own code (even a DLL), implementing your specific requirements.

[fargo007]

It's not the UN/PW that is at issue here but the hardware ID.

[ColinM9991]

On 11/4/2022 at 10:01 AM, c0ff said:

Agreed on plaintext storage.

We definitely won't implement any vendor-specific auth management.

However, we can, for example, add support for reading login/password from lua, where you can load your own code (even a DLL), implementing your specific requirements.

How about not requiring credentials for the dedicated server? Aside from the fact that servers are linked to your store account, it makes no sense to demand users to type in credentials on something that should be headless and unattended.

I appreciate there's a local web portal for changes, but I think FTPing some config files over to configure the server is generally a better idea as it frees up the need to have it tied to an account in the first place.

[c0ff]

from the next update, DCS in the dedicated server mode won't use hardware ID for encypting the nerwork.vault file anymore.

This should solve the issue with cloud-based servers.

The only thing you have to do is to log in manually once.

[fargo007]

Superb!  Thank you!