hmm. yes, I think you're right. This is a general issue with how we store configs, but we may be able to fix it by inferring the storage key on the Conf object from the config definition block somehow.
can you open a ticket? --j. 2009/9/16 Karsten Bräckelmann <[email protected]>: > Found out the other day, that the VBounce whitelist_bounce_relays > settings are leaking between users. Tested on 3.2. > > Looking at the code and related bugs 6003 [1] and 4179 [2] it appears > this would still be an issue with trunk. Or so I assume, since I don't > really know what the proper fix would be. Hence poking here first to get > some opinions, before filing a bug. > > The recent fix for bug 6003 feels like a lot of foot-work adding each > and every user option. And is prone to break again. > > Moreover, looking at that list of options being defined empty, I wonder > if there actually are more issues lurking right around the corner. E.g. > ok_locales immediately comes to mind, which should be treated just like > the whitelist stuff in the fix for bug 6003, no? It isn't, so I'd assume > it is leaking, too. :/ > > Thoughts? > > > [1] https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6003 > [2] https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4179 > > -- > char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; > main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: > (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}} > > -- --j.
