[addons.mozilla.org] Information about v2.6.2 #285
Maybe some of you have already noticed, version 2.6.2 has been released here, but you can't see it on addons.mozilla.org yet. This is caused by the fact that Mozilla has rejected the version. The reason is that I am supposed to give the original source of all 158 resources. Links to CDNs are not allowed 😒
Your add-on includes third-party libraries. Please provide the origin of the exact library version you were using and make sure you are using an exact copy of the original maintainers release version. For more information, refer to https://extensionworkshop.com/documentation/publish/third-party-library-usage/ .
I'll wait and see what I get as a response and update this issue immediately...
You had us hope for a "recommended" badge there :) But we are behind you.
Unfortunately I still have no feedback from Mozilla. The last answer from the reviewer was on 2021-02-26 😒
That would be nice, but I don't think so.
At worst, Mozilla will disable the extension because it violates the policy. 😞
I don't know. Looks like something changed in the validation process in Feb 2021 (see screenshot). The last update of Decentraleyes was in November last year. Maybe Thomas (developer of Decentraleyes) has already been contacted by Mozilla and is also affected.
The test/beta versions are also affected. 😒
Good news. I have received a reply from Mozilla:
Please create a script that would download the files from the servers and compare them to the files inside the XPI. Please remember that established libraries must be included in their original format without any modification (changing the file name does not matter)
@nobody sorry but I tryed your
./audit.sh and had to do
chmod +x audit.sh first (should be set & commited ... but this is only a nit)
then I only got
No connection: ../resources ... for USE_TOR=false
Thanks for testing 👍
I've implemented a few checks, because maybe something is missing on this OS.
Which OS are you using?
I use latest artix (linux 5.11.4 x64)
with your patches if i start it with:
USE_TOR=false ./audit.sh I get this:
... REMOTE HASH: - STATUS: NO CONNECTION https://cdnjs.cloudflare.com/ajax/libs/Swiper/4.5.1/js/swiper.min.js ============================================================================================================================================= SCANNED: 9/1071 PATH: ../resources/Swiper/5.4.5/css/swiper.min.css 1615568271 ERROR torsocks: [socks5] Resolve destination buffer too small (in socks5_recv_resolve_reply() at socks5.c:701) LOCAL HASH: - REMOTE HASH: - STATUS: NO CONNECTION https://cdnjs.cloudflare.com/ajax/libs/Swiper/5.4.5/css/swiper.min.css ===================================================== ...
You have to manually edit that option inside the script and then run the script.
... # ============================================================================= # SETTINGS: # # Use local Tor Proxy USE_TOR=false #fast (~ 5 minutes) # USE_TOR=true #slow (~ 15 minutes) # ...
I'll add this in the README.md 👍
I should have looked more into the script ... but I just asumed it handle things as normal linux scripts do ...
Which variant you use doesn't make a big difference. The only problem with your variant is that the variable is set to true inside the script.
Normally we start bash scripts with
bash script or
bash script.sh, if we follow the conventions of Google. After the script name there are arguments, e.g.
bash script -h or
bash script.sh -h. In this case I've added the
.sh extension so Windows users will immediately know what it is when WSL is configured.
VARIABLE=true script.sh I've seen very rarely.
I've added a small help, which can be called with
bash audit.sh -h.
What a bummer!
Now Mozilla's validator doesn't work. It works without the resources. The version v2.6.3 cannot be published/signed at the moment.
This was probably only a temporary problem 🥳 🥳 🥳
I think we can close here now because version v2.6.2 was not released and now v2.6.3 is waiting for release.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?