From owner-freebsd-ports@FreeBSD.ORG Wed Apr 6 12:25:06 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D41316A4CE for ; Wed, 6 Apr 2005 12:25:06 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0481D43D55 for ; Wed, 6 Apr 2005 12:25:05 +0000 (GMT) (envelope-from Shane@007Marketing.com) Received: from [192.168.8.50] (ppp19-170.static.internode.on.net [150.101.19.170])j36CP2cx015007 for ; Wed, 6 Apr 2005 21:55:03 +0930 (CST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Wed, 06 Apr 2005 21:54:54 +0930 From: Shane Ambler To: FreeBSD Mailing Lists Message-ID: In-Reply-To: <20050406203052.C9CD.REES@ddcom.co.jp> Mime-version: 1.0 Content-type: text/plain; charset="ISO-2022-JP" Content-transfer-encoding: 7bit Subject: Re: mod_tsa anyone? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2005 12:25:06 -0000 You can find openssl in /usr/ports/security/openssl Not sure what version shipped with the last release but if you use cvsup to update your ports tree (appendix A of the handbook) you will get 0.9.7f You will find the ports install it into /usr/local/bin/openssl whereas the system installs it into /usr/bin/openssl - you need to specify the /usr/local version when you make your mod_tsa. On 6/4/05 9:01 PM, "Joel" wrote: > I babbled: > >> In the archives, I found that the usual approach for combining modssl >> with something else is to get the apache+modssl port, then get the other >> mod ports. (Dynamic loading.) >> >> Now, over at opentsa.org, they say they have reports of successful >> installs on freebsd. But I don't have enough experience with ports to >> know what I'm doing, so I'm wondering where I should put those mod_tsa >> patch files, and what flags I should set in which configuration files. >> >> Maybe if I figure out where the sources went when I did the make in >> /usr/ports/www/apache13-modssl, I can figure out the instructions for >> mod_tsa. If I can successfully apply the patches, what's the next step? >> Will a repeat make walk on the patches? >> >> Now I see a reminder about certificates, and that reminds me of my >> second question. >> >> mod_tsa for apache 1.3.33 requires openssl 0.9.7e, and the version in >> freeBSD is 0.9.7d . >> >> I tried, just for grins, running over to /usr/src/secure/usr.bin/openssl >> and doing a make, but the results didn't really give me any clues. I >> didn't see anything in the Makefile there that I could recognize as >> being intended to tell the make process to update openssl. And I don't >> see any evidence yet of the source files for openssl. > > Tomorrow, first thing when I get to work, I'm going to try untarring the > mod_tsa patches for mod_ssl into the ports/www/apache13-modssl/files > directory and running make. As long as I don't do make install, I can > always make clean and try again, right? > > I think I'll clone apache13-modssl into my home directory first, though. > > -- > Joel Rees > digitcom, inc. 株式会社デジコム > Kobe, Japan +81-78-672-8800 > ** ** > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- Shane Ambler Sales Department 007Marketing.com Shane@007Marketing.com