Expand VC website's HiddenOS / PlausableDeniability page with PhantomDrive example

Open
#1,830 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
security

Research direction

Start by reviewing the PhantomDrive links in the issue and locating VeraCrypt's hidden-volume size selection and warning logic. Determine how the reported size mismatch could be explained or guarded against; done means VeraCrypt gives users actionable guidance about choosing a safer hidden-area size. The issue names no source files or tests, so first trace the relevant UI and validation paths.

Written by the indexing model from the issue text.

Description

Desired behavior

There is now a USB called PhantomDrive. It's failure is its hidden area is much bigger than unencrypted area.
Similar issue could happen to Veracrypt. Veracrypt should suggest user to pick a better size for hidden area.

Screenshots/Mockup/Designs

Additional information

Your Environment

Please tell us more about your environment

VeraCrypt version: Latest

Dominant language
C
Stars
11.7k
Forks
1.4k
Avg merge
1d 1h
Merged PRs (30d)
28

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from veracrypt/VeraCrypt

All issues in veracrypt/VeraCrypt

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.