Re: Javascript repository or package for PEAR

Hi, Leandro Lucarella wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Bretterklieber, el lunes 3 de febrero a las 17:08 me escribiste:

I think that PEAR don't have to *depend* on JS. I mean that no PEAR package should not work if JS is disabled in (or not supported by) the

yes for "normal" packages, but no If you would like to made client-side password encryption,

First, I'm sory, I forgot to make a list-reply, I'll reply this to the list, I hope you don't mind... About client side encryption, I think it would be optional too, beacuse if you use SSL the client side encryption has no sense. It makes also sense with SSL, because you can pass the CHAP packets directly to other authentication backends like RADIUS, smbpasswd or you can use MS-API functions to authenticate the user directly vs. SAM.

If a package only provides client side encryption, the, IMHO it has to have a big warning saying that the package doesn't works without JS capable browser. There must be no warning, there will be a switch like "plaintext_fallback_allowed", if set to yes, then plaintext auth is performed usualy if JS is deactivated. If not allowed, then auth fails (maybe with a hint that JS must be activated).

bye, -- ------------------------------- ------------------------------------- Michael Bretterklieber - Michael.Bretterklieber@jawa.at JAWA Management Software GmbH - http://www.jawa.at Liebenauer Hauptstr. 200 -------------- privat --------------- A-8041 GRAZ GSM: ++43-(0)676-93 96 698 Tel: ++43-(0)316-403274-12 E-mail: michael@bretterklieber.com Fax: ++43-(0)316-403274-10 http://www.bretterklieber.com ------------------------------- ------------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972