Skip Menu |

This queue is for tickets about the CGI-Auth-Basic CPAN distribution.

Report information
The Basics
Id: 100882
Status: resolved
Worked: 30 min
Priority: 0/
Queue: CGI-Auth-Basic

People
Owner: burak [...] cpan.org
Requestors: nerfur [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Can't use string ("") as a HASH ref while "strict refs" in use at /usr/local/share/perl5/CGI/Auth/Basic.pm line 314. when using 'password'.
Date: Fri, 12 Dec 2014 13:34:41 +0300
To: bug-CGI-Auth-Basic [...] rt.cpan.org
From: S V <nerfur [...] gmail.com>
perl -v This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi CGI::Auth::Basic v 1.22 (from CPAN) CentOS 6 Code to reproduce (taken from examples and added password field): #!/usr/bin/perl -w use strict; use warnings; use CGI::Auth::Basic; CGI::Auth::Basic->new( cgi_object => 'AUTOLOAD_CGI', #file => './password.txt', password => 'hash', )->check_user; my $pok = print "Content-type: text/html\n\n" . 'You can use this program. ' . 'Now anything that this program does is accessible! :)' ; This code produces: Can't use string ("") as a HASH ref while "strict refs" in use at /usr/local/share/perl5/CGI/Auth/Basic.pm line 314. -- Nerfur Dragon -==(UDIC)==-
12 Ara 2014 Cum, 05:34:55 tarihinde, nerfur@gmail.com yazdı: Show quoted text
> perl -v > This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi > > CGI::Auth::Basic v 1.22 (from CPAN) > > CentOS 6 > > Code to reproduce (taken from examples and added password field): > > #!/usr/bin/perl -w use strict; use warnings; use CGI::Auth::Basic; > CGI::Auth::Basic->new( cgi_object => 'AUTOLOAD_CGI', #file => > './password.txt', > password => 'hash', )->check_user; > my $pok = print "Content-type: text/html\n\n" . 'You can use this > program. ' . 'Now anything that this program does is accessible! :)' ; > This code produces: > > Can't use string ("") as a HASH ref while "strict refs" in use at > /usr/local/share/perl5/CGI/Auth/Basic.pm line 314.
Hi, This is fixed in version 1.23 (just released) Thanks for reporting