From owner-freebsd-ports@FreeBSD.ORG Tue Aug 7 13:56:41 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BD0B16A417 for ; Tue, 7 Aug 2007 13:56:41 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by mx1.freebsd.org (Postfix) with ESMTP id 0491713C458 for ; Tue, 7 Aug 2007 13:56:40 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so1978991fka for ; Tue, 07 Aug 2007 06:56:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qIzQV9HawFt82LzD7BPaVEpK7feNdj5gCSLZis/8IBWFhxIRDp4/lA8ZF979IYgrjkY6wKkq000RPEMtwAWV2d1WCDHcdFrXhaP0ZkgW2kbiEZehc2giduxrEmhs5kd6BwRhoD/fhLX7ywDX2wI/FW1+P8AZF8x5igwmbCg2uFY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CnMeLba3Mysze0seQihGZOYULa+dPHT4Czc5atYD2fgp2BfcYjhJ9QkTMTeRUWmrEORLJh/jo20mY2CqFe7qu/TMW4uTCWB1jCi4zXRuNC1rzwDEE8RXmX5bEExgtomWF/s0M6DKh8JdSwAzJT+1LlWXYu/V7OhQgWP2d5ZWqNk= Received: by 10.86.65.11 with SMTP id n11mr5222089fga.1186494999259; Tue, 07 Aug 2007 06:56:39 -0700 (PDT) Received: by 10.86.71.6 with HTTP; Tue, 7 Aug 2007 06:56:39 -0700 (PDT) Message-ID: <790a9fff0708070656j77bc1f82l6c267df10e65cdfc@mail.gmail.com> Date: Tue, 7 Aug 2007 08:56:39 -0500 From: "Scot Hetzel" To: "Rakhesh Sasidharan" In-Reply-To: <20070807160649.Y22638@obelix.home.rakhesh.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070807160649.Y22638@obelix.home.rakhesh.com> Cc: freebsd-ports@freebsd.org Subject: Re: Building Pine with PASSFILE option X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2007 13:56:41 -0000 On 8/7/07, Rakhesh Sasidharan wrote: > I understand one can compile the email client Pine with an option > PASSFILE= to enable the option of saving your mail account > passwords. The Pine website talks about it and so do many sites all over > the net. > > FreeBSD's ports do not seem to offer such an option. I went through the > Pine Makefile, however, and I see that the "EXTRA_OPTS" variable is what's > used to compile Pine with extra configurable options. > > So my question is this: if I want to compile Pine from ports with this > PASSFILE option, can I do something like the following in > /usr/ports/mail/pine4? > > # make EXTRA_OPTS+=PASSFILE=.pine.pwd install > This won't work from the command line. > I used the "+=" coz I got the got the impression that adds onto the > existing extra options. And if I want to make this permanent, can I define > it in /etc/make.conf accordingly? > > .if ${.CURDIR:M*/mail/pine4} > EXTRA_OPTS+= PASSFILE=.pine.pwd > .endif > But it will work from /etc/make.conf (using either "=" or "+="), as long as you don't select LDAP support. A better way to add support for PASSFILE, would be to add: PASSFILE "Add support for a Pine Password File (DANGEROUS)" off to the list of options, then add the following below .if defined(WITH_IPV6) ... .endif: .if defined(WITH_PASSFILE) EXTRA_OPTS+= PASSFILE=.pine.pwd .endif You would then need to add a warning when this option is enabled, as according to doc/tech-notes.txt this option is dangerous: PASSFILE _WARNING!_ Turning this on is very dangerous and should probably not be done, except on single user systems! For : _WARNING_! Use this feature with caution! It effectively makes the user's mail no more secure than the physical security of the machine running _Pine_. What's more, while the password is cloaked by a mild (some might say, feeble) encryption scheme, it is nonetheless sitting in a file on the disk and subject to cracking by anyone with access to it. _BEWARE_! After you make these changes and test them, submit the change using send-pr for inclusion to the pine4 port. The maintainer will then make the decision if this change is appropriate for the ports. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.