On 2006/11/02 11:53, Joachim Schipper wrote: > On Wed, Nov 01, 2006 at 11:54:24PM +0100, Marc Balmer wrote: > > stuartv wrote: > > >with an OpenBSD server. Unfortunately, since most of our > > >work is done using Access databases (and other Microsoft > > >Office products) we will have to continue using Windows > > >systems for our desktop systems (for now). This is a mix
You might not have too much work to move to a proper SQL backend and still use Access as the user-interface, there are ODBC drivers for pgsql/mysql, mdbtools and sqlfairy to help with translating. If you stick with keeping the data in mdb files, investigate oplock settings, google will find some references. > > Your setup is easy to do with OpenBSD but the encrypted filesystem > > OpenBSD does not offer. And it is not needed. Nobody will steal your > > file server. If people steal line cards from live routers (as reportedly was the cause of level3's outage in london yesterday) it's possible. > Actually, OpenBSD does offer encrypted filesystems - well, technically, > svnd(4) is an encrypting block device, but that's close enough. this isn't quite the same thing, the encrypted filesystem relevant to SMB file-serving is where individual files are (DES-)crypted by the server with public-key crypto to encrypt the DES key which is then stored with the file (the private key is stored as part of the user's login profile). As such this is something that would have to be implemented by Samba, not the OS. It's not something that's entirely useful - guess what - the file is sent over the wire in the clear. duh.
