boxcryptor-single-file-decryptor

Open source code for basic Boxcryptor file decryption (by secomba)

Boxcryptor-single-file-decryptor Alternatives

Similar projects and alternatives to boxcryptor-single-file-decryptor

  • Tink

    Tink is a multi-language, cross-platform, open source library that provides cryptographic APIs that are secure, easy to use correctly, and hard(er) to misuse.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better boxcryptor-single-file-decryptor alternative or higher similarity.

boxcryptor-single-file-decryptor reviews and mentions

Posts with mentions or reviews of boxcryptor-single-file-decryptor. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-01-07.
  • Independent Audit: Insights into the Source Code of Boxcryptor
    2 projects | news.ycombinator.com | 7 Jan 2021
    TL;DR: this code should've never passed audit. I've found numerous problems, but I'll focus on the attack that lets someone successfully manipulate a ciphertext and have it successfully decrypt as something else. While the audit report says "Boxcryptor is not enforcing integrity [of ciphertexts]," this attack can let an adversary decrypt a (short) ciphertext, given a padding oracle. This company should've never rolled their own crypto in response to Authenticated Encryption, which has been solved, if you just use a pre-existing library.

    I'm surprised that this code has a "successful" audit. The cryptography _protocol_ that is implemented in the linked github repo (https://github.com/secomba/boxcryptor-single-file-decryptor) has several flaws (in addition to having some bad code practices that I'll skip over since this repo is supposed to only document the encryption protocols).

    First, the authors' problems appear to stem from their choice to manually implement an unusual (and inefficient) construction of the Authenticated Encryption primitive. Authenticated Encryption is the most common crypto primitive that people when they say "they want encryption." It's placed front-and-center in libsodium, ring, mundane, tink, monocypher, and every modern cryptography library that I've seen, since it is such a common operation. Modern Authenticated Encryption constructions include: AES-GCM, (X)ChaCha20-Poly1305. While there exist others, the industry has converged on these two as the standard.

    These block cipher modes did not emerge for no reason. The cryptography community has steadily iterated on what the default should be when somebody asks, "how can I encrypt my file." We've arrived at these constructions, in particular, because previous constructions have had security flaws.

    The authors of this repo have chosen to use the following protocol (for decryptDataPBKDF2):

    1. Derive two keys (KE, KH) from a password string using PBKDF2. KE is the encryption key used with AES, and KH is an HMAC key (used for multiple purposes, which is problematic).

Stats

Basic boxcryptor-single-file-decryptor repo stats
1
39
0.0
almost 4 years ago

secomba/boxcryptor-single-file-decryptor is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of boxcryptor-single-file-decryptor is C++.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com