Apache

刚刚想睡觉的时候收到了commit mail:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

clement     2004/05/28 08:27:02 PDT

  FreeBSD ports repository
  Modified files:
    www/apache2          Makefile 
  Added files:
    www/apache2/files    patch-modules:ssl:ssl_engine_kernel.c 
  Log:
  - Import security fix from Apache CVS...
  * modules/ssl/ssl_engine_kernel.c (ssl_hook_UserCheck): Fix buffer
  overflow in FakeBasicAuth code if client's subject DN exceeds 6K in
  length (CVE CAN-2004-0488); switch to using apr-util base64 encoder
  functions.
  - ... and of course bump PORTREVISION.
  
  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0488
  http://secunia.com/advisories/11534/
  
  Reported by:    Charles-Damien Orbello <tazma@cultdeadsheep.org>
  
  Revision  Changes    Path
  1.178     +1 -0      ports/www/apache2/Makefile
  1.1       +39 -0     ports/www/apache2/files/patch-modules:ssl:ssl_engine_kernel.c (new)

Some search engines has grabbed some of my links out (Primarily, MP3). So I put some limits there. This is because I don’t want FreeBSDChina to be a MP3 downloading site - It’s harmful for the server, and we don’t want it.

The code is the following, it’s simple and effective:

With help from clement@, I have finally addressed the problem I am encounting was caused by a mix of libkse(libpthread) and its older version.

As a result of recent changes on the Frontfree Reverse Proxy Server, the server signature has been changed from “Apache 2.0.48 on FreeBSD” to “IIS 6.0 on FreeBSD”.

I’m not concerned about the disclosure of what server I am using because it acts nothing when we call IIS a “Apache”, well, I think it’s silly to do things like that, but, well, a IIS running on FreeBSD is somewhat not normal on others’ sight.

Today I have committed several major changes to existing Frontfree Website System 2.0. This is a “major” change because it is the first time we have utilized Apache’s rewrite technology on reverse proxying, which, in other words, is an important change that the reverse proxying technology is going much more mature than it was first taken place.