Colin Blake wrote: > The use of the word "extension" in Umesh's introduction is misleading. > This is for use within a product, which is not your typical browser with > a typical user. There is no plan to offer any such proxy as a general > purpose extension.
If you want to perform some kind of filtration on the content, the right way to do it is to filter it when it comes out of the SSL pipe in the local browser (or other client product), not to MITM attack the pipe. The MITM attack leaves the browser/client vulnerable to many OTHER attacks. There are other extensions that already do this, intercept/filter the content in side the client process, on "this side" of the SSL pipe. I suggest you try to do it in the way that those other extensions do. Work WITH the client's built-in security system, rather than against it. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
