-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > observer? Maybe there's another way to get at the same goal.
I gave this a thought, and I think the proper way to do this would be to use a new enctype value for the form. Anyway, signing is just another different way of encoding an urlencoded form, it's just an extra layer. So, these days we have two enctypes: application/x-www-form-urlencoded multipart/form-data I would like a webdeveloper to specify enctype="application/x-www-form-urlencoded-openpgp-signed" and have firefox (well, my extension) handle how that should be encoded. This way I wouldn't have to worry about using the observer service to tamper the HTTP POST payload, nor even hook on the FORM or "extending" it. So, I need to know/get some pointers/simple exame (I have done some research, but is not much clear) on how to: Declare a new "enctype handler" for the "application/x-www-form-urlencoded-openpgp-signed" type that would, when called, use the standard "application/x-www-form-urlencoded" handler, and then sign (with Enigform's current procedure) the result, and then return that to... Firefox. I think this is quite a better approach. What do you think, group? (sorry to bother, I'm starting to feel like I should use my own mailing list and invite some of you). Sincerely, Buanzo - -- Arturo "Buanzo" Busleiman - Consultor Independiente en Seguridad Informatica Mail Hosting Seguro y Consultoria - http://www.buanzo.com.ar/pro/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF0lp0AlpOsGhXcE0RAu52AJ0XhSPZJpzCcFn1Pow4bbtsX8L2AQCdGsuK 6u9hpsPOSAxmi9luLiFP57E= =0Bjz -----END PGP SIGNATURE----- _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
