can anyone point me to tips on xss attack avoidance under pylons? one of the measures i have running in mod_perl right now is a 'referer check' ( doesn't work against spoofed headers, but hey - it blocks out a surprising amount of attempts! ). what i do is lock-down the account and other writable directory ( /my/ , /service/my/ ) to call an error if the referer header isn't from the same domain/ip whitelist. I'm wondering if anyone has worked on similar functionality under pylons already
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
