Open Access Open Access  Restricted Access Subscription Access

FLASH VAULT

Mrs. Sabeetha, Bhoomash a k, Gokulan v, Gowtham v, Dharun Adithya i, Akileshwaran b

Abstract


Flash Vault is a privacy-first web-based application designed for secure and temporary sharing of encrypted messages and files. The system uses client-side encryption to protect user data before it is transmitted to the server. It implements AES-256-GCM through the Web Crypto API to provide confidentiality and data integrity. The application follows a zero-knowledge architecture where the server stores only encrypted data and never receives the encryption keys or plaintext content. Encryption keys are maintained in the URL fragment, keeping them separate from server requests. Users can share text and files up to 20MB through secure, temporary links. The system supports burn-on-read functionality and automatic expiration to ensure shared data is securely removed after use. It also incorporates temporary storage, automated cleanup, and rate limiting to improve security and prevent misuse. The primary objective of Flash Vault is to provide a simple, secure and privacy-focused solution for sharing sensitive information without permanent data storage.

Full Text:

PDF

References


National Institute of Standards and Technology (NIST). (2001). Advanced Encryption Standard (AES), Federal Information Processing Standards Publication 197.

Dworkin, M. (2007). Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC. NIST Special Publication 800-38D.

World Wide Web Consortium (W3C). Web Cryptography API. W3C Recommendation.

OWASP Foundation. OWASP Application Security Verification Standard (ASVS). OWASP.

OWASP Foundation. Cryptographic Storage Cheat Sheet. OWASP Developer Guide.

Mozilla Developer Network (MDN). Web Crypto API. MDN Web Docs.

Mozilla Developer Network (MDN). SubtleCrypto API and AES-GCM. MDN Web Docs.

Fielding, R. T. (2000). Architectural Styles and the Design of Network-based Software Architectures. University of California, Irvine.

Rescorla, E. (2018). The Transport Layer Security (TLS) Protocol Version 1.3. RFC 8446.

IETF. HTTP Semantics. RFC 9110.ocumentation: Real-Time Bidirectional Event-Based Communication.” Socket.IO Documentation.

Grigorik, I. (2013). “High Performance Browser Networking.” O’Reilly Media, Sebastopol, CA.

Fielding, R. T. (2000). “Architectural Styles and the Design of Network-Based Software Architectures.” Doctoral Dissertation, University of California, Irvine.


Refbacks

  • There are currently no refbacks.