apache2 just shows the default apache start page rather than the SuSEhelp (or system status information) screen, which apache1 on 8.0 did. Apache/1.3.27 (Linux/SuSE 8.2) fails to start while the system boots for some reason , i am starting SuSE in init 3 mode . Please help , thank you. I've installed the rpms, Apache and mod_perl, mod_python and mod_php4. However, they don't seem to be taking effect. I've added : LoadModule php4_module /usr/lib/apache2-worker/libphp4.so to suse_loadmodule.

SSL (Secure Socket Layer) data transport requires encryption, and many governments have restrictions upon the import, export, and use of encryption technology. If Apache included SSL in the base package, its distribution would involve all sorts of legal and bureaucratic issues, and it would no longer be freely available. Also, some of the technology required to talk to current clients using SSL is patented by RSA Data Security, who restricts its use without a license.

Comanche (http://www.comanche.org) has not been updated since Apr 11, 2001 (at the time this is written). It *might* work with apache2, but it seems unlikely. Unfortunately, comanche is broken as of 8.1, because it became incompatible with the current Tcl version. [If you happen to know how to fix this, please contact us. Thanks.]

Apache-SSL does not add any date processing to the underlying components, so does not affect the overall compliance of your system. The main component, Apache, has this to say on the matter. You should also check your operating system, hardware and any other modules you include.

Ben Srour explains how he did it on Mac OS/X here. The process should be very similar for other Unix variants. Mailing Lists There are two Apache-SSL mailing lists. For support and general help from the Apache-SSL community, send a blank email to apache-ssl-help@lists.aldigital.co.uk. This is probably the most direct route to getting arbitrary questions answered. However, BEFORE posting your question, please check that it hasn't already been answered by searching the archive.

How do I configure TLS and the STARTTLS facility? imap-2006 supports SSL and TLS client functionality on UNIX and 32-bit Windows for IMAP, POP3, SMTP, and NNTP; and SSL and TLS server functionality on UNIX for IMAP and POP3. UNIX SSL build requires that a third-party software package, OpenSSL, be installed on the system first. Read imap-2006/docs/SSLBUILD for more information.

In the Webmin Servers module, create a new user and give him access to only the Apache Webserver module. After saving, click on Apache Webserver next to the user's name in the list of Webmin users and use the form that appears to deny him access to everything except one selected virtual server. Many other modules can also be configured in a similar way to restrict the access of a user to only certain DNS domains, Unix users or mail aliases.

The configuration of the Apache server is controlled by a text file called httpd.conf. On a Linux machine this is most likely found at /etc/httpd/conf/. On a Windows machine it is most likely found at C:/Program Files/Apache Group/Apache(2)/conf/. This file can be editted in any text editor. The easiest way to configure the Apache server to run GPM, is to change Apache's DocumentRoot directive to "C:/Program Files/Apache Group/Apache2/htdocs/thegpm" on Windows or "/var/www/thegpm/" on Linux.

We recommend you to use the Combined log format because the Common log format doesn't contain information about referrers and user agents (OS, browsers, spiders). By default Apache uses the Common log format but the majority of hosting providers set the Combined log format for Apache on their servers.

runs on Windows NT/9x, Netware 5.x and above, OS/2, and most versions of Unix, as well as several other operating systems DBM databases for authentication allows you to easily set up password-protected pages with enormous numbers of authorized users, without bogging down the server. Customized responses to errors and problems Allows you to set up files, or even CGI scripts, which are returned by the server in response to errors and problems, e.g.

Here is a link to 'how to' install a cert: that covers SGC SuperCert, SSL Web Server Certificate, and SSL123 Certificate:

Get SSLeay 0.8.0 or later from [ftp://ftp.psy.uq.oz.au/pub/Crypto/ SSL] ?? Build and test and install it! Get Apache SSLeay extensions from [ftp://ftp.ox.ac.uk/pub/crypto/SSL /] here Unpack it in the apache source directory and patch Apache as per the README. Configure and build it. You might also try [http://www.zedz.net] ZEDZ net which has many pre-built packages, and is located outside of the United States.

It is the parameter " register_long_arrays " which by default (in PHP5) is set to " Off ". It is enough to set it to " ON " and all functions (access to the administration, recognition at the time of the access to the site).

What is SSL? The SSL security protocol provides data encryption, server authentication, message integrity, and optional client authentication for a TCP/IP connection. Because SSL is built into all major browsers and web servers, simply installing a digital certificate turns on their SSL capabilities.

Yes, in general, starting Apache with a built-in mod_ssl is just like starting an unencumbered Apache, except for the fact that when you have a pass phrase on your SSL private key file. Then a startup dialog pops up asking you to enter the pass phrase. To type in the pass phrase manually when starting the server can be problematic, for instance when starting the server from the system boot scripts.

Yes. In general, starting Apache with mod_ssl built-in is just like starting Apache without it. However, if you have a passphrase on your SSL private key file, a startup dialog will pop up which asks you to enter the pass phrase. Having to manually enter the passphrase when starting the server can be problematic - for example, when starting the server from the system boot scripts. In this case, you can follow the steps below to remove the passphrase from your private key.

No additional configuration on the agent side is needed to run Maven 2 builds. A snapshot version of Maven 2.1 is distributed as an agent plugin (just like bundled Ant 1.6.5) pomLocation- the directory where the pom.xml file is located. In the example the "%build.working.dir%" macro is used, that is substituted with the real directory path on the concrete agent machine. Alternatevely, if there is a separate Maven 2.1.

Enable the ssl option in csoftadm and create a ~/ssl directory (with permissions of 0700). Move the certificate text file to ~/ssl/cert and the private key to ~/ssl/key. If your certificate requires a passphrase, you must place it in ~/ssl/pp. When you are done, send a request to technical support for opening the SSL port for your v-host address.

By default, Squid connects directly to origin servers for SSL requests. But if you must force SSL requests through a parent, first tell Squid it can not go direct for SSL: acl SSL method CONNECT never_direct allow SSL With this in place, Squid should pick one of your parents to use for SSL requests.

Also, if you see: SSL_Accept failed error:140760EB:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol in your error log, it's for the same reason.

configure --enable-shared=apache_ssl then enable the module in your httpd.conf: LoadModule apache_ssl_module modules/libssl.so gcc -c -I../os/unix -I../include -I/usr/local/ssl/include -funsigned-char -DTARGET=\"httpsd\" -DAPACHE_SSL '../apaci' -DAPACHE_SSL buff.c buff.c: In function 'ap_read': buff.c:259: structure has no member named 'stats' buff.c:267: structure has no member named 'stats' buff.c:268: structure has no member named 'stats' buff.

That's trivial: mod_ssl uses version strings of the syntax <mod_ssl-version>-<apache-version>, for instance 2.4.0-1.3.9. This directly indicates that it's mod_ssl version 2.4.0 for Apache version 1.3.9. And this also means you only can apply this mod_ssl version to exactly this Apache version (unless you use the --force option to mod_ssl's configure command ;-).

Make sure you add mod_ssl to the Apache source tree first and then do a fresh configuration and installation of PHP3. For SSL support EAPI patches are required which have to change internal Apache structures. PHP3 needs to know about these in order to work correctly. Always make sure that -DEAPI is contained in the compiler flags when PHP3 is built.