=> Bootstrap dependency digest>=20010302: found digest-20210928 WARNING: [license.mk] Every package should define a LICENSE. => Checksum SHA1 OK for w3c-httpd-3.0A.tar.gz => Checksum RMD160 OK for w3c-httpd-3.0A.tar.gz => Checksum SHA512 OK for w3c-httpd-3.0A.tar.gz ===> Installing dependencies for w3c-httpd-3.0Anb1 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency cwrappers>=20150314: found cwrappers-20180325 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Overriding tools for w3c-httpd-3.0Anb1 ===> Extracting for w3c-httpd-3.0Anb1 cd /tmp/www/w3c-httpd/work/All && /bin/mkdir -p darwin && /bin/cp freebsd/Makefile.include darwin/ ===> Patching for w3c-httpd-3.0Anb1 => Applying pkgsrc patches for w3c-httpd-3.0Anb1 => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-aa => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.4 2006/10/07 22:39:28 schwarz Exp $ | |--- BUILD.orig 1994-09-24 20:28:46.000000000 +0200 |+++ BUILD 2006-10-07 22:21:25.000000000 +0200 -------------------------- Patching file BUILD using Plan A... Hunk #1 succeeded at 56. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ab => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ab Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.2 1999/05/09 21:12:33 tron Exp $ | |*** Library/Implementation/HTTCP.c.orig Mon Dec 30 12:20:05 1996 |--- Library/Implementation/HTTCP.c Mon Dec 30 13:23:20 1996 -------------------------- Patching file Library/Implementation/HTTCP.c using Plan A... Hunk #1 succeeded at 113. Hunk #2 succeeded at 124. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ac => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.1 1999/05/09 21:12:33 tron Exp $ | |--- All/netbsd/Makefile.include.orig Fri Jul 14 03:32:20 1995 |+++ All/netbsd/Makefile.include Sun May 9 23:01:01 1999 -------------------------- Patching file All/netbsd/Makefile.include using Plan A... Hunk #1 succeeded at 4. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ad => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.1 1999/05/10 13:56:54 bad Exp $ | |--- Daemon/Implementation/HTLog.c.org Mon Jul 1 02:07:23 1996 |+++ Daemon/Implementation/HTLog.c Mon May 10 15:40:29 1999 -------------------------- Patching file Daemon/Implementation/HTLog.c using Plan A... Hunk #1 succeeded at 425. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ae => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ae Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.1 2001/04/05 14:24:40 wiz Exp $ | |*** /dev/null Tue Feb 6 11:05:04 1996 |--- README-CACHE_CHECK_SIZE Tue Feb 6 13:27:32 1996 -------------------------- (Creating file README-CACHE_CHECK_SIZE...) Patching file README-CACHE_CHECK_SIZE using Plan A... Empty context always matches. Hunk #1 succeeded at 1. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** WWW/Daemon/Implementation/HTCache.c.orig Fri Aug 12 12:36:11 1994 |--- Daemon/Implementation/HTCache.c Mon Feb 5 14:02:11 1996 -------------------------- Patching file Daemon/Implementation/HTCache.c using Plan A... Hunk #1 succeeded at 382. Hunk #2 succeeded at 510. Hunk #3 succeeded at 550. Hunk #4 succeeded at 567. Hunk #5 succeeded at 591. Hunk #6 succeeded at 618. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-af => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-af Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-af,v 1.1 2001/04/05 14:24:40 wiz Exp $ | |*** /dev/null Tue Feb 6 11:05:04 1996 |--- README-CACHEDIRS Tue Feb 6 13:03:37 1996 -------------------------- (Creating file README-CACHEDIRS...) Patching file README-CACHEDIRS using Plan A... Empty context always matches. Hunk #1 succeeded at 1. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** WWW/Daemon/Implementation/HTCache.c.orig Fri Aug 12 12:36:11 1994 |--- Daemon/Implementation/HTCache.c Fri Sep 15 16:25:33 1995 -------------------------- Patching file Daemon/Implementation/HTCache.c using Plan A... Hunk #1 succeeded at 5. Hunk #2 succeeded at 246. Hunk #3 succeeded at 278. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ag => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ag Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ag,v 1.1 2001/04/05 14:24:40 wiz Exp $ | |============================================================================ |README: |============================================================================ | |OVERVIEW | | This SSL tunneling patch for CERN httpd adds support for the | CONNECT method used by SSL enhanced clients to open a secure | tunnel through the proxy. | |THEORY | | The CONNECT method takes | | hostname:port | | as its argument, and the request is in the form of the | HTTP/1.0 request (that is, the string "HTTP/1.0" and the | request headers must follow the request). Example: | | CONNECT home1.netscape.com:443 HTTP/1.0 | | | The response will be either a normal HTTP/1.0 error response | (in case the host is unreachable for one reason or another), | or in case of success: | | HTTP/1.0 200 Connection established | | | after which the connection is open, and the client may start | the SSL handshake. | | This is a superior approach because it allows the HTTP request | headers to be passed, making it possible to do authentication | on the proxy, and allows any other future extension. | |CONFIGURATION | | Because the configuration of CERN httpd is based on URL | patterns, for ease of configuration, the hostname:port | argument in automatically transformed into an internal | representation: | | connect://hostname:port | | connect:// URLs do not exist in real life -- this is just a | notion in the configuration file to make life easier!! | |ENABLING | | SSL tunneling is disabled by default. To enable it for HTTPS | (uses the port 443), add the following line in the | configuration file: | | Pass connect://*:443 | | To enable secure news (SNEWS, uses port 563) tunneling, add | line: | | Pass connect://*:563 | | DO NOT use trailing slashes. DO NOT allow all connect:// | requests, the following is unsafe: | | Pass connect://* | |PROTECTION | | IP address protection should always be used in connection with | SSL tunneling. To create a protection template P which allows | access only for hosts with IP addresses 198.93.*.* and | 198.95.*.*, use the template: | | Protection P { | CONNECT-Mask @(198.93.*.*, 198.95.*.*) | } | | Note that this only declares a template; to actually apply the | protection use the Protect rule, AFTER the Protection | declaration, but BEFORE the Pass rule: | | Protect connect://* P | | Or, to collect them all together: | | Protection P { | CONNECT-Mask @(198.93.*.*, 198.95.*.*) | } | Protect connect://* P | Pass connect://*:443 | Pass connect://*:563 | | The Protection binding to name P may be left out in case it's | only used once, and the protection configuration may be | inlined in place of the protection name in Protect rule: | | Protect connect://* { | CONNECT-Mask @(198.93.*.*, 198.95.*.*) | } | Pass connect://*:443 | Pass connect://*:563 | | For a better insight of the CERN httpd's configuration system, | please refer to the online manual: | | http://www.w3.org/httpd/ | |PROXY AUTHENTICATION | | This patch does not enable proxy authentication. Proxy | authentication is not supported by the CERN proxy. Proxy | authentication uses the status code 407, and headers | Proxy-Authenticate and Proxy-Authorization. | | You MUST NOT try to use the Protect directive to turn on | normal user authentication on (the one that uses the 401 | status code, and WWW-Authenticate and Authorization headers). | That is an incorrect way to do authentication for the proxy, | and causes compatibility and security problems. | |CHAINING PROXIES | | This patch does not enable chaining proxies to do SSL | tunneling. More specifically, the CERN proxy with this patch | IS able to act as the OUTMOST proxy in the chain, but it | doesn't work if it is the inner proxy that has to speak to | another, outer proxy to establish a secure connection through | that. Therefore, a combination such as inner Netscape Proxy | and outer CERN httpd would work, but not vice versa. | |THE NETSCAPE PROXY SERVER | | The Netscape Proxy Server is a commercially supported proxy | server available from Netscape Communications Corporation. In | addition to it's unique, more efficient architecture, it | natively supports proxy authentication, proxy chaining, SSL | tunneling and HTTPS proxying, enabling also clients without | native SSL support to use HTTPS. | |AUTHOR | Ari Luotonen, Netscape Communications Corporation, 1995 | | |DISCLAIMER | | I do not have any official connection to the CERN httpd | development anymore. I have left the CERN WWW project in | summer '94. I do not provide any support for this software or | this patch. For general CERN httpd support, please contact: | | httpd@w3.org | | THIS PATCH IS PROVIDED IN GOOD FAITH, AS IS. I AND NETSCAPE | MAKE NO CLAIMS TO ITS SUITABILITY FOR ANY PARTICULAR PURPOSE, | AND I AND NETSCAPE PROVIDE ABSOLUTELY NO WARRANTY OF ANY KIND | WITH RESPECT TO THIS PATCH OR THIS SOFTWARE. THE ENTIRE RISK | AS TO THE QUALITY AND PERFORMANCE OF THIS SOFTWARE/PATCH IS | WITH THE USER. IN NO EVENT WILL I OR NETSCAPE BE LIABLE TO | ANYONE FOR ANY DAMAGES ARISING OUT THE USE OF THIS | SOFTWARE/PATCH, INCLUDING, WITHOUT LIMITATION, DAMAGES | RESULTING FROM LOST DATA OR LOST PROFITS, OR FOR ANY SPECIAL, | INCIDENTAL OR CONSEQUENTIAL DAMAGES. | | |============================================================================ |PATCH TO WWW COMMON LIBRARY 2.17 AND CERN HTTPD 3.0: |============================================================================ | |*** Library/Implementation/HTAccess.c.orig Thu Sep 29 04:53:28 1994 |--- Library/Implementation/HTAccess.c Tue May 9 13:16:50 1995 -------------------------- Patching file Library/Implementation/HTAccess.c using Plan A... Hunk #1 succeeded at 146. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** Library/Implementation/HTAccess.h.orig Sun Sep 25 07:15:14 1994 |--- Library/Implementation/HTAccess.h Tue May 9 13:15:47 1995 -------------------------- Patching file Library/Implementation/HTAccess.h using Plan A... Hunk #1 succeeded at 60. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** Daemon/Implementation/HTAAProt.h.orig Sun Sep 25 06:55:47 1994 |--- Daemon/Implementation/HTAAProt.h Mon May 15 21:05:40 1995 -------------------------- Patching file Daemon/Implementation/HTAAProt.h using Plan A... Hunk #1 succeeded at 50 (offset -2 lines). Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** Daemon/Implementation/HTAAProt.c.orig Sun Sep 25 11:53:03 1994 |--- Daemon/Implementation/HTAAProt.c Mon May 15 21:18:05 1995 -------------------------- Patching file Daemon/Implementation/HTAAProt.c using Plan A... Hunk #1 succeeded at 356. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** Daemon/Implementation/HTAAServ.c.orig Sun Sep 25 06:52:53 1994 |--- Daemon/Implementation/HTAAServ.c Mon May 15 21:06:18 1995 -------------------------- Patching file Daemon/Implementation/HTAAServ.c using Plan A... Hunk #1 succeeded at 212 (offset 4 lines). Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** Daemon/Implementation/HTRequest.c.orig Fri Aug 12 03:36:29 1994 |--- Daemon/Implementation/HTRequest.c Mon May 15 21:32:44 1995 -------------------------- Patching file Daemon/Implementation/HTRequest.c using Plan A... Hunk #1 succeeded at 1022 (offset 16 lines). Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------- |*** Daemon/Implementation/HTDaemon.c.orig Mon Sep 26 07:23:00 1994 |--- Daemon/Implementation/HTDaemon.c Mon Jun 12 15:58:58 1995 -------------------------- Patching file Daemon/Implementation/HTDaemon.c using Plan A... Hunk #1 succeeded at 65. Hunk #2 succeeded at 164 (offset 1 line). Hunk #3 succeeded at 383 (offset 1 line). Hunk #4 succeeded at 2101 (offset 48 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ah => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ah Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ah,v 1.1 2006/10/07 22:39:28 schwarz Exp $ | |--- ./Library/Implementation/tcp.h.orig 2006-10-07 22:59:41.000000000 +0200 |+++ ./Library/Implementation/tcp.h 2006-10-07 23:00:26.000000000 +0200 -------------------------- Patching file ./Library/Implementation/tcp.h using Plan A... Hunk #1 succeeded at 722. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ai => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ai Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ai,v 1.1 2006/10/07 22:39:28 schwarz Exp $ | |--- Makefile.orig 2006-10-07 23:37:17.000000000 +0200 |+++ Makefile 2006-10-07 23:37:32.000000000 +0200 -------------------------- Patching file Makefile using Plan A... Hunk #1 succeeded at 4. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ba => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ba Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ba,v 1.2 1999/05/09 21:12:33 tron Exp $ | |*** Daemon/Implementation/CommonMakefile.orig Mon Dec 30 17:25:30 1996 |--- Daemon/Implementation/CommonMakefile Mon Dec 30 17:27:26 1996 -------------------------- Patching file Daemon/Implementation/CommonMakefile using Plan A... Hunk #1 succeeded at 35. Hunk #2 succeeded at 157. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-bb => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-bb Hmm... Looks like a new-style context diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-bb,v 1.2 1999/05/09 21:12:33 tron Exp $ | |*** All/freebsd/Makefile.include.orig Mon Dec 30 17:18:49 1996 |--- All/freebsd/Makefile.include Mon Dec 30 17:19:46 1996 -------------------------- Patching file All/freebsd/Makefile.include using Plan A... Hunk #1 succeeded at 5. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-bc => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-bc Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-bc,v 1.2 1999/05/09 21:12:33 tron Exp $ | |--- Daemon/Implementation/HTPasswd.c.orig Sun Sep 25 06:48:03 1994 |+++ Daemon/Implementation/HTPasswd.c Sat Mar 8 10:02:19 1997 -------------------------- Patching file Daemon/Implementation/HTPasswd.c using Plan A... Hunk #1 succeeded at 77. Hunk #2 succeeded at 102. Hunk #3 succeeded at 140. Hunk #4 succeeded at 166. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ca => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-ca Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ca,v 1.2 1999/05/09 21:12:33 tron Exp $ | |--- Daemon/Implementation/CGIParse.c.orig Wed Jun 3 12:38:15 1998 |+++ Daemon/Implementation/CGIParse.c Wed Jun 3 12:38:41 1998 -------------------------- Patching file Daemon/Implementation/CGIParse.c using Plan A... Hunk #1 succeeded at 293. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-cb => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/w3c-httpd/patches/patch-cb Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-cb,v 1.1 2006/11/02 18:59:36 rillig Exp $ | |What does that code want to say me? I'm confused. | |--- BUILD.SH.orig 1994-09-23 14:12:52.000000000 +0200 |+++ BUILD.SH 2006-11-02 19:55:14.000000000 +0100 -------------------------- Patching file BUILD.SH using Plan A... Hunk #1 succeeded at 18. done ===> Creating toolchain wrappers for w3c-httpd-3.0Anb1 ===> Configuring for w3c-httpd-3.0Anb1 => Substituting "strcasestr" in Daemon/Implementation/HTWild.c Library/Implementation/HTString.c Library/Implementation/HTString.h Defaulting to DES encrypted passwords. Set the environment variable MD5_PW if you want MD5 encrypted passwords. => Checking for portability problems in extracted files