Encryption

​

When to use

⚠️ This is at-rest obfuscation, not strong cryptography. The AES key is derived from the configured public-key asset (or deviceUniqueIdentifier as fallback) — both are non-secret material available to the running app.

​

Role

• Local AES-256-CBC encryption — EncryptData/DecryptData encrypt/decrypt byte arrays for cache file storage. IV is randomly generated per operation and prepended to the output.
• Key derivation — uses SHA-256 of the configured PEM public key (extracted from -----BEGIN PUBLIC KEY----- markers) or, if absent, SystemInfo.deviceUniqueIdentifier.
• Public-key string flow removed — EncryptString/DecryptString are [Obsolete] and throw NotSupportedException. This flow was removed in Sprint 4.6 because it relied on RSA decryption with a public key, which is cryptographically impossible.

​

Inspector configuration

​

API Reference

​

Code

using Molca.Networking.Utils;
using UnityEngine;

public class CacheHelper : MonoBehaviour
{
    public byte[] EncryptForCache(byte[] rawData)
    {
        return Encryption.EncryptData(rawData);
    }

    public byte[] DecryptFromCache(byte[] encryptedData)
    {
        return Encryption.DecryptData(encryptedData);
    }
}

​

Troubleshooting

• EncryptString/DecryptString throw NotSupportedException: these methods were removed. Use EncryptData/DecryptData for byte-level encryption, or SecureStorage for credentials.
• Different device, different key: without a configured _publicKey TextAsset, the key derives from deviceUniqueIdentifier, meaning cache files are not portable across devices.

​

Related

• CacheManager — consumes Encryption for cache file obfuscation
• SecureStorage — encrypted storage for credentials (preferred for sensitive data)
• RuntimeManager — Encryption is a child subsystem