From: "Robin H. Johnson" <robbat2@gentoo.org>
To: Petre Rodan <petre.rodan@ravantivirus.com>
Cc: gentoo-dev@gentoo.org, "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: [gentoo-dev] qmail testing again
Date: Wed, 3 Sep 2003 02:29:15 -0700 [thread overview]
Message-ID: <20030903092915.GA5985@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <20030903065536.GA27869@peter.rav.local>
[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]
On Wed, Sep 03, 2003 at 09:55:36AM +0300, Petre Rodan wrote:
> I'm sorry to disturb you, but I couldn't help noticing that currently
> there are 15 patches to qmail, and this number has the tendency to
> rise with every ebuild.
I expect it to be around 20 when I'm done with the ebuild.
> I feel that DJ Bernstein did a great job creating the world's safest
> MTA. This is one of the main reasons sysadmins use it. My point is
> that even if there are reasons for upgrading the product (to add new
> features and such) the issues with not doing it are considerable and
> will likely out-weigh them.
DJB himself has mentioned that he uses some of the patches in some
cases, and just for the most part does not have time to contribute to
maintaining qmail anymore.
I have personally considered forking qmail in the past, simply to
go thru a validation of the security of the patches and distribute them
officially integrated. I simply do not have enough time to attempt this
until I am finished university, unless somebody is willing to sponsor me
to do it as some part-time work (I presently work part time at the
university to cover some of my tuition).
> The commotion generated by smtp-auth patch is an example.
SMTP AUTH (both directions) and STARTTLS both require more setup than
just emerging the package. If you don't set them up, then qmail behaves
in a functionally identical way to how it did before.
The security hole (bugtraq id 8196) is caused solely by
misconfiguration. I've put code into place (not yet committed to CVS) in
the startup scripts for qmail-smtpd that will detect the possible
misconfiguration and error out.
> Now please don't get me wrong, I appreciate your work, I simply fell
> in love with Gentoo but I think that those who would like to emerge
> qmail should have the choice of selecting the exact features that can
> make them happy. Simply masking versions doesn't sound to good, maybe
> some USE switches would ease the way. I'm wondering maybe
> qmail-1.03-x.ebuild can be made to inherit some patch related switches
> from a file that is system-specific.
I will definetly look at an optional flag to disable the majority of the
patches that could have security issues anyway.
--
Robin Hugh Johnson
E-Mail : robbat2@orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-09-03 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 0:32 [gentoo-dev] qmail testing again Robin H. Johnson
2003-09-03 6:55 ` Petre Rodan
2003-09-03 9:29 ` Robin H. Johnson [this message]
2003-09-04 11:49 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030903092915.GA5985@curie-int.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=petre.rodan@ravantivirus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox