Labs/Jetpack/Reboot/JEP/118: Difference between revisions

Jump to navigation Jump to search
update with require("self").id plan
(raise questions about long-term management of the signing key)
(update with require("self").id plan)
 
Line 29: Line 29:
The browser's add-on manager/loader will also check the signature. The AMO check is merely a courtesy to alert developers about signature problems early: the browser's check is the important one, which protects end users.
The browser's add-on manager/loader will also check the signature. The AMO check is merely a courtesy to alert developers about signature problems early: the browser's check is the important one, which protects end users.


The JID will be available to the add-on code via the JEP105 introspection mechanism, perhaps simply as "me.id", or perhaps through some other packaging interfaces.
The JID will be available to the add-on code via the JEP105 introspection mechanism, with the following code:
 
    let my_id = require("self").id;
 
This ID will be a printable string.


==== The Steps ====
==== The Steps ====
Confirmed users
471

edits

Navigation menu