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.

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.

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 ;-).

By using the ulimit command in bash, the limit command in tcsh, or the rlimit command in ksh. See the appropriate manual page for details. If you wish to enable or disable core dumping for all processes by default, you can change the default setting in linux/sched.h. Refer to definition of INIT_TASK, and look also in linux/resource.h. PAM support optimizes the system's environment, including the amount of memory a user is allowed.

In Apache version 1.2, the error log message about dumped core includes the directory where the dump file should be located. However, many Unixes do not allow a process that has called setuid() to dump core for security reasons; the typical Apache setup has the server started as root to bind to port 80, after which it changes UIDs to a non-privileged user to serve requests. Dealing with this is extremely operating system-specific, and may require rebuilding your system kernel.

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.

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.

In theory, yes. A DCMES element specified with an element qualifier is, effectively, a "new" element or property- with a more specialized meaning than its parent element. However, it is not possible to create a new Dublin Core element whose meaning goes beyond the scope of of the original elements in the DCMES. It is expected that local or application-specific requirements may require additional qualifiers or elements that have not been approved by the Dublin Core community at large.

Several very good ones already exist, for instance the JGMOD or DUMB packages. See the audio library extensions section on the Allegro.cc website (http://www.allegro.cc/). You are not allowed to suggest that one of these libraries be merged into Allegro, because this topic has already been done to death on the mailing list and we are tired of it.

IIS Mod-Rewrite is compatible with apache mod_rewrite both in syntax and functionality. This means that a rewrite configuration for Apache is not only accepted by IIS Mod-Rewrite, but it also behaves the way Apache mod_rewrite does. However, some of the functions available in apache mod_rewrite are not implemented in IIS Mod-Rewrite, simply because IIS and Apache have completely different design and those functions are meaningless for IIS.

A compiled mod_jk for linux can be found at http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/bin/linux/i386/ , documentation at http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/mod_jk-howto.html No, mod_jk and mod_jserv are not compatible (cannot be installed in the same instance of Apache). When transitioning, I've used mod_jserv for both Tomcat and JServ instances with different ports.

Check to see if a structure type declaration just before main() is missing its trailing semicolon, causing main() to be declared as returning a structure. See also questions 10.9 and 16.4.

A missing semicolon causes the compiler to believe that main returns a structure.  (The connection is hard to see because of the intervening comment.)  Since struct-valued functions are usually implemented by adding a hidden return pointer, the generated code for main() tries to accept three arguments, although only two are passed (in this case, by the C start-up code).  See also question 17.21.

Since it's hard to tell from a stack trace only, what is going wrong, please send as much information as possible. If you're lucky, you're the writer of the service and you can send the component implementation code and the code which instantiates the object as well. If you are not the component developer then you're forced to contact the component developer.

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

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.

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.

The mod_ssl v1 package was initially created in April 1998 by Ralf S. Engelschall via porting Ben Laurie's Apache-SSL 1.17 source patches for Apache 1.2.6 to Apache 1.3b6. Because of conflicts with Ben Laurie's development cycle it then was re-assembled from scratch for Apache 1.3.0 by merging the old mod_ssl 1.x with the newer Apache-SSL 1.18. From this point on mod_ssl lived its own life as mod_ssl v2. The first publicly released version was mod_ssl 2.0.0 from August 10th, 1998.

First, let us explain what Wassenaar and its Arrangement on Export Controls for Conventional Arms and Dual-Use Goods and Technologies is: This is a international regime, established 1995, to control trade in conventional arms and dual-use goods and technology. It replaced the previous CoCom regime.

On this page you will see two boxes. In the first box to the left, enter the extension(s) which will be added to the new handler. Once you have done so, in the box across from it enter the actual handler that you will be adding. Now that you have entered the required information, click on the button labeled as Add. This will take you to a new page telling you that the new handler has been added.

Apache JServ is the right name. Please, avoid the use of other denominations because "JServ" is a registered trademark we don't own and "mod_jserv" is somehow misleading since it should be used to refer only to the Apache module used to communicate with Apache JServ. We know this sucks but there are some claims in Sun's license that simply don't fit with our open source model because we may get sued for problems found in their code even if we didn't touch it.

Usually just all SSL ciphers which are supported by the version of OpenSSL in use (can depend on the way you built OpenSSL). Typically this at least includes the following: In order to use Anonymous Diffie-Hellman (ADH) ciphers, it is not enough to just put ''ADH'' into your SSLCipherSuite. Additionally you have to build OpenSSL with ''-DSSL_ALLOW_ADH''. Because per default OpenSSL does not allow ADH ciphers for security reasons.