Jason:

This is a problem for everyone that owns a simple file server, no matter
what type of file is. :-)

For the first Rod message, I understand that the problem was direct access
to the file. Maybe Rod is using a os that don't have security (win98,...).

But I undestand that Rod's problem is the copy to another machine with a
'clean' isc4.gdb. And in that way, even if he don't owns the server, he just
needs to instruct the client for this subject. And it's up to his client to
protect the file, as he (maybe already) do with other files that security is
important.

Artur

----- Original Message -----
From: "Jason Chapman (JAC2)" <jason@...>
Newsgroups: egroups.ib-support
To: <ib-support@yahoogroups.com>
Sent: Thursday, April 10, 2003 4:06 PM
Subject: Re: [ib-support] ISC4 security MORE


> I think Rod's problem is when you install your software on a client site
> with their own Hardware Support who have access to the server. In essence
> there is no way i can see of protecting the info on the server without:
> 1) Using EFS (Encrypted File System), I believe this is an option with
W2K.
> 2) Supplying them with a server that is yours and they don't have access
to
> it at all.
> You then have the issue of backups and whether to make them encrypted
.....
>
> I think there has been talk of building a plug-in architecture, kind of
> like Blob filters to add functionality that isn't going to be in the core
> products. Ideas for the use of this are encryption, XML .....
>
> HIH
>
> JAC.
>