search

mlgualtieri / CSS-Exfil-Protection

Official repository for the CSS Exfil Protection browser extensions.
MIT License
155 stars 11 forks source link

Feature request: XUL based extension for Pale Moon #9

Open mlgualtieri opened 6 years ago

mlgualtieri commented 6 years ago

Adding this bug as a feature request placeholder.

beerisgood commented 6 years ago

Pale Moon need to add support for add-ons, not otherwise. Also they use a old and unsecure add-on base without signed add-ons

mlgualtieri commented 6 years ago

Thanks for the info! A user wrote to me hoping that a XUL based version could be added at some point. The last time I did any XUL development was a decade ago and I don't remember it being a pleasant experience. I'll still consider it if there are folks who would want to use it. For now, this bug will be a placeholder so I remember the request.

beerisgood commented 6 years ago

I wouldn't spend time on that, but it's your baby ;)

Zero3K commented 5 years ago

Its been 4 months since then. Any updates?

mlgualtieri commented 5 years ago

At the moment there are no active plans to port the extension to Pale Moon. That may change if there's enough demand. I've never used Pale Moon and it's been a long time since I've messed with XUL, so there would be a learning curve to get things going. Unfortunately, at the moment I don't have the bandwidth to dig into it.

ghost commented 5 years ago

I would like to tell the palemoon user, if you want the extension in XUL and well rolled up your sleeves and help the dev to do it, he created an app for both major browsers, you used an obsolete version of firefox as a base, you can not ask all devs to maintain their app under XUL.

FourthDr commented 5 years ago

If this vulnerability was discovered over five months ago, why is it just now getting press?? Also, non quantum based versions of Firefox where still supported back in November of 2018 54.9.0esr? Instead of a full XUL add-on, how about a greasemonkey script? That should be easier to do I would think. You can still get Firefox classic add-ons from here: https://github.com/JustOff/ca-archive

FourthDr commented 5 years ago

You can still find the XUP School here https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Overlay_Extensions/XUL_School Until 2020.

mlgualtieri commented 5 years ago

If this vulnerability was discovered over five months ago, why is it just now getting press??

The extension was made a Firefox featured extension this April, so it's likely why it's getting new (and welcome!) attention. FYI - My original write up was posted Jan 2018. The issue dates back much further though and there is some previous work going back a decade published by others.

Instead of a full XUL add-on, how about a greasemonkey script? That should be easier to do I would think. You can still get Firefox classic add-ons from here: https://github.com/JustOff/ca-archive

'Easier' may be an overstatement. It would likely still need a complete rewrite to work as a Greasemonkey script. It may be doable though. At the moment I really don't have time to re-develop the plugin from scratch and am just supporting the Chrome/Chromium and Firefox extensions.

ghost commented 5 years ago

I have during my free time tested the possibility of use it in greasemonkey (tapermonkey) and it don't work since the chrome command isn't supported in these script.

I suggest to close this request since nobody want to do it (and @mlgualtieri won't do it, which is normal given the amount of work it represents), Personally I haved tried in grasemonkey it don't work and Xul I gave I never want to touch it again in my life xD.

ghost commented 4 years ago

Is this still being considered?

ghost commented 4 years ago

Actually @mlgualtieri work on a news version because chrome 85's change will break some part of the extension, so he have to patch it before that. I'm waiting this new version to try to start implement whitelist too (and merge the localization in it too). So Yes but it's not the top priority of him (or other contributor) it's all i can say. But if anyone who Know Xul can help for the implementation he/her will be welcome to help. :)

mlgualtieri commented 4 years ago

I haven't closed the bug because I don't want to outright close the door on it, but it's not something I have plans for in the near future, for the same reasons as above (would need a complete rewrite in XUL).

As per your comment @aelisya, I'll be releasing version 1.0.18 as soon as I can. I ran into an issue that didn't completely resolve one of the bugs I was hoping to fix in this release. Then I ran out of time to work on it. I'm going to merge my current edits in now, with the intent of finalizing it and releasing it asap... but that won't be before Wednesday as I'm giving a (virtual) talk this week and all my spare time is going into prep for that. The fixes for Chrome 85 won't be until another release.

ghost commented 4 years ago

I was about to check to port it, but i won't do it, since i don't think there is enough user on Palmoon and i have some code to do to prepare the port another extension to manifest V3 and the deprecation of WebRequest