Re: [Catalyst] improving usability / doc

2007-08-17 Thread Adam Bartosik
How many people decided to take different framework just because catalyst doc still sucks? Sucks is somewhat hurtful to the many contributers, but whatever, I see what you mean. Thanks - it is just what I think when I see flexibility of Catalyst compared eg. to Rails

Re: [Catalyst] improving usability / doc

2007-08-17 Thread Anthony Gardner
I'll be happy to help out. Will be working on 3 C projects in the near future and will need to re-read the docs so helping with tarting them up will help my learning. Am on holiday for the next three weeks and will unsubscribe from the mailing list today but I'll re-subscribe and check the

Re: [Catalyst] improving usability / doc

2007-08-17 Thread Matt S Trout
On Thu, Aug 16, 2007 at 05:06:10PM +0200, Adam Bartosik wrote: I wonder how much better Catalyst doc would looks if the top doc page, http://search.cpan.org/dist/Catalyst-Manual/ (linked from top catalyst page) had tutos in 1..9 order, not alphabetical? Is such change in naming eg:

Re: [Catalyst] improving usability / doc

2007-08-17 Thread Carl Franks
On 17/08/07, Jonathan Rockway [EMAIL PROTECTED] wrote: Sucks is somewhat hurtful to the many contributers... ... (search.cpan.org's navigation sucks). hmm? ;) ___ List: Catalyst@lists.rawmode.org Listinfo:

Re: [Catalyst] improving usability / doc

2007-08-17 Thread Daniel McBrearty
the thing that I have found confusing in the past is the fact that if you go here: http://search.cpan.org/~mramberg/Catalyst-Runtime-5.7008/ which appears to be the root node of things, then scroll down for documentation, you find this:

Re: [Catalyst] improving usability / doc

2007-08-17 Thread Geir Aalberg
Carl Franks wrote: On 17/08/07, Jonathan Rockway [EMAIL PROTECTED] wrote: Sucks is somewhat hurtful to the many contributers... ... (search.cpan.org's navigation sucks). hmm? By their own admission. How many years have we been told that there will be better navigation features and such

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Carl Johnstone
Anyone doing something like this already? Suggestions? Caveats? You'll almost certainly have to log it per-IP address rather than an a cookie or session or anything like that. Any real password-cracking bot is unlikely to honour your cookies or session identifiers. Which in return means

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Bill Moseley
On Fri, Aug 17, 2007 at 03:56:23PM +0100, Carl Johnstone wrote: Anyone doing something like this already? Suggestions? Caveats? You'll almost certainly have to log it per-IP address rather than an a cookie or session or anything like that. Any real password-cracking bot is unlikely to

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Wade . Stuart
Bill Moseley [EMAIL PROTECTED] wrote on 08/17/2007 10:32:36 AM: On Fri, Aug 17, 2007 at 03:56:23PM +0100, Carl Johnstone wrote: Anyone doing something like this already? Suggestions? Caveats? You'll almost certainly have to log it per-IP address rather than an a cookie or

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Carl Johnstone
Well, that would be every environment where Catalyst runs. If you want to do something fancy, I'd suggest looking at lingerd, a C daemon written to take TCP connections handed off from mod_perl. It would require some C-level hacking, but I expect you could alter it for this purpose. Lingerd

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Carl Johnstone
Also considered issuing a redirect to a simple server that will delay the number of failed attempts seconds before redirecting back to the login page. Any smart attacker would get clued about this an not follow that redirect. Fun anyways, though. ;) As I just said in the other

[Catalyst] Template directive failing?

2007-08-17 Thread Michael Higgins
New problem with my code: Error message is: Couldn't render template file error - shipments/form_create_do: not found action = shipments/form_create_do and in my Shipments.pm sub form_create_do : Local { # Set the TT template to use $c-stash-{template} =

[Catalyst] Re: Template directive failing? [ solved ]

2007-08-17 Thread Michael Higgins
On Fri, 17 Aug 2007 10:40:11 -0700 Michael Higgins [EMAIL PROTECTED] wrote: New problem with my code: [8] In all the other controllers, this syntax seems to be working _just fine_. I must be missing something very basic. Any thoughts? I'm lost on how to track this one down. :( Restarted

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Bill Moseley
On Fri, Aug 17, 2007 at 11:49:42AM -0400, Perrin Harkins wrote: On 8/17/07, Carl Johnstone [EMAIL PROTECTED] wrote: You'll almost certainly have to log it per-IP address rather than an a cookie or session or anything like that. Any real password-cracking bot is unlikely to honour your

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Jason Kohles
On Aug 17, 2007, at 10:56 AM, Carl Johnstone wrote: Anyone doing something like this already? Suggestions? Caveats? You'll almost certainly have to log it per-IP address rather than an a cookie or session or anything like that. Any real password- cracking bot is unlikely to honour your

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Perrin Harkins
On 8/17/07, Bill Moseley [EMAIL PROTECTED] wrote: I missed something along the way in this thread. Cookies? Is that to block a specific client? Yes, as opposed to an IP that could be a proxy. I'm just thinking of blocking specific logins when too many failed logins are attempted. That

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Bill Moseley
On Fri, Aug 17, 2007 at 02:12:21PM -0400, Jason Kohles wrote: Instead of delaying the response, one possibility is to send a complete response without a login form, just a note that says 'too many attempts, try again in X seconds', possibly with a refresh to reload the page once the

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Christian Storm
I like the idea of the captcha after a few failed requests. Although, if it's a real person having problems logging in then the addition of the captcha just make it that much more likely that they will not be able to login. Kind of amazing how often I fail the captcha. Plus, captcha's are not

Re: [Catalyst] improving usability / doc

2007-08-17 Thread Kieren Diment
I've made an attempt to fix this for the next minor release. It relies on pulling the wool over the cpan indexers eyes, so we'll have to wait and see if it works for sure. On 17/08/07, Daniel McBrearty [EMAIL PROTECTED] wrote: the thing that I have found confusing in the past is the fact that

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Bill Moseley
On Fri, Aug 17, 2007 at 02:33:21PM -0400, Perrin Harkins wrote: I'm just thinking of blocking specific logins when too many failed logins are attempted. That works if they keep hitting the same login with different passwords. Are you concerned about them trying many logins with a common

Re: [Catalyst] Rate limiting password attacks

2007-08-17 Thread Jonathan Rockway
Bill Moseley wrote: What's the status of the Cache plugin(s) wrt. backends? I want to be able to swap between FastMmap and Memcached via a config option As per the docs: # configure a backend or use a store plugin __PACKAGE__-config-{cache}{backend} = { class =