Am 20.12.19 um 22:59 schrieb Steve Naidamast blackfalconsoftw...@outlook.com [firebird-support]: > The first would be using DotNetZip to compress and encrypt the Firebird > database file into a zip file with a pass word. The next level of encryption > would be to take the zip file and encrypt it again using standard file > encryption technologies (ie: AES) Each set of compression\encryption > processes would use a different internally generated key every time the > process is initiated.
This is acceptable for transporting database file, it does not really work while your application is using database. > This may not be a perfect solution but I have it working to a point where the > response time of these processes are acceptable on a Firebird database file > of 1.5 gigs. However, it will be up to the user to set what they want > through my application's security options, which will provide the option to > do one or both security processes upon opening and closing the application or > upon demand. Really pack&encrypt 1.5GB on start/close? The user still can Copy FDB-file while it is unpacked... > My concept is distantly related to your own Encryption schemes in Firebird > 3.0 where your security is supported by third-party plugins instead of using > a singular security scheme built in to the database engine. "third-party" does mean that this code is not part of firebird package.it should be possible to write an plugin of your own. Elmar
