Visit The New, Modern Unix Linux Community

Top Forums UNIX for Dummies Questions & Answers Is there an unrecoverable erase command? Post 152 by Neo on Wednesday 1st of November 2000 06:41:41 PM
Yes, there are many utilities available for UNIX systems which will destroy the data on hard drives and make them "unrecoverable". These utilities are not part of the standard distributions and are normally commercial or opensource applications. What OS are you using?
 
Test Your Knowledge in Computers #794
Difficulty: Medium
1/10 has a finite binary representation.
True or False?

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Erase files and directory

I have a set of files created under different name, but they all have the same directory name at some point. I will like to delete all the files and directories after the common name: Here is an example: techs\fins\results\oaks\bigs tech2\gihs\results\gears\picks ... (3 Replies)
Discussion started by: odogbolu98
3 Replies

2. UNIX for Dummies Questions & Answers

stty erase e command

I'm not familiar with the stty command. What would "stty erase e" do to my system and what kind of problems would it create? Also, how would I undo this command? (1 Reply)
Discussion started by: CEngel0327
1 Replies

3. UNIX for Dummies Questions & Answers

erase file

I have a file that always generated in the system eg. /tmp/log.txt , it is generated by the application program , but this file should not be present in the system otherwise there are some program problem , I want to erase this file once the program has generate it , as I know , it can link to... (2 Replies)
Discussion started by: ust
2 Replies

4. UNIX for Advanced & Expert Users

stty erase in a script

does anyone know how to incorporate this in a script so users can actually make use of their backspace button that they've grown accustomed to? stty erase ^H --- this isn't working the script. works on command line but i wanna invoke it whenever this program of mine is run so users can use... (2 Replies)
Discussion started by: Terrible
2 Replies

5. UNIX for Advanced & Expert Users

stty erase r

after hitting this command...on pressing r acts as a backspace character.... how to disable this function (5 Replies)
Discussion started by: bishweshwar
5 Replies

6. Filesystems, Disks and Memory

"mt erase" command does not work

Hi I have some data in my tape which I want to erase with the command mt erase The process runs for a long time without cleaning data. What can be the problem?? krishan (2 Replies)
Discussion started by: krishan
2 Replies

7. UNIX for Dummies Questions & Answers

Erase an at job

Hello everybody i need to erase a at job that i write. I wrote at 22 at>execute a command at>Ctr + d How do i erase this? I don`t wan`t to do this. I need to change something when i pressed ctrl + d give a job number (2 Replies)
Discussion started by: enkei17
2 Replies

8. AIX

How to use dd command to erase the data in disk

how to use dd command to erase the data in disk, such as hdisk2? (9 Replies)
Discussion started by: rainbow_bean
9 Replies

9. OS X (Apple)

Can I erase and start my mac with unix command

I made a tragic error and erased the extensions manager from my IMac. Now, I can't get the computer to boot up. It just stays on the gray screen. I've tried using the open apple+s method, which brings up the command console (not sure if I've got the lingo down right), and I've tried everything, but... (12 Replies)
Discussion started by: ccff22290
12 Replies

10. UNIX for Beginners Questions & Answers

Ps2pdf: Unrecoverable error

Good Day all, I'm new to ghostscript and have installed it in my unix system two days back. But while using ps2pdf, I get the error pasted at the bottom. I was able to convert my PS file via PDF Creator manually. But this error seems to be coming while using ps2pdf. My PS File is... (8 Replies)
Discussion started by: ADHVADARZIN
8 Replies
BZERO(3)						     Linux Programmer's Manual							  BZERO(3)

NAME
bzero, explicit_bzero - zero a byte string SYNOPSIS
#include <strings.h> void bzero(void *s, size_t n); #include <string.h> void explicit_bzero(void *s, size_t n); DESCRIPTION
The bzero() function erases the data in the n bytes of the memory starting at the location pointed to by s, by writing zeroes (bytes con- taining '') to that area. The explicit_bzero() function performs the same task as bzero(). It differs from bzero() in that it guarantees that compiler optimizations will not remove the erase operation if the compiler deduces that the operation is "unnecessary". RETURN VALUE
None. VERSIONS
explicit_bzero() first appeared in glibc 2.25. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +-----------------+---------------+---------+ |Interface | Attribute | Value | +-----------------+---------------+---------+ |bzero(), | Thread safety | MT-Safe | |explicit_bzero() | | | +-----------------+---------------+---------+ CONFORMING TO
The bzero() function is deprecated (marked as LEGACY in POSIX.1-2001); use memset(3) in new programs. POSIX.1-2008 removes the specifica- tion of bzero(). The bzero() function first appeared in 4.3BSD. The explicit_bzero() function is a nonstandard extension that is also present on some of the BSDs. Some other implementations have a simi- lar function, such as memset_explicit() or memset_s(). NOTES
The explicit_bzero() function addresses a problem that security-conscious applications may run into when using bzero(): if the compiler can deduce that the location to zeroed will never again be touched by a correct program, then it may remove the bzero() call altogether. This is a problem if the intent of the bzero() call was to erase sensitive data (e.g., passwords) to prevent the possibility that the data was leaked by an incorrect or compromised program. Calls to explicit_bzero() are never optimized away by the compiler. The explicit_bzero() function does not solve all problems associated with erasing sensitive data: 1. The explicit_bzero() function does not guarantee that sensitive data is completely erased from memory. (The same is true of bzero().) For example, there may be copies of the sensitive data in a register and in "scratch" stack areas. The explicit_bzero() function is not aware of these copies, and can't erase them. 2. In some circumstances, explicit_bzero() can decrease security. If the compiler determined that the variable containing the sensitive data could be optimized to be stored in a register (because it is small enough to fit in a register, and no operation other than the explicit_bzero() call would need to take the address of the variable), then the explicit_bzero() call will force the data to be copied from the register to a location in RAM that is then immediately erased (while the copy in the register remains unaffected). The problem here is that data in RAM is more likely to be exposed by a bug than data in a register, and thus the explicit_bzero() call creates a brief time window where the sensitive data is more vulnerable than it would otherwise have been if no attempt had been made to erase the data. Note that declaring the sensitive variable with the volatile qualifier does not eliminate the above problems. Indeed, it will make them worse, since, for example, it may force a variable that would otherwise have been optimized into a register to instead be maintained in (more vulnerable) RAM for its entire lifetime. Notwithstanding the above details, for security-conscious applications, using explicit_bzero() is generally preferable to not using it. The developers of explicit_bzero() anticipate that future compilers will recognize calls to explicit_bzero() and take steps to ensure that all copies of the sensitive data are erased, including copies in registers or in "scratch" stack areas. SEE ALSO
bstring(3), memset(3), swab(3) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 BZERO(3)

Featured Tech Videos

All times are GMT -4. The time now is 01:12 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy