List Info

Thread: Auth-1.3.1RC1 (beta) Released.




Auth-1.3.1RC1 (beta) Released.
user name
2006-08-11 01:25:12
A bit more information about the fix to #8407. It should not
cause  
problems if you where using Auth as originally intended
(yeah right  
there is probably 2 users that fall into that category).

Basically it does automatic quoting of table and field
names. If  
you've been adding your own quoting (ie for using table
field names  
with capitol letters in PostgreSQL, using field names that
are  
reserved words) this latest patch will cause your
application to break.

The point of this RC is to get feedback from the user base
about  
whether this patch should stay or not. Personally I believe
it should  
as it is the correct way (well almost, prepare would be
better, but  
this patch is less intrusive), however if there is enough
opposition  
from the user base I'm quite willing to back the patch out
and just  
release the rest of the fixes.

You have until this time next week to speak up or forever
hold your peace.

Adam Ashley

----- Message from pear-devlists.php.net ---------
     Date: 11 Aug 2006 01:21:10 -0000
     From: PEAR Announce <pear-devlists.php.net>
Reply-To: PEAR Announce <pear-devlists.php.net>
  Subject: [PEAR] [ANNOUNCEMENT] Auth-1.3.1RC1 (beta)
Released.
       To: PEAR general list <pear-generallists.php.net>


> The new PEAR package Auth-1.3.1RC1 (beta) has been
released at   
> http://pear.php.net/.
>
> Release notes
> -------------
> This release candidate is test the numerous fixes
described below. It is also
> to get feedback on the change made for Bug #8407. Bug
#8407 adds automatic
> quoting of table and field names used in SQL in the
Database backends.
>
>  * Fixed Bug #7031: session_regenerate_id() not
cleaning up old   
> session storage.
>    Fix for this bug in PHP5.1.0+ has been done, still a
problem in   
> older versions
>    of PHP.
>  * Fixed Bug #7421: Allow false to be passed in for
allowLogin and   
> advancedSecurity
>    options.
>  * Fixed Bug #7434: Enable start_tls support for LDAP
Container by   
> Stuart Prescott
>    <php.netnanonanonano.net>
>  * Fixed Bug #7537: Made File Container capable of
using all   
> File_Passwd backends.
>  * Fixed Bug #7841: Added missing </center>.
Really the whole frontend needs
>    reworking.
>  * Fixed Bug #7860: Removed deprecated session_register
call.
>  * Fixed Bug #7899: sessionValidThru() returning
incorrect value when no idle
>    timeout set.
>  * Fixed Bug #7956: Session handling had several
security bugs   
> before PHP4.3.3.
>    Bumped PHP dependancy so we don't have to deal with
them.
>  * Fixed Bug #8076: MDB & MDB2 Containers not using
default db_fields values
>  * Fixed Bug #8351: Documentation of
$loginFailedCallback pointed to  
>  incorrect
>    set function.
>  * Fixed Bug #8406: Error message updates by Adam
Harvey   
> <pearadamharvey.name>
>  * Fixed Bug #8407: Database containers don't quote
table/field names by Adam
>    Harvey <pearadamharvey.name>
>
>
>
> Package Info
> -------------
> The PEAR::Auth package provides methods for creating an
authentication
> system using PHP.
>
> Currently it supports the following storage containers
to read/write
> the login data:
>
> * All databases supported by the PEAR database layer
> * All databases supported by the MDB database layer
> * All databases supported by the MDB2 database layer
> * Plaintext files
> * LDAP servers
> * POP3 servers
> * IMAP servers
> * vpopmail accounts
> * RADIUS
> * SAMBA password files
> * SOAP
> * PEAR website
>
>
>
> Related Links
> -------------
> Package home: http://pear.php.net/
package/Auth
>    Changelog: ht
tp://pear.php.net/package/Auth/download/1.3.1RC1
>     Download: http://pear
.php.net/get/Auth-1.3.1RC1.tgz
>
> Authors
> -------------
> Martin Jansen <mjphp.net> (lead)
> James E. Flemer <jflemeralum.rpi.edu>
(developer)
> Yavor Shahpasov <yavosiava.org> (lead)
> Adam Ashley <phpadamashley.name> (lead)
>
> --
> PEAR General Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub
.php
>
>


----- End message from pear-devlists.php.net -----

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Auth-1.3.1RC1 (beta) Released.
user name
2006-08-11 07:12:53
Adam Ashley wrote:

> A bit more information about the fix to #8407. It
should not cause 
> problems if you where using Auth as originally intended
(yeah right 
> there is probably 2 users that fall into that
category).
> 
> Basically it does automatic quoting of table and field
names. If you've 
> been adding your own quoting (ie for using table field
names with 
> capitol letters in PostgreSQL, using field names that
are reserved 
> words) this latest patch will cause your application to
break.

Automatic identifier quoting is tricky. For example
interbase has issues 
in that department. In MDB2 I have handled this through an
option 
"identifier_quoting" which defaults to false.

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Auth-1.3.1RC1 (beta) Released.
user name
2006-08-12 14:23:19
Hi Adam:

On Fri, Aug 11, 2006 at 09:25:12AM +0800, Adam Ashley wrote:

> Basically it does automatic quoting of table and field
names.

In your initial post, I thought you were talking about
values.  I 
think automatically delimiting identifiers is a bad idea.

Field names entered into queries from program settings like
this does 
not constitute SQL injection.

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M
P A N Y
            data intensive web and database programming
                http://www.Analy
sisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f:
718-854-0409

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Auth-1.3.1RC1 (beta) Released.
user name
2006-08-14 07:28:07
 

Daniel Convissor wrote:
> In your initial post, I thought you were talking about 
> values.  I think automatically delimiting identifiers
is a bad idea.
> 
> Field names entered into queries from program settings
like 
> this does not constitute SQL injection.

Does it account for someone having previously fed it a
quoted fieldname?  Or
will it double quote things?

If it can account for that..what is the harm? Dan may have a
valid point,
I'm just not sure from what he wrote what makes it a bad
idea (other than
that it is not necessary).

What potential problems might we face?

Thanks!

Jay

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )