So the xpinstall.signatures.required=false pref in about:config trick
doesn't work anymore for trunki?
Regards,
Martijn
On Tue, Mar 1, 2016 at 5:48 AM, Philip Chee wrote:
> On 28/02/2016 09:45, Bobby Holley wrote:
>
> >> We were promised that trunk and aurora builds would not enforce addon
> >>
On 28/02/2016 09:45, Bobby Holley wrote:
>> We were promised that trunk and aurora builds would not enforce addon
>> signing when xpinstall.signatures.required=false. I did not see any
>> discussion about rescinding this commitment.
> We also run automation on release-channel builds to test the b
The decision not to enforce addon signing on trunk/aurora is not changing.
But, to support running our automation with unsigned addons on
trunk/aurora, but signed addons on beta/release, we would have to implement
some pretty complex logic at the aurora -> beta uplift, and this is
substantial enoug
On Sat, Feb 27, 2016 at 4:33 AM, Philip Chee wrote:
> On 26/02/2016 22:45, Andrew Halberstadt wrote:
> > To date, our continuous integration has been setting
> > 'xpinstall.signatures.required=false' to bypass addon signing. But
> > soon, this pref will become obsolete and Firefox will enforce si
On 26/02/2016 22:45, Andrew Halberstadt wrote:
> To date, our continuous integration has been setting
> 'xpinstall.signatures.required=false' to bypass addon signing. But
> soon, this pref will become obsolete and Firefox will enforce signing
> no matter what.
>
> In preparation, we will begin si
To date, our continuous integration has been setting
'xpinstall.signatures.required=false' to bypass addon signing. But soon,
this pref will become obsolete and Firefox will enforce signing no
matter what.
In preparation, we will begin signing extensions that are used in our
test automation. If y
6 matches
Mail list logo
