"PasswordFormat": 1, how do I use this command?

[AzKat 🐔]

Long story short, read up a bit, but I only see how to provide the --cryptkey=<key> argument, but I haven't seen a way to use the initial vector argument.

How can I use it?

Do I just go with
--initialvector=<iv>

Solution
1. Use "PasswordFormat": 0 in the config and keep your passwords in the config files as plain text
2. Add --cryptkey=<key> to shortcut of ASF (or in the arguments field if you're launching via task scheduler) 
<key> stands for a random string of characters.
Example: 
C:\ASF\ASF.exe --cryptkey=1234abcd (this is your custom key, don't use 1234abcd, make your own)

3. Save the shortcut or click "ok" on the task scheduler action window.
4. Launch the shortcut that contains the --cryptkey=1234abcd
5. Wait for all bots to load
6. Press C
7. Type in !password bot_x (This will generate the AES password that you can store in the config file for the bot named "bot_x") 
8. Copy the AES string it generated (CTRL+M to mark, select with left click, right click to copy)
9. Paste the AES string it generated into your bot config .json file, replacing your plain text password (in this example the file is named bot1.json)
10. Change from "PasswordFormat": 0 to "PasswordFormat": 1
11. Close ASF and save the config file
12. Check that you get no errors / warnings in the ASF gui (it will automatically restart the bot once you make a change to the config file)
13. Repeat steps 4-12 for each bot you want to set AES encryption on 

[Archi]

You can't, it's automatically generated and saved together with the encrypted value, as it serves similar purpose to salt in other encryption algorithms.

There's no direct benefit of being able to provide it. It's enough to say that it's unique per every generated password, you can verify that by executing !encrypt 1 <stringToEncrypt> several times to notice that the output is different despite same string being encrypted.

Is there a particular need why you'd like to set it yourself?

[AzKat 🐔]

Originally posted by Archi:

You can't, it's automatically generated and saved together with the encrypted value, as it serves similar purpose to salt in other encryption algorithms.

There's no direct benefit of being able to provide it. It's enough to say that it's unique per every generated password, you can verify that by executing !encrypt 1 <stringToEncrypt> several times to notice that the output is different despite same string being encrypted.

Is there a particular need why you'd like to set it yourself?

There is no particular need besides not being able to use said --cryptkey as it would give ... quite a few errors in the console and in the end asking me for the password for each account.

Basically I would set the --cryptkey=<key> as the "secret key" as an argument to a shortcut so I could see the GUI and I would set the base64 encrypted value in the steampassword field.
Then when I'd start the shortcut, I'd get the password invalid error, as well as a bunch of other errors.

code of errors:

2020-11-24 20:11:22|ArchiSteamFarm-4644|ERROR|ASF|DecryptedSteamPassword() SteamPassword is invalid!
2020-11-24 20:11:22|ArchiSteamFarm-4644|ERROR|ASF|DecryptAES() System.Security.Cryptography.CryptographicException: Padding is invalid and cannot be removed.
   at Internal.Cryptography.UniversalCryptoDecryptor.GetPaddingLength(ReadOnlySpan`1 block)
   at Internal.Cryptography.UniversalCryptoDecryptor.UncheckedTransformFinalBlock(ReadOnlySpan`1 inputBuffer, Span`1 outputBuffer)
   at Internal.Cryptography.UniversalCryptoDecryptor.UncheckedTransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
   at Internal.Cryptography.UniversalCryptoTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
   at System.Security.Cryptography.CryptoStream.ReadAsyncCore(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken, Boolean useAsync)
   at System.Security.Cryptography.CryptoStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at SteamKit2.CryptoHelper.SymmetricDecrypt(Byte[] input, Byte[] key, Byte[]& iv)
   at SteamKit2.CryptoHelper.SymmetricDecrypt(Byte[] input, Byte[] key)
   at ArchiSteamFarm.ArchiCryptoHelper.DecryptAES(String encryptedString)
2020-11-24 20:11:22|ArchiSteamFarm-4644|ERROR|ASF|DecryptedSteamPassword() SteamPassword is invalid!

edit: should be noted that I can decrypt the exact password using the key and the IV

edit#2: ... should I have created this AES password using the builtin command?
I'm most likely doing something wrong as the bot can login using the base64 encrypted password, despite it giving 2x messages for each bot about:

2020-11-24 20:22:38|ArchiSteamFarm-4968|INFO|b1|OnConnected() Logging in...
2020-11-24 20:22:39|ArchiSteamFarm-4968|INFO|b1|OnLoggedOn() Successfully logged on as 76561198200258575.
2020-11-24 20:22:39|ArchiSteamFarm-4968|INFO|b1|Init() Logging in to ISteamUserAuth...
2020-11-24 20:22:39|ArchiSteamFarm-4968|INFO|b1|IsAnythingToFarm() Checking first badge page...
2020-11-24 20:22:39|ArchiSteamFarm-4968|INFO|b1|Init() Success!
2020-11-24 20:22:41|ArchiSteamFarm-4968|INFO|b1|StartFarming() We don't have anything to idle on this account!
2020-11-24 20:23:02|ArchiSteamFarm-4968|ERROR|ASF|DecryptedSteamPassword() SteamPassword is invalid!
2020-11-24 20:23:16|ArchiSteamFarm-4968|ERROR|ASF|DecryptedSteamPassword() SteamPassword is invalid!

[Archi]

You are doing something wrong. You should use plaintext password and not touch password format, use !encrypt command to generate encrypted string, then put it in the config and change password format, as the security page on wiki tells you to. And you should supply --cryptkey before you do the !encrypt command and all the time afterwards.

[AzKat 🐔]

Originally posted by Archi:

You are doing something wrong. You should use plaintext password and not touch password format, use !encrypt command to generate encrypted string, then put it in the config and change password format, as the security page on wiki tells you to. And you should supply --cryptkey before you do the !encrypt command and all the time afterwards.

Oh, that explains it, I thought I had to generate the password myself, however from what I see, the !password command gives me an encrypted password as well, and if I use this AES password it does indeed work.

Thanks for the assist, and please add "examples" to your sections, as people such as I read between the lines too much :(

Also one final thing, is it normal to get different passwords each time I type in:
c !password b1

[Rudokhvist]

Originally posted by AzKat:

Also one final thing, is it normal to get different passwords each time I type in:
c !password b1

you really should start paying attention

Originally posted by Archi:

you can verify that by executing !encrypt 1 <stringToEncrypt> several times to notice that the output is different despite same string being encrypted.

[ℓαтєяαℓυѕ ⛧]

please help, i followed your guide untill step 7,
my bot name is BOT1
when i put command !password BOT1
it replies

>> Enter command : !password BOT1
<> Executing...
<< <BOT1> Unknown Command!

[Rudokhvist]

Originally posted by ℓαтєяαℓυѕ ⛧:

please help, i followed your guide untill step 7,
my bot name is BOT1
when i put command !password BOT1
it replies

>> Enter command : !password BOT1
<> Executing...
<< <BOT1> Unknown Command!

Don't hijack other user's thread, create your own.