9 msgMaximum length of a header line?
3 msgDelay splitted in logfile
4 msgCustomize the 221 Bye message
1 msgPostfix snapshot 20070724
8 msgrelay access denied
5 msgspamcop link to my website in signature leads t...
13 msgMessage size limit per user
4 msgchaining aliases failing?
5 msgmisdelivery of mail to user@virtual to user@domain
2 msgVacation Message - request for comment on imple...

Possible DoS when the adress and the virtual my...
\ Horváth Róbert (24 Jul 2007)
. \ (Wietse Venema) (24 Jul 2007)
. \ Leandro Santi (24 Jul 2007)
. \ steeeeeveee (24 Jul 2007)
. . \ (Wietse Venema) (24 Jul 2007)
. . . \ Victor Duchovni (24 Jul 2007)
. . . . \ steeeeeveee (24 Jul 2007)
. . . . . \ Victor Duchovni (24 Jul 2007)
. . . . . . \ steeeeeveee (24 Jul 2007)
. . . . \ Leandro Santi (24 Jul 2007)

1 msgPostfix + Dovecot + Procmail
7 msg2 instances of smtpd in master.cf
2 msgdiskless client with link to servers mailqueue
4 msgAuthentication: how does it work?
1 msguupth or pathto in Postfix
3 msgSASL and NIS errors
1 msgpostfix sqlite ??
2 msgProblem authenticating postfix users with cyrus...
19 msgsender address verification vs. script-generate...
Subject:Re: Possible DoS when the adress and the virtual mysql transport table's characterset mismatches?
Group:Postfix-users
From:steeeeeveee
Date:24 Jul 2007


 

-------- Original-Nachricht --------
Datum: Tue, 24 Jul 2007 16:33:12 -0400
Von: Victor Duchovni <Victor.Duchovni>
An: steeeeeveee
CC: postfix-users
Betreff: Re: Possible DoS when the adress and the virtual mysql transport table\'s characterset mismatches?

> On Tue, Jul 24, 2007 at 10:25:32PM +0200, steeeeeveee wrote:
>
> > -------- Original-Nachricht --------
> > Datum: Tue, 24 Jul 2007 16:19:59 -0400
> > Von: Victor Duchovni <Victor.Duchovni>
> > An: Postfix users <postfix-users>
> > Betreff: Re: Possible DoS when the adress and the virtual mysql
> transport table\'s characterset mismatches?
> >
> > > On Tue, Jul 24, 2007 at 04:14:48PM -0400, Wietse Venema wrote:
> > >
> > > > > query = SELECT transport FROM domain WHERE
> > > CONVERT(domain USING utf8)=CONVERT(_latin1'%s' USING utf8) AND
> backupmx='0' AND
> > > active='1'
> > >
> > > Looks like a table scan if the 'domain' attribute is not already utf8.
> > > Otherwise converting from LATIN1 to utf8 for comparison looks
> perfectly
> > > reasonable if it is in fact necessary.
> > >
> > In my case domain is (or should) already be in UTF8. So the first
> convert is not really needed. But I had so much bad experience with MySQL and PHP
> that I did not wanted to risk anything. So I force the convert.
>
> If the optimizer is not overly clever, it will not use an index for
> columns that are inputs to functions (like CONVERT), so you should
> probably drop redundant conversions if they are NOPs. Of course if your
> table is small enough, and traffic rates are modest, table scans may
> be acceptable.
>
The MySQL optimizer is not that clever. As soon as you use a CONVERT it will do a full table scan for the converted field. Without the CONVERT the query would use the index. Even if I force the usage of the index MySQL will still do the table scan.
I personally have no problems with MySQL doing the table scan. I prefer to catch problems with the convert then having Postfix to suffer from character/collation conversation problems with MySQL.


> --
> Viktor.
>
// Steve


> Disclaimer: off-list followups get on-list replies or get ignored.
> Please do not ignore the "Reply-To" header.
>
> To unsubscribe from the postfix-users list, visit
> http://www.postfix.org/lists.html or click the link below:
> <mailto:majordomo?body=unsubscribe%20postfix-users>
>
> If my response solves your problem, the best way to thank me is to not
> send an "it worked, thanks" follow-up. If you must respond, please put
> "It worked, thanks" in the "Subject" so I can delete these quickly.

--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


© 2004-2008 readlist.com