From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,aa529428387c8116
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-09-13 14:20:02 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsmi-us.news.garr.it!newsmi-eu.news.garr.it!NewsITBone-GARR!elvis.franken.de!chico.franken.de!news.franken.de!uni-erlangen.de!news-nue1.dfn.de!news-koe1.dfn.de!RRZ.Uni-Koeln.DE!blackbush.xlink.net!blackbush.de.kpnqwest.net!news.erfurt.thur.de!drcomp.erfurt.thur.de!not-for-mail
From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
Newsgroups: comp.lang.ada
Subject: Re: Crypting files with Ada
Date: 13 Sep 2002 20:42:43 GMT
Organization: Modern Electronics
Message-ID: <slrnao4je3.ui5.adi@drcomp.erfurt.thur.de>
References: <slrnao1f2i.271.randhol+news@kiuk0156.chembio.ntnu.no>
 <slrnao1h97.271.randhol+news@kiuk0156.chembio.ntnu.no>
 <slrnao23p4.o7a.adi@drcomp.erfurt.thur.de>
 <slrnao38p3.lm.randhol+news@kiuk0156.chembio.ntnu.no>
NNTP-Posting-Host: drcomp.erfurt.thur.de
X-Server-Date: 13 Sep 2002 20:42:43 GMT
User-Agent: slrn/0.9.7.4 (Linux)
Xref: archiver1.google.com comp.lang.ada:28962
Date: 2002-09-13T20:42:43+00:00
List-Id: <comp.lang.ada>

Preben Randhol <randhol+news@pvv.org> wrote:

>> So take your glibAda and call unlink(filename); Or even better
>               ^^^^^^^
>               what is this?

This is inexistend. Unfortunately. It is ment like 'glibc', but only
for Ada.

The library should implement remove() on top of the Kernel-API in Ada.

Another approach (which I don't like) would be a more or less direct
binding to glibc, so to say "Pragma Import" all the time.

> The problem is that if you simply delete a file in say Windows or Linux 
> you don't rease it you only delete the link. 

Right.

> So unless the OS has overwritten the place the file occupied with new 
> files one can recover it.

Yes. This is why someone intended wipe:

Description
       The  wipe  command  reads each file in sequence and writes
       over the file with nul characters.  If the  -i  option  is
       given,  it prompts the user before wiping the file.  If -d
       is given, it removes each  file  after  writing  over  it.
       (The default behavior is just to write over it.)  If -v is
       given, wipe will print the version number.

You may have a look at the source or re-implement it on your own. It
doesn't sound too difficult.
 
> I guess one could change every byte in the file with 0 and then write
> the file again before deleting it.

Better read from /dev/random :) And do multiple passes in order to
destroy remaining magnetization.


-- 
mail: adi@thur.de  	http://adi.thur.de	PGP: v2-key via keyserver

Das Gras steht hoch, man kann kaum mehr blicken,
das ist die richtige Zeit zum --- Rasenmaehen.