On Wed, Jul 1, 2009 at 12:28 AM, Kenneth Gonsalves <law...@thenilgiris.com>wrote:
> > hi > > running django trunk. There was an smtp auth failure and since debug was on > there was a traceback. I notice in the traceback that the email username > and > password that are set in settings.py are disclosed. Is this a bug? Settings with PASSWORD in their name will get hidden in the actual settings display: http://docs.djangoproject.com/en/dev/ref/settings/#debug So if you're seeing the email password being displayed in the settings part of the debug page that would seem to be a bug -- but I can't recreate that. On my debug page that setting is hidden. I'm guessing, then, that you mean you could see the password in the traceback local arguments? I don't think that's a bug, as I don't think there's any attempt to hide/suppress "sensitive" information in the local variable data. (In general, how would the filtering code be able to identify what counts as "sensitive"?) If you happen to hit a case where a "sensitive" setting has been stashed in a local variable, it'll be visible on the DEBUG page. (DEBUG=True is really not meant for production.) Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
