From:	Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Some dodgy FILE hackery
Date:	15 Mar 2000 18:30:00 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	19
Message-ID:	<8aokr8$s7u$1@nets3.rz.RWTH-Aachen.DE>
References:	<8amfqu$ue5$1 AT newsg2 DOT svr DOT pol DOT co DOT uk> <200003150008 DOT TAA21146 AT envy DOT delorie DOT com> <38CFD37F DOT 44FD33CB AT bigfoot DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 953145000 28926 137.226.32.75 (15 Mar 2000 18:30:00 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	15 Mar 2000 18:30:00 GMT
User-Agent:	tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

JP Morris <doug-15 AT bigfoot DOT com> wrote:
> DJ Delorie wrote:
>> 
>> > So, using DJGPP, is there a way to intercept read() and write() in order to
>> > encrypt/decrypt the data they are writing/reading? How do I do it?
>> 
>> Use file system extensions.  See "File System Extensions" in the docs,
>> or http://www.delorie.com/djgpp/doc/libc-2.02/libc_284.html

> Presumably this is seriously unportable.

So what? The OP specifically asked for a solution based 'using DJGPP',
and this is the DJGPP newsgroup. And of course, read() and write()
themselves are already unportable (to non-Unix systems, at the least),
so intercepting such system calls must be seriously unportable by
definition of the task.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -