Enigma Node

Overview

The Enigma Node provides a suite of cryptographic utilities for encrypting, decrypting, signing, verifying, hashing, and generating random data. It supports multiple cryptographic algorithms including AES 256, ECC (ED25519), RSA, and hash functions (SHA-256, SHA-1). This node is useful in scenarios where secure data transformation is required within an automation workflow, such as encrypting sensitive information before storage or transmission, verifying digital signatures, generating cryptographic keys, or creating hashes for data integrity checks.

Practical examples:

• Encrypting user data with AES 256 before saving to a database.
• Generating RSA key pairs for secure communication setup.
• Creating SHA-256 hashes of files to verify integrity.
• Signing messages with ECC keys to ensure authenticity.
• Generating random strings for tokens or passwords.

Properties

When "HASH" is selected:

When "AES_256" is selected:

When "RSA" is selected:

When "ECC" is selected:

When "RANDOM" is selected:

Output

The node outputs JSON data containing the results of the selected cryptographic operation:

• For AES 256:

  • On key generation: { "key": "<base64 AES key>" }
  • On encryption:
    • If binary output disabled: { "encrypted": "<base64 encrypted data>" , "key": "<base64 AES key>" }
    • If binary output enabled: binary data containing encrypted content, IV, and tag.
  • On decryption:
    • If binary output disabled: { "encrypted": "<decrypted plaintext>" }
    • If binary output enabled: binary data containing decrypted content.

• For ECC:

  • On key generation: { "public_key": "<base64>", "private_key": "<base64>" }
  • On sign: { "encrypted": "<base64 signature>" }
  • On verify: { "valid": true|false }

• For HASH:

  • { "hash": "<encoded hash string>" }

• For RANDOM:

  • { "random": "<base64 random string>" }

• For RSA:

  • On key generation: { "public_key": "<base64>", "private_key": "<base64>" }
  • On encryption: { "encrypted": "<base64 encrypted data>" }
  • On decryption: { "decrypted": "<decrypted plaintext>" }

If binary output is enabled (only for AES 256 encryption/decryption), the node outputs the processed binary file data.

Dependencies

• Uses the @cubbit/enigma library for cryptographic operations.
• No external API services are required.
• Requires proper configuration of input parameters such as keys and messages.
• No special environment variables or credentials are needed beyond providing valid cryptographic keys in base64 format.

Troubleshooting

• Missing or invalid keys: Encryption and decryption require valid base64-encoded keys. Errors will occur if keys are missing or malformed.
• Incorrect IV for AES encryption: The initialization vector must be provided for encryption; otherwise, encryption will fail.
• Invalid input format: For binary processing, ensure the binary property name matches the actual binary data property.
• Signature verification failure: If the signature or keys do not match the message, verification will return false.
• Unsupported operations: Selecting incompatible options or omitting required parameters will cause errors.
• Error messages typically include details about missing keys, invalid base64 data, or unsupported operations. To resolve, verify all inputs and their formats carefully.

Links and References

• AES Encryption
• ECC (Ed25519)
• RSA Encryption
• SHA Hash Functions
• Base64 Encoding