Sponsored Content
Full Discussion: forbid file recovery
Top Forums UNIX for Dummies Questions & Answers forbid file recovery Post 302271339 by geekosaur on Wednesday 24th of December 2008 10:26:02 PM
Old 12-24-2008
Code:
dd if=/dev/zero of=dummyfile; rm dummyfile

Which just fills all available disk space with zeroes. You might want to follow with
Code:
dd if=/dev/urandom of=dummyfile; rm dummyfile

to overwrite with random data.

Note, if the machine in question is an ssh or https server, you don't want to exhaust the available entropy; consider generating one one machine and piping through ssh onto the other.
Code:
dd if=/dev/urandom | ssh other 'cat >dummyfile; rm dummyfile'

Note also that if this involves the root filesystem or a multi-user system this will cause problems when the disk fills. Think carefully before doing this on critical systems.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How can I forbid a user to go up his home directory

Hi everybody, How can I forbid a user to go up his home directory ? Thanks MarcoW (2 Replies)
Discussion started by: MarcoW
2 Replies

2. UNIX for Dummies Questions & Answers

shell script: forbid extension

Rather new to unix, so please don't beat me! I'm trying to get a list of files into a variable that I can use throughout the rest of the script. The challenge is that I need to exclude a certain extension from the list, and I'm having trouble with it. For example: item_a item_a.exe... (3 Replies)
Discussion started by: Loriel
3 Replies

3. Shell Programming and Scripting

forbid the error message

In my system , there is a script seems have a minor problem but I can't find it out , now everytime run the script , it will generate some error message to the system log , is it possible to forbid it generate the error to the system log or put all these message to /dev/null ? thx (3 Replies)
Discussion started by: ust
3 Replies

4. UNIX for Advanced & Expert Users

Recovery Of Passwd File

the file /etc/passwd has corrupted mistakenly.actually the file has saved as "oot:0:0:root:/root/sbin/bash". first r of root has been deleted .. can anyone tell me how can i recover as normal user (2 Replies)
Discussion started by: singh_hackerz
2 Replies

5. Solaris

Password Recovery From /etc/shadow file

Is it possible to reset a normal user password , by editing password field in /etc/shadow file? Thanks (6 Replies)
Discussion started by: ksvaisakh
6 Replies

6. Programming

How forbid use fork() in exec() program.

Hello World! I am writing code in C++ which have to launch another application X using exec(). I would like to set some limits on it using setrlimit etc... My problem is that i don't know how to forbid using fork() and strlimit by application X. How can i do it? (3 Replies)
Discussion started by: kzi
3 Replies

7. Cybersecurity

File Integrity checker with recovery

Hello friends I have an CentosOS 5 box running Apache, I want to Install a powerful File Integrity checker with recovery option to maintain any changes may be happened without my hand Could you help me to recommend such solution Thanks (3 Replies)
Discussion started by: reaky
3 Replies

8. HP-UX

@ character forbid to write in vi.

Hi ALL, I'm encountering this problem on HP Shell (tcsh) environment. Once I enter in vi to edit a file and add my sql script, like this: sqlplus user/pass @promo.sql(tu run my script) the @ character is not possible to write. I push on the key but is not written inside. Also in sqlplus... (3 Replies)
Discussion started by: cicalons
3 Replies

9. UNIX for Advanced & Expert Users

File recovery

Hi, Please let me know the way to recover the files deleted from home directory by 'rm*' command . Thanks in advance. (10 Replies)
Discussion started by: ravigupta2u
10 Replies

10. UNIX for Advanced & Expert Users

Is possible to recovery a deleted file in AIX?

is it possible to recovery a deleted file in AIX? (2 Replies)
Discussion started by: fiyas
2 Replies
RANDOM(4)						   BSD Kernel Interfaces Manual 						 RANDOM(4)

NAME
random , urandom -- random data source devices. SYNOPSIS
pseudo-device random DESCRIPTION
The random device produces uniformly distributed random byte values of potentially high quality. To obtain random bytes, open /dev/random for reading and read from it. To add entropy to the random generation system, open /dev/random for writing and write data that you believe to be somehow random. /dev/urandom is a compatibility nod to Linux. On Linux, /dev/urandom will produce lower quality output if the entropy pool drains, while /dev/random will prefer to block and wait for additional entropy to be collected. With Yarrow, this choice and distinction is not necessary, and the two devices behave identically. You may use either. OPERATION
The random device implements the Yarrow pseudo random number generator algorithm and maintains its entropy pool. Additional entropy is fed to the generator regularly by the SecurityServer daemon from random jitter measurements of the kernel. SecurityServer is also responsible for periodically saving some entropy to disk and reloading it during startup to provide entropy in early system operation. You may feed additional entropy to the generator by writing it to the random device, though this is not required in a normal operating envi- ronment. LIMITATIONS AND WARNINGS
Yarrow is a fairly resilient algorithm, and is believed to be resistant to non-root. The quality of its output is however dependent on regu- lar addition of appropriate entropy. If the SecurityServer system daemon fails for any reason, output quality will suffer over time without any explicit indication from the random device itself. Paranoid programmers can counteract this risk somewhat by collecting entropy of their choice (e.g. from keystroke or mouse timings) and seed- ing it into random directly before obtaining important random numbers. FILES
/dev/random /dev/urandom HISTORY
A random device appeared in the Linux operating system. Darwin September 6, 2001 Darwin
All times are GMT -4. The time now is 06:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy