Feature #15326
Onionshare
0%
Description
Update to the latest version onionshare
Subtasks
Related issues
| Is duplicate of Tails - Bug #14649: Ship OnionShare 2.x in Tails | Confirmed | 2017-09-13 |
History
#1 Updated by mercedes508 2018-02-20 12:08:51
- Assignee set to emmapeel
#2 Updated by emmapeel 2018-02-27 09:44:03
- Status changed from New to Confirmed
- Assignee deleted (
emmapeel) - Target version deleted (
Tails_3.6) - Type of work changed from Security Audit to Debian
- Affected tool changed from Additional Software Packages to OnionShare
Maybe somebody participating in pkg-privacy-maintainers@lists.alioth.debian.org wants to take this one over?
It is true that a lot of improvements have been done in OnionShare since 0.9.2-1 released on Nov 13, 2016:
https://github.com/micahflee/onionshare/releases
(current latest release 1.3, 14 hours old!)
#3 Updated by emmapeel 2018-02-27 09:46:05
- Status changed from Confirmed to Duplicate
oops I just found Bug #14649, thus closing this one as duplicated
#4 Updated by emmapeel 2018-02-27 09:46:32
- is duplicate of Bug #14649: Ship OnionShare 2.x in Tails added
#5 Updated by intrigeri 2018-02-27 10:42:55
emmapeel wrote:
> It is true that a lot of improvements have been done in OnionShare since 0.9.2-1 released on Nov 13, 2016:
FYI this is true for most of the software we ship but we won’t update them all to the last upstream release: we’re based on Debian stable for a reason. In order to make such a ticket convey more useful information than essentially “upstream is alive and publishes new releases”, best is to point out the specific improvements that might be worth doing extra work to upgrade this specific package in Tails.
#6 Updated by emmapeel 2018-02-27 14:10:51
intrigeri wrote:
> best is to point out the specific improvements
The reason I see from my POV is that ‘This has been requested by users’ but I haven’t done a thorough check about specific security features. I added the date of last update, and the link to the different changelogs, so this ticket can be prioritized by somebody with more information about the Debian landscape than me.
> that might be worth doing extra work to upgrade this specific package in Tails.
I thought I didn’t meant that when selecting ‘Type of Work: Debian’, as the ticket this one duplicates means too.
Anyway just wanted to make it clear but this ticket is duplicated anyway.
#7 Updated by intrigeri 2018-02-27 14:25:02
> The reason I see from my POV is that ‘This has been requested by users’
For me it’s not a good enough reason unless these users can spell why they want a newer version: pretty often users don’t understand we’re based on stable and are scared when they see anything that’s not fully up-to-date.
>> that might be worth doing extra work to upgrade this specific package in Tails.
> I thought I didn’t meant that when selecting ‘Type of Work: Debian’, as the ticket this one duplicates means too.
No, that’s fine.
FYI the ticket that one duplicates is about uploading a newer version to Debian and ensuring it reaches Debian Buster. It does not necessarily imply we’ll update OnionShare in Tails 3.x.
> Anyway just wanted to make it clear but this ticket is duplicated anyway.
Sure! Thanks for clarifying :)
#8 Updated by emmapeel 2018-02-27 14:39:40
- Assignee set to Leonardo_Porpora
Just wanted to add some information specially for the reporting user and others interested on Onionshare updates:
As we pin onionshare to install it from sid in Tails 3.x, as soon as it is available in sid, we will be able to have it on Tails (provided it does not break anything).
#9 Updated by Anonymous 2018-02-28 11:42:25
FYI why I did not prepare this new version yet: It introduces many new changes, in particular it will is supposed to allow using system tor - this means that we have to retest quite some things in the Tails context - and this will require some more time than just preparing the package.