Michael Parker wrote:
On Fri, Dec 17, 2004 at 05:00:14PM -0600, Stuart Johnston wrote:
Yes, quite. I double checked just to be sure and I notice that the
'debug: plugin' line comes after the user_prefs is loaded even if it is
loaded by init.pre. Never the less, if I remove the loadplugin line
On Fri, Dec 17, 2004 at 05:00:14PM -0600, Stuart Johnston wrote:
>
> Yes, quite. I double checked just to be sure and I notice that the
> 'debug: plugin' line comes after the user_prefs is loaded even if it is
> loaded by init.pre. Never the less, if I remove the loadplugin line
> from init.p
Michael Parker wrote:
On Fri, Dec 17, 2004 at 04:41:01PM -0600, Stuart Johnston wrote:
I certainly don't disagree with the security problems with allowing
users to load plugins. The problem is that in fact, user_conf CAN load
a plugin and does quite certainly execute its code, despite what the
On Fri, Dec 17, 2004 at 04:41:01PM -0600, Stuart Johnston wrote:
>
> I certainly don't disagree with the security problems with allowing
> users to load plugins. The problem is that in fact, user_conf CAN load
> a plugin and does quite certainly execute its code, despite what the
> documentati
Matt Kettler wrote:
At 05:04 PM 12/17/2004, Stuart Johnston wrote:
I have been having a difficult time getting URIDNSBL to work and I
finally figured out why. I was trying to do the loadplugin in a
user_prefs file in order to test out a new configuration.
The problem is that the builtin plugins
At 05:04 PM 12/17/2004, Stuart Johnston wrote:
I have been having a difficult time getting URIDNSBL to work and I finally
figured out why. I was trying to do the loadplugin in a user_prefs file
in order to test out a new configuration.
The problem is that the builtin plugins can not be enabled
