Hi all,
We have a client who runs a merged Server application, with web server
functionality.
We're now in the process of sorting out a SSL connection with this
application as they're now requesting data back from their Customers
when they log in via the web interface.
We regularly update the database structure by providing a new, merged
Server application, and this is uploaded to the client to install via a
standard non secure ftp upload.
To those of you who have similar setups - how do you deal with the
Private Key files?
Presumably it is a very BAD idea for us to get that file from the
client, install it in our development copy of the structure, compile,
merge, and then upload over a potentially insecure connection.
We could get the local IT manage to manually copy the relevant files to
the Server Database folder of the new version every time an update is
released, but we'd rather try and develop an automated solution.
Any suggestions?
Cheers,
Allan Udy
Golden Micro Solutions Ltd, Blenheim, New Zealand
http://www.golden.co.nz<http://www.golden.co.nz>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
