Cryptography expert usually recommend not to use the same key (here the ransomware's public key) for transport and storage. Maybe the symmetric key should not e

Cryptography expert usually recommend not to use the same key (here the ransomware's public key) for transport and storage. Maybe the symmetric key should not even be stored locally. But the drawback is that with this approach the same symmetric key would be used to encrypt all files leaving it longer in memory. If 1 symmetric key is used per file it would mean that the ransomware would need to be queried for every file. Using a locally generated asymmetric key encryption key AKEK to encrypt the files means that: - The AKEK Pubkey can be kept in memory and the AKEK private key be sent immediately to the control center. - A different symmetric key can be used to encrypt every file and the control center can be queried only once to retrieve the AKEK private key On an unrelated note, I wonder if people thought about doing a DDOS on the onion service ... ?