Question: is there a manual for whitelisting?

[jeroenvermeulen]

Hi @gwillem,

Is there a manual for whitelisting an encrypted licence check from an extension?
I already decrypted the source so I am sure it is safe.

Kind regards, Jeroen

[Mooey28]

I think it's just a hash of the file into the whitelist in the app? Not sure if the actual files are kept in the corpus anywhere? Perhaps it would be good to store the encoded and decided versions of these whitelisted files so people can independently verify that they are indeed safe?

…

On 14 May 2017 13:26, "Jeroen Vermeulen" ***@***.***> wrote: Hi @gwillem <https://github.com/gwillem>, Is there a manual for whitelisting an encrypted licence check from an extension? I already decrypted the source so I am sure it is safe. Kind regards, Jeroen — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#91>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWjyNOQEZZ0wRl4u0AxnP5lcwRENop5cks5r5vMHgaJpZM4NaXOT> .

[gwillem]

They are indeed in the corpus and are processed by tools/build_rules.py (or tools/validate_signatures.py). There's no naming standard so far, suggestions welcome! Actually I was hoping we could do without whitelist (because of the maintenance load), but a pragmatic and small WL enables quite a few signatures.