Bug #8560 for Apache-Htpasswd: Does module create a new passwd file if none exists?

Mon Nov 22 12:19:16 2004 Guest - Ticket created

Subject:

Does module create a new passwd file if none exists?

Hi Kevin, Thanks for such a useful module. I'm try to do some testing where a passwd file does not yet exist. My tests are failing with the error that the file or directory cannot be found (no such file or directory). I found that simply creating an empty file is sufficient for my tests to pass. It would be nice if there were a way to have A::Htpasswd handle this. Here's all the code it required: # # If the password file does not exist, create it unless (-e $passwd_file) { open (PASS, ">$passwd_file") || die "Unable to open $passwd_file: $!"; close PASS; } Thanks, William

Mon Nov 22 12:50:01 2004 kmeltz [...] cpan.org - Correspondence added

Hi, I'll consider this. I have always wanted the module to only modify the file, not worry about creating it, ownership, permissions, etc... Mainly so the application using it has to deal with that, and not the module. I don't want tainted data being passed to the module, and it creating a file which it shouldn't because the app isn't scrubbing the input properly. I'd rather the app open security holes, rather than the module. Cheers, Kevin [guest - Mon Nov 22 12:19:16 2004]: Show quoted text

> Hi Kevin, > > Thanks for such a useful module. I'm try to do some testing where a > passwd file does not yet exist. My tests are failing with the error > that the file or directory cannot be found (no such file or > directory). > > I found that simply creating an empty file is sufficient for my tests > to pass. It would be nice if there were a way to have A::Htpasswd > handle this. Here's all the code it required: > > # > # If the password file does not exist, create it > unless (-e $passwd_file) { > open (PASS, ">$passwd_file") || die "Unable to open $passwd_file: > $!"; > close PASS; > } > > > Thanks, > William

Wed Aug 26 12:01:02 2009 ambs [...] cpan.org - Correspondence added

On Mon Nov 22 12:50:01 2004, KMELTZ wrote: Show quoted text

> Hi, > > I'll consider this. I have always wanted the module to only modify the

Damn. Doesn't exist yet :( Show quoted text

> file, not worry about creating it, ownership, permissions, etc... Mainly > so the application using it has to deal with that, and not the module. I > don't want tainted data being passed to the module, and it creating a > file which it shouldn't because the app isn't scrubbing the input > properly. I'd rather the app open security holes, rather than the module. > > Cheers, > Kevin > > [guest - Mon Nov 22 12:19:16 2004]: >

> > Hi Kevin, > > > > Thanks for such a useful module. I'm try to do some testing where a > > passwd file does not yet exist. My tests are failing with the error > > that the file or directory cannot be found (no such file or > > directory). > > > > I found that simply creating an empty file is sufficient for my tests > > to pass. It would be nice if there were a way to have A::Htpasswd > > handle this. Here's all the code it required: > > > > # > > # If the password file does not exist, create it > > unless (-e $passwd_file) { > > open (PASS, ">$passwd_file") || die "Unable to open $passwd_file: > > $!"; > > close PASS; > > } > > > > > > Thanks, > > William

> >

Wed Aug 26 12:01:03 2009 The RT System itself - Status changed from 'new' to 'open'