ArecaKeyMerge - Merge two or more Keyfiles from Areca-Controllers
------------------------------------------------------------------
When you create a volume(s) on a Areca-Controller and enable any kind
of hardware-encryption and create keyfiles with for example:
cli vsf genkey path=mykeys.bin
and create additional volume(s) later and your load your keys with:

cli vsf dlkey path=mykeys.bin
Volume: Abcdef     Serial: 642896439ed18585 Status: Encryption Key Assigned
Volume: Anotherone Serial: 5765439ed6363972 Status: Encryption Key Assigned
ErrMsg: Invalid Encryption Key File
GuiErrMsg < 0x00 >: Success.

You get an "ErrMsg: Invalid Encryption Key File" near the end,
because there are more encrypted volumes than keys in the file.

If you now do:
cli vsf genkey path=mynewkeys.bin
The 'old' volumes will be skipped and only the new keys will be written,
now you have to load two (or more) keyfiles each time.

If you use genkey2 it will create a separate keyfile for each volume !
(But same problem as above - if a keyfile was already created and
loaded for a volume - no new one will be written)

That's why i wrote ArecaKeyMerge, you just give it two or more source-
keyfiles and a destination and it will merge them all into one file.

Example output:
C:\Temp>ArecaKeyMerge.exe myraids.key newvol.key combined.key
CRC, Identifier and Filelength of "myraids.key" is OK !
Volume: DataRaid Serial: 739ed64289618584 Type: AESKey_256Bit Key: 'G...' (64 bytes)
Volume: ExtraRaid Serial: 739ed63657653971 Type: AESKey_256Bit Key: 'T...' (64 bytes)
CRC, Identifier and Filelength of "newvol.key" is OK !
Volume: NewVR Serial: 739ed60509239015 Type: AESKey_256Bit Key: 'M...' (64 bytes)
Written 3 Keys to "combined.key" succesfully !

You'll get warning messages when the CRC, Identifier or Filelength of
keyfiles doesn't match, but ArecaKeyMerge will continue creating a new file.

Currently implemented Volumetypes are:
256Bit Password
256Bit AES Key
128Bit Password
128Bit AESKey

If you get an Errors about Unknown Volumetype, send me the keyfiles/
informations about the volumes you got and i will have a look at it/
add it to ArecaKeyMerge.

ArecaKeyMerge can't overwrite files, to ensure
accidental deleting of sourcekeys doesn't happen.

ArecaKeyMerge needs a .NET 2.0 Framework to run.

Viruscheck of the Exe shows: 2 / 69
https://www.virustotal.com/de/file/da56aa7474aebb7a7d232465820928f057ef64c1c7992b8ded985dd4b0ba9d14/analysis/1538852673
I guess two "matches" because so many "Serial", "Password", "Keyfile",
"AESKey" and "CRC"-Strings in the Exe, they might think its a
crypto-trojan. ^^

You can copy your keyfiles in a virtual machine and use ArecaKeyMerge from
there, it doesn't need anything from the controller or access to the volumes. 

Please donate something for my efforts to Paypal:
Holger.Hippenstiel@gmx.de Thanks in advance ! :)
