Showing 2 open source projects for "metadata file"

View related business solutions
  • $300 Free Credits to Build on Google Cloud Icon
    $300 Free Credits to Build on Google Cloud

    New to Google Cloud? Get $300 in credits to explore Compute Engine, BigQuery, Cloud Run, Gemini Enterprise Agent Platform, and more.

    Start your next project with $300 in free Google Cloud credit. Spin up VMs, run containers, query petabytes in BigQuery, or build agents with Gemini Enterprise Agent Platform. Once your credits are used, keep building with 20+ always-free tier products including Compute Engine, Cloud Storage, GKE, and Cloud Run functions. No commitment required—just sign up and start building.
    Claim $300 Free
  • Our Free Plans just got better! | Auth0 Icon
    Our Free Plans just got better! | Auth0

    With up to 25k MAUs and unlimited Okta connections, our Free Plan lets you focus on what you do best—building great apps.

    You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
    Try free now
  • 1
    PTBC

    PTBC

    irreversible encryption with time self-destruction

    Petoron Time Burn Cipher (PTBC) A promising cipher based on self-destruction of time, complete absence of traces and impossibility of key selection. Key features: AES-CFB encryption with per-file IV Argon2id key derivation with 256MB RAM resistance TTL (time to live) built directly into the encrypted file HMAC-SHA512 integrity verification Self-deleting mode (--autowipe) and one-time access marking (--onetime) No file metadata, no recovery, no password resets Philosophy: If you lose the password - it’s over. If time expires - it’s gone. ...
    Downloads: 2 This Week
    Last Update:
    See Project
  • 2
    Naeon

    Naeon

    The safest way to store private data in untrusted (cloud) environments

    Naeon secures data in untrusted off-site storage through a layered approach: files are compressed, then AES-256 encrypted with a randomly generated 128-character passphrase yielding approximately 762 bits of entropy — far beyond the reach of both classical and quantum brute-force attacks. The ciphertext is obfuscated by prepending and appending random byte blocks, making the result unidentifiable as an encrypted file. The payload is then sharded into one private chunk — holding the encryption key and part of the data — and multiple equal-sized public chunks, each renamed to its SHA-512 hash and given a uniform timestamp to prevent metadata inference. A private filename conversion table preserves the concatenation order needed for restoration. ...
    Downloads: 3 This Week
    Last Update:
    See Project
  • Previous
  • You're on page 1
  • Next