Table of Contents
If you want to send us your comments, please do so. Thanks
More on comments
Privacy commands
shred
Erase files (not recursieve)
shred can be found in the package coreutils
Directories can be removed with the --remove=[HOW] option
- HOW is in general optional
- The default mode for HOW is 'wipesync', but it can be expensive. Be careful
The HOW options (see also the man page)
- unlink : use a standard unlink call
- wipe : also first obfuscate bytes in the name
- wipesync : also sync each obfuscated byte to disk
shred --iterations=0 --remove --zero --verbose filetoshred # Only fill the file with zero's. Useful on a SSD or SD card shred --iterations=1 --remove --zero --verbose /foldertoshred/ shred --iterations=5 --remove --zero --verbose filetoshred
Fill with zero's
File('s)
Zero is in this case: 0x00
If you only want / need to fill the file with zero's ( 0x00 ) use --iterations=0 . 0 because the --zero pass is not counted as an iteration
shred --iterations=0 --remove --zero --verbose filetoshred
Empty space
You can use * zerofree * dd (Not advised, see the zerofree description: apt-cache show zerofree
wipe
Erase files and / or directories
Example
wipe -r -f -c -i -qQ 1 > /home/user/wipe.log WhatToWipe # WhatToWipe can be a file or a directory
-a | abort | Abort when an error occurs. Does not work in version 0.22 nor 0.23 |
-c | chmod | Turn write permissions off if needed |
-f | force | Do not ask for confirmation |
-i | verbose | Display what is going on |
-q | quick | Make 4 (the default) passes on each file |
-Q n | number | Set the number of passes to make. Needs -q |
-r | recursive | Decent into directories |
Errors
When using the option -S c , on Debian 10 Buster, this error can occur, even when executed as root
sh: 1: /dev/urandom: Permission denied Error: pipe command "/dev/urandom" must output at least 128 bytes (got 0)
Solutions:
- Do not use -S c
- Use -S r
- t.b.d.
scrub
scrub writes patterns on a disk or a file
DBAN
DBAN erases entire disks
autonuke is sufficient in most cases
nwipe
It is a fork of dwipe used by DBAN
nwipe --method=dodshort --verify=last --prng=mersenne --rounds=1 --logfile=/home/user/nwipe`date '+%Y%m%d.%H%M'`.txt /dev/sdx
This will also write all zero's to the drive in the last round
Windows
- Power the computer up and insert the DBAN CD
- If the computer boots into Windows
- Power down the computer
- Switch the power supply off or pull the power connector of of the (wall)socket
- Press the power key for a few seconds
- Connect the disk with Windows on it, via an SATA to USB cable, to an USB port
- Power the computer up
- When DBAN is started enter “autonuke” and hit ENTER
- When about 10 MB is wiped turn off the computer
- Switch the power supply off or pull the power connector of of the (wall)socket
- Press the power key for a few seconds
- Remove the SATA to USB cable
- Connect the disk to the SATA cable wich is connected to the motherboard
- Power the computer up
- When DBAN is started enter “autonuke” and hit ENTER
- Remove the DBAN disk from the drive
Intel Management Engine
Check the status of the IME. See ME cleaner
Requires git, make and some dev files to be installed. About 60MB. We got an error even after installing the pciutils-devel and zlib-develthe packages:
# make Checking for development libraries: pci and zlib... not found. For RPM based distributions like Fedora, please install pciutils-devel and zlib-devel. For DEB based distributions, please install libpci-dev and zlib1g-dev. Makefile:73: recipe for target 'pciutils' failed make: *** [pciutils] Error 1
To be investigated
Main subjects on this wiki: Linux, Debian, HTML, Microcontrollers, Privacy
RSS
Disclaimer
Privacy statement
Bugs statement
Cookies
Copyright © : 2014 - 2024 Webevaluation.nl and the authors
Changes reserved.