Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Dec 2017 09:09:39 +1100 (EST)
From:      Dave Horsfall <dave@horsfall.org>
To:        FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   Re: Procmail Vulnerabilities check
Message-ID:  <alpine.BSF.2.21.1712110904320.35694@aneurin.horsfall.org>
In-Reply-To: <EC0F9F41-4A57-4A8F-A7B4-67D954182DDA@adamw.org>
References:  <fb3d23c5-e32d-452a-a0c3-c3cb12340054@cloudzeeland.nl> <a66d1c33-e405-d9e8-d9c3-2738b5e66887@cloudzeeland.nl> <alpine.BSF.2.21.1712080956580.41281@wonkity.com> <20171208180905.GA96560@troutmask.apl.washington.edu> <alpine.BSF.2.21.1712091013310.35694@aneurin.horsfall.org> <20171209012522.GA42506@troutmask.apl.washington.edu> <alpine.BSF.2.21.1712091451300.35694@aneurin.horsfall.org> <fe88c5e6-155d-dd64-96d5-8f394c41d92f@FreeBSD.org> <20171210171122.GA48536@troutmask.apl.washington.edu> <EC0F9F41-4A57-4A8F-A7B4-67D954182DDA@adamw.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Dec 2017, Adam Weinberger wrote:

> DMA is a phenomenal program and is totally sufficient for a large 
> percentage of our user-base. I wasn’t aware of the lack of .forward 
> support, and I completely agree that that’s a very detrimental omission.

What about its spam filtering, such as /etc/mail/access and DNSBLs etc?

(I hope it's a coincidence that its name is also the same as the pro-spam 
Direct Marketing Association...)

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
From owner-freebsd-ports@freebsd.org  Sun Dec 10 22:26:01 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBE21E9F0A0
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sun, 10 Dec 2017 22:26:01 +0000 (UTC)
 (envelope-from mazhe@alkumuna.eu)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 71A8E65C35;
 Sun, 10 Dec 2017 22:26:01 +0000 (UTC)
 (envelope-from mazhe@alkumuna.eu)
Received: from yggdrasil.alkumuna.eu (unknown
 [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87])
 by smtp1-g21.free.fr (Postfix) with ESMTPS id 6A398B0053E;
 Sun, 10 Dec 2017 23:25:53 +0100 (CET)
Received: from gramr.alkumuna.eu
 ([IPv6:2a01:e35:8a74:6e70:62a4:4cff:fe54:b212])
 (authenticated bits=0)
 by yggdrasil.alkumuna.eu (8.15.2/8.15.2) with ESMTPSA id vBAMPpdB066845
 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT);
 Sun, 10 Dec 2017 23:25:52 +0100 (CET)
 (envelope-from mazhe@alkumuna.eu)
Date: Sun, 10 Dec 2017 23:25:50 +0100
From: Matthieu Volat <mazhe@alkumuna.eu>
To: Stefan Esser <se@freebsd.org>
Cc: Chris H <bsd-lists@BSDforge.com>, freebsd-ports@freebsd.org
Subject: Re: Working on FLAVOR support in portmaster
Message-ID: <20171210232550.27114ee0@gramr.alkumuna.eu>
In-Reply-To: <d041e1cc-b204-e2b4-ee0b-5d742b3787d1@freebsd.org>
References: <20171209102517.005de250@gramr.alkumuna.eu>
 <17c98bad038d40d023c8e1e3f93fe160@udns.ultimatedns.net>
 <20171210184716.604de089@gramr.alkumuna.eu>
 <d041e1cc-b204-e2b4-ee0b-5d742b3787d1@freebsd.org>
X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 boundary="Sig_/MEjG+AQpLSzmnQsVrBssiJh"; protocol="application/pgp-signature"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alkumuna.eu; s=default;
 t=1512944752; bh=NTPRTB8QRGQv98KNqmSng2n6jUNn9oSnBdhHlKbrKVA=;
 h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:MIME-Version:Content-Type;
 b=GEFWxATmzACFb12D1yityVYAaRKVJ27LF6JEnnahd839XlqvbZY/6WqHTvlj2GBhUJzQTP927sr/OHpzMGNFgfS6KFYzh8ktwtW/QUQMDbT6VPfJ1Ho7DIvkYQr+OER7uT+8RDyNhTA18WLuB1ID7TbYO/kaFWuhChZZrGv939E=
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>;
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Dec 2017 22:26:01 -0000

--Sig_/MEjG+AQpLSzmnQsVrBssiJh
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sun, 10 Dec 2017 22:33:25 +0100
Stefan Esser <se@freebsd.org> wrote:

> Am 10.12.17 um 18:47 schrieb Matthieu Volat:
> > They do... but only if you commit and push something (even if it's only
> > a personnal clone). If you just keep the changes on your computer, ther=
e's
> > nothing. =20
> The GitHub master version has changes, that are not yet in any release.

As someone involved in some projects, I do understand the differences betwe=
en working trees and releases, this was specifically about helping developp=
ement by being more communicative about it.

There's nothing in the commit tree (<https://github.com/freebsd/portmaster/=
commits/master>) nor the networkd (<https://github.com/freebsd/portmaster/n=
etwork>) as of now regarding this issue. I don't know for others, but this =
has led me to invest some time not knowing this was duplicate work.

>=20
> This is irrelevant as long as FLAVOR support is missing in portmaster,
> since there is no version that fully supports flavors, right now.

Please understand I am not asking for a working release, I'm asking for a m=
ore transparent developpement process that would allow other people to more=
 easily follow, familiarize themselves with and help in portmaster developm=
ent...

>=20
> > As much as I am defiant of github on certain aspects, I've found in qui=
te
> > some occasion the discussion/comment system around pull requests quite =
nice. =20
>=20
> I'm working in FLAVOR support and I have a version that correctly builds
> the Python ports, that have been converted.
>=20
> But I'm currently trying to understand, where the information that the
> ports is to be re-installed, gets lost. Debugging shell scripts is a lot
> of work, since you cannot single step through them. Portmaster does call
> itself recursively, which further complicates understanding and tracing
> the execution. (Besides, portmaster is a main program of 4300+ lines with
> functions sprinkled throughout the code. I have a local version, which
> breaks this large main program in named subroutines, which makes it much
> easier to understand the logic flow, but hides the actual changes when
> creating diffs. I have backported the FLAVOR changes to a portmaster
> version without those subroutines, to get the minimal functional patch,
> but now I'm fighting with the install vs. upgrade distinction being lost.)

You can however set the execution trace argument to produce a full log. I w=
as under the impression that when encountering package@flavor, splitting wa=
s needed in a few places to match the port directory and then simply add -D=
FLAVOR=3Dvalue to the MAKEFLAGS.

>=20
> I can send you the current version in private mail (I do not want to spam
> the mail-list with a 120k+ shell script).

This is exactly why I thought a WIP branch or something of the like would b=
e useful, unless you want to proceed alone without any feedback. But then a=
gain, I posted my own (naive) approach at the issue and it did not seems to=
 provoke any feedback, so maybe I was a bit too much hopeful.




--Sig_/MEjG+AQpLSzmnQsVrBssiJh
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE1xv/SVkem9252haa3yo2fFz8JX4FAlottG4ACgkQ3yo2fFz8
JX4BYQ//edBV91KVnMXH1LxxTUf5RzRwHbdLVUUImASTpWgi3uEHiMlDo6iGs74J
vzfNfrmlrzjiMzkkpTXndPzM9T/cWRcHY5q1DqFdEh2w5ZdhOna+GNO2rQ+jzVsb
dpyTzZ8vI1FKXAyVY32LlpTNxaBtybih7gBAZqJFnD+rr/ApUxvbRJr2lbwe3OBa
R4bHkdUpS7Ra74u0on3BLvALQwOpRewqJRtpzHJGEWd53oq44ud8qGKg8SXG6asr
f1/od9VMmWk1wFDK/VnJ7qfOt0nuVOx1DPavzSlVln5GcNJ5J47g9VbDP+I1N7wU
X/2JOXdwHp1UPq03FSnoU0Pkd3VSUnXCtvvCOIp2EGDxTyGywdPcbC+M7EKLOb45
Cf7Xnhf913kD3sM5I4oHv6VDigq4oUlbz4Q+1fED7v0GAbLkIPDbAuJTBBCm6IHQ
nI40U7DGhjCae5bPItJDzbcuTdFTiNcMUBtFGMT/ig4XLD9XIdodaAWGCWRyzNia
YYO+jSKom9TWf7wfsTb5gXM2ZzL1IpP1mfGreSpX0jInrFfdNJX4wrdSnEVqQt0B
7Gz2ktI/qmJWJeIu/dgrdcE1d2Vd6oICagPmy1loV526Gdbwrr2RsLywKokmcPtS
0vFI5HccTFMkUhBuAD6mFFc0vjqMR5JWViLocYTeQTebqdeDL4Q=
=rdYC
-----END PGP SIGNATURE-----

--Sig_/MEjG+AQpLSzmnQsVrBssiJh--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1712110904320.35694>