Merge lp:~ken-vandine/content-hub/url-dispatcher into lp:content-hub
| Status: | Merged |
|---|---|
| Approved by: | Michael Sheldon on 2015-05-18 |
| Approved revision: | 209 |
| Merged at revision: | 209 |
| Proposed branch: | lp:~ken-vandine/content-hub/url-dispatcher |
| Merge into: | lp:content-hub |
| Diff against target: |
401 lines (+343/-0) 9 files modified
CMakeLists.txt (+1/-0) debian/content-hub.install (+3/-0) tools/CMakeLists.txt (+17/-0) tools/send/CMakeLists.txt (+59/-0) tools/send/autoexporter.cpp (+79/-0) tools/send/autoexporter.h (+50/-0) tools/send/content-hub-send.desktop (+9/-0) tools/send/content-hub-send.url-dispatcher (+5/-0) tools/send/exporter.cpp (+120/-0) |
| To merge this branch: | bzr merge lp:~ken-vandine/content-hub/url-dispatcher |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Sheldon (community) | 2015-05-13 | Approve on 2015-05-18 | |
| PS Jenkins bot | continuous-integration | Approve on 2015-05-15 | |
|
Review via email:
|
|||
Commit Message
Added url-dispatcher integration. This allows export and share requests to be initiated by opening a url.
Description of the Change
Added url-dispatcher integration. This allows export and share requests to be initiated by opening a url. For example, to create a share request to facebook you could open a url like:
"content:
Parameters:
* pkg - click package name (required)
* app - click app name, ubuntu-app-launch will attempt to guess if not provided
* ver - version of the click package, defaults to "current-
* handler - export or share, defaults to defaults to "export"
A simple way to test this would be to run this from a shell:
url-dispatcher "content:
This will open the messaging-app and insert the link
File transfers are prohibited, for security reasons. So this only works for remote links and text shares.
- 205. By Ken VanDine on 2015-05-13
-
tidy up a bit
- 206. By Ken VanDine on 2015-05-13
-
merged trunk
- 207. By Ken VanDine on 2015-05-14
-
Cleaned up appId creation and all text to be set
- 208. By Ken VanDine on 2015-05-14
-
white space cleanup
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:208
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Ken VanDine (ken-vandine) wrote : | # |
Are there any related MPs required for this MP to build/function as expected? Please list.
* No
Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
* Yes
Did you perform an exploratory manual test run of your code change and any related functionality on device or emulator?
* Yes
Did you successfully run all tests found in your component's Test Plan (https:/
* Yes, plus I ran the url-dispatcher test in the description. I'll add that to the test plan after this lands
If you changed the UI, was the change specified/approved by design?
* No change
If you changed UI labels, did you update the pot file?
* No change
If you changed the packaging (debian), did you add a core-dev as a reviewer to this MP?
* There are packaging changes, I'm a core-dev
| Michael Sheldon (michael-sheldon) wrote : | # |
This doesn't appear to obey apparmor profiles, so as it stands this could potentially give unrestricted access to all files owned by the phablet user.
For example, creating a simple QML app that calls:
Qt.openUrlExter
Will result in a user's SSH known_hosts file being sent to the hub-importer app (but potentially an app could be using this to send files directly back to itself and it could be grabbing much more important files if they exist, like ~/.ssh/id_rsa).
Unfortunately I don't think applying the apparmor profile of the app which called url-dispatcher will be enough either, as a malicious developer could create a website like http://
- 209. By Ken VanDine on 2015-05-15
-
Don't support file transfers via url-dispatcher
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:209
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michael Sheldon (michael-sheldon) wrote : | # |
Did you perform an exploratory manual test run of the code change and any related functionality on device or emulator?
* Yes
Did CI run pass? If not, please explain why.
* Yes
Have you checked that submitter has accurately filled out the submitter checklist and has taken no shortcut?
* Yes

PASSED: Continuous integration, rev:206 jenkins. qa.ubuntu. com/job/ content- hub-ci/ 254/ jenkins. qa.ubuntu. com/job/ content- hub-vivid- amd64-ci/ 50 jenkins. qa.ubuntu. com/job/ content- hub-vivid- armhf-ci/ 50 jenkins. qa.ubuntu. com/job/ content- hub-vivid- armhf-ci/ 50/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ content- hub-vivid- i386-ci/ 50
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/content- hub-ci/ 254/rebuild
http://