And following on from Jamie's comment about a 0-day update for Firefox
when 12.10 is released - at this stage of the 6-week release cycle (for
Firefox), all addons should be compatible with the next release already.
I expect to have functioning, compatible addons to be available at the
start of
Can we someone from the webapps team to commit to following Chris'
advice and to track nightly builds so problems are found early and
addressed way before the browser updates hit the archive?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also, could someone send an email to security at ubuntu.com CC'ing
Chris with the plan regarding testing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Title:
[FFE] Update WebApps to
Addons compatibility has already been tested with Firefox 16 and 17,
using Mozilla's tarballs. We'll continue to be testing them along the
cycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
I'm sorry, I wasn't clear. I know we are ready now, my concern is future
testing and support in the stable releases for the full duration of
their support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To be more clear. Currently, our developers are testing the addons in
the current and next versions of Firefox (16, 17), using both nightly
builds PPA and tarballs directly from Mozilla. Currently, we are working
in the infrastructure to automate that tests in Jenkins. So we have
manual tests,
@comment 23: the described process will have to be applied to all
supported/maintained versions of FF going forward. My understanding is
that we are covered for now, but adding more versions is a concern,
which to me should be addressed by the test automation vrruiz is working
on.
--
You
The conversation has started surrounding processes for liaising with the
security, so no need to block on this any more.
ACK from security.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Thanks very much for the explanation, that definitely clears up a lot of
questions I had. I wish the README file could be filled out in later
versions with some of the details on what libunity-webapps is, and how
it works.
I see in unity-webapps-apt-package-mechanism.c that it uses PackageKit
to
ACK from release team, please get this in before beta 2 freeze if
possible.
Please make sure to update the README and provide content to the Release
Notes for this.
** Changed in: libunity-webapps (Ubuntu Quantal)
Status: New = Triaged
--
You received this bug notification because you
I realize that this bug is about libunity-webapps and not about the browser
extensions, but this bit concerns me:
Part of the WebApps technology, integration scripts that expand the scope of
a given website (URL) are being run along with a given webpage by dedicated
extensions (for chromium and
- What guarantees do we have that the extension won't break in the next
browser security update?
The extensions all use each browser's built-in extension mechanism, we
don't rely on specific mechanisms besides that only the public browser
extension api. We have (will) to keep track of the changes
Thanks for your response, this is very encouraging because it is
imperative that the security updates go out when they are available.
I think we need to define a process for coordinating your testing with
the security/Desktop team(s). This will probably start with you guys
tracking the beta
Jamie:
- There is a document for the manual tests. The document specify precise
steps to check that the browser extensions are installed and work
correctly, along all the desktop integration features of Web Apps, both
for Firefox and Chromium.
- Firefox has automated tests for the extension,
Jamie:
on the chromium side we are already involved through Ken VanDine with
the chromium team, and working along with the releases and working off
the beta channels before they reach stable. The process is taking shape
and we have tried to be responsive so far,
We will most likely work to put a
Glad to hear about the tests-- sounds like you will uncover the problems
sooner than later before we need to perform a security update, which is
great.
I want to be clear though-- we are most likely going to have a 0-day
update for firefox when 12.10 is released so a plan for interfacing with
my
This bug was fixed in the package libunity-webapps - 2.3.3-0quantal1
---
libunity-webapps (2.3.3-0quantal1) quantal-proposed; urgency=low
* New upstream release.
- Don't add all webapps to the messaging menu (LP: #1052568)
- Update WebApps to support dpkg distribution
Yes for the two questions,
We are in discussion for the Firefox support issues, but landing this
also matters in order to have chromium working,
** Changed in: libunity-webapps (Ubuntu Quantal)
Status: Incomplete = New
--
You received this bug notification because you are a member of
** Changed in: libunity-webapps (Ubuntu Quantal)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Title:
[FFE] Update WebApps to support dpkg distribution
** Changed in: libunity-webapps (Ubuntu Quantal)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Title:
[FFE] Update WebApps to support dpkg distribution
A few comments to help clear things out:
- this is a key feature of the WebApps technology that would actually
prevent it from properly working so its Importance should be set to
'high',
- the code is strictly confined to libunity-webapps and has been tested
for some time now, as Robert Carr
If this causes issues, what is the plan for reverting? what dependencies
need to be taken into account?
Can you please add a code diff so security team has somthing to review?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
- in case of issues, we have a few options:
* remove the code that tries to install a package associated with an
integration script that has been found to be available but not
installed (i.e. a package exists for it) for a given URL, the code
would be removed w/ a low controlled risk from
Do I understand correctly that this is about the browser triggering the
installation of Debian packages from the Ubuntu repository when visiting
webapps-compatible websites?
It looks like the firefox support is not too close to landing (bug
#1040313). Is there much point to landing this without
** Changed in: libunity-webapps (Ubuntu)
Milestone: None = ubuntu-12.10-beta-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Title:
[FFE] Update WebApps to support dpkg distribution
What testing has occured on this? When can it land?
Has the security team reviewed this approach?
** Also affects: libunity-webapps (Ubuntu Quantal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Is there a diff we can review to see what the security implications of
this is?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Title:
[FFE] Update WebApps to support dpkg distribution
A fair amount of testing has occurred, the code actually landed prior to
FFE but wasn't fully enabled, this is some bug fixing around it. Some of
it is also covered by tests, or is a derivative of older tested code.
There is not an exact diff, but the security implementations as far as
this goes
The aptdaemon end of this is handled under bug 1035207
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043461
Title:
[FFE] Update WebApps to support dpkg distribution mechanism
To manage
29 matches
Mail list logo
