From: Steffen Dettmer <steffenat_private> > * Kurt Seifried wrote on Thu, May 23, 2002 at 14:05 -0600: > One possible solution, assuming you need to write the data > but not read it until later is to encrypt it, generate a > public/private keypair using pgp/gnupg, load the public key > onto the server with your app, have it write > the files after encrypting the data. Thus you can retrieve > the data (ftp, www, whatever) and then decrypt it at your > leisure and use it. > I don't think that this makes things secure. If the web server > runs as nobody, the CGI script must be executable for nobody. The > secret key must be reable for nobody. Of course you can protect ^^^^^^ I interpreted Kurt's suggestion as meaning only the public key is available to the CGIs. Collection of generated records (online orders?) is done by another account on another machine. > Maybe you should search an ISP that offers i.e. suexec'd CGI > scripting. I tend to agree. A book [0] points out that without suEXEC or similar a buggy CGI might kill the webserver or modify logfiles even if there are no mutually-hostile CGI authors. There's nothing to stop you putting -T in your CGI scripts, setuid or not. If you're feeling ambitious you might jail the CGI and have it talk to the database or whatever through some sort of IPC application gateway. 0. "Web Servers, Security, & Maintanance", Larson & Stephens, 0-13-022534-7 -- ############################################################## # Antonomasia ant notatla.demon.co.uk # # See http://www.notatla.demon.co.uk/ # ##############################################################
This archive was generated by hypermail 2b30 : Tue May 28 2002 - 15:25:08 PDT