On Tue, 25 Aug 1998 14:53:25 -0400, Hilary Stokes wrote:>However, with a new version of the Secure Server there will be better >documentation, so I would rather offer an upgrade that includes >the whole box set (CDs, manual, support). > >What are your thoughts for the upgrade? > >1) CD only at a low price >2) CD with documentation and support for a little more $.As an upgrade, I would prefer a CD only at a low price, with the documentation available on the CD as PDF or HTML, since here they are only likely to be read during install. I''m a little odd in that I like my docs in electronic form, to save office space on infrequently referenced items. One overall item I''d like to see Red Hat address somewhere is their testing policy. Is there a place to volunteer to read those new docs -before- release and provide feedback? I''m aware of the Raw Hide testing program, but how does Red Hat administer alpha/beta/document releases for selected critical packages such as the Secure Server?>Also, if you have any other comments/suggestions, please feel free >to email them to me at hilary@redhat.com.I would be forever in your debt if the next release of Secure Server included the mod_pyapache module, so that Python programs could be run directly. Since Red Hat already relies upon Python in their configuration tools, it''d be a natural addition. Of course, I suppose if the next release includes the necessary headers and such, it could be done as an add-on module. At the moment, I''m out of luck w/o source to rebuild the server. It seems the mod_pyapache maintainers didn''t structure their existing work to be a .so add-on. I''d hope that those includes in the next release will be packaged as a separate *-devel RPM package. Last, I''d like to see some of the schizo pathing re /home/httpd for some utilities bundled with the release and /home/httpsd for the server be straightened out. To explain, if the server goes into /home/httpsd, don''t put the htdig cgi-bin into httpd/cgi-bin where it won''t be found by the server right after install. Thanks for listening all, Jeff Rush
It would also be nice to have the opportunity to start the server unattended. Not to have to supply the pem pass phrase. A nice option would be too easily have the secure and unsecure doc root be the same. I am not convinced a virtual server is the most efficient way to do this. Thanks Brad
On Thu, 27 Aug 1998, Jeff Rush wrote:> I would be forever in your debt if the next release of Secure Server > included the mod_pyapache module, so that Python programs > could be run directly. Since Red Hat already relies upon Python > in their configuration tools, it''d be a natural addition.I''m the lead developer for the product. I''ll look into doing this. The includes in the next release will be packaged in a separate -devel RPM package, yes.> Last, I''d like to see some of the schizo pathing re /home/httpd > for some utilities bundled with the release and /home/httpsd for > the server be straightened out. To explain, if the server goes > into /home/httpsd, don''t put the htdig cgi-bin into httpd/cgi-bin > where it won''t be found by the server right after install.There will be consistency in the use of httpsd. The only file named with ''httpd'' and not ''httpsd'' will httpd.conf, because it is used to configure both secure and unsecure parts of the server. Sound reasonable? --- -Preston Brown Red Hat Software, Inc. pbrown@redhat.com
> > It would also be nice to have the opportunity to start the server > unattended. Not to have to supply the pem pass phrase.Count me in too.> A nice option would be too easily have the secure and unsecure doc root be > the same. I am not convinced a virtual server is the most efficient way > to do this.Could you not set this line in /etc/httpsd/conf/srm.conf to be the document root for the unsecure server as well? DocumentRoot /home/httpsd/html Or are you referring to running one binary for both secure and unsecure documents? Regards, Bill Pitz BRAM Corp. bill@bram.net / 707-773-1722
> > It would also be nice to have the opportunity to start the server > > unattended. Not to have to supply the pem pass phrase. > > Count me in too. > > > A nice option would be too easily have the secure and unsecure doc root be > > the same. I am not convinced a virtual server is the most efficient way > > to do this. > > Could you not set this line in /etc/httpsd/conf/srm.conf to be the document root for the unsecure server as well? > > DocumentRoot /home/httpsd/html > > Or are you referring to running one binary for both secure and unsecure documents?Why run 2 binaries and why maintain 2 separate document roots. I realize that everyones needs are a bit different, but I would be very curious to here how many people want to server https and http document out of the same directory. From the content of the traffic on this list, I would guess more than half? My request is to have a __simple__ & __effecient__ option to serve documents from the same directory. Thanks Brad
Its nice to have wishes granted. :) THANK YOU Brad> > It would also be nice to have the opportunity to start the server > > unattended. Not to have to supply the pem pass phrase. > > Instructions for doing this are in the manual. You must remove your > passphrase from your key. Doing so is NOT RECOMMENDED, as then if a > hacker gains access to your box they can steal your key and intercept all > your "secure" transactions. Not too good... > > > A nice option would be too easily have the secure and unsecure doc root be > > the same. I am not convinced a virtual server is the most efficient way > > to do this. > > This will be available in the next release. > > --- > -Preston Brown > Red Hat Software, Inc. > pbrown@redhat.com > > > -- > PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! > http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists > To unsubscribe: mail redhat-secure-server-request@redhat.com with > "unsubscribe" as the Subject. >
On Thu, 27 Aug 1998, Bradley Glonka wrote:> > It would also be nice to have the opportunity to start the server > unattended. Not to have to supply the pem pass phrase.Instructions for doing this are in the manual. You must remove your passphrase from your key. Doing so is NOT RECOMMENDED, as then if a hacker gains access to your box they can steal your key and intercept all your "secure" transactions. Not too good...> A nice option would be too easily have the secure and unsecure doc root be > the same. I am not convinced a virtual server is the most efficient way > to do this.This will be available in the next release. --- -Preston Brown Red Hat Software, Inc. pbrown@redhat.com
On Thu, 27 Aug 1998, Bradley Glonka wrote:> My request is to have a __simple__ & __effecient__ option to serve > documents from the same directory. >I addressed this question to the minivend users and, I thought, this list also. The most compelling answer was the possiblity of serving secure documents from the unsecure server. Stuff Happens you know. Rod