void-linux / void-linux/void-packages

Package request: Cryptsetup-Nuke

Open
#51,791 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

request
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Package name

Cryptsetup-Nuke

Package homepage

https://gitlab.com/kalilinux/packages/cryptsetup-nuke-keys

Description

when creating an encrypted LUKS container, a master key is generated at random. A passphrase is then used to encrypt the master key in turn. This process means that the passphrase is not directly coupled to the data. That is, if two sets of identical data are encrypted and the same passphrase used, the master keys remain unique to each set and cannot be swapped out. What this also means however, is that regardless of the passphrase used, if the master key is lost, recovering data is impossible. This process conveniently lends itself to being used as a nuke by deliberately wiping the keys.

[https://www.kali.org/blog/nuke-kali-linux-luks/]

Does the requested package meet the package requirements?

Compiled

Is the requested package released?

Yes

Contributor guide

Open the contributing guide

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.

Research direction

No repository file or test is named. Start by reviewing the Cryptsetup-Nuke homepage and the repository's existing package requirements, then compare similar package definitions; done means the requested released package is added and builds successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.