Re: [Tails-dev] Improve Tails Installer UX
hi, kurono wrote (18 May 2016 16:22:45 GMT) : > Regarding https://labs.riseup.net/code/issues/9005 and several related > tickets: #8861, #8860, #8859, #9006, I think its time to ask for > feedback What kind of feedback do you want? (It's not obvious to me given the cross-post.) Do you want code reviews, or shall we wait for the GUI design bits to be reviewed first? Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Improve Tails Installer UX
Hi! Regarding https://labs.riseup.net/code/issues/9005 and several related tickets: #8861, #8860, #8859, #9006, I think its time to ask for feedback even if I know there still things to do (Like deleting *-launcher stuff). But anyway, it would be nice to add changes and fixes before it gets finished. Thanks, kurono signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] An update to zuluCrypt status in debian
segfault wrote (18 May 2016 13:12:34 GMT) : > intrigeri: >> Personally, I'd much rather see work towards having TrueCrypt volumes >> supported in udisks2 and GNOME Disks, than adding a second GUI to >> manage encrypted volumes: having to choose between two tools with >> overlapping functionality seems like a recipe for bad UX, to me. > I agree and I already planned to work on TrueCrypt / VeraCrypt support > in udisks and GNOME Disks. Woohoo! Wait, you just let us know that you can write C, right? Beware, we have lots of other tasks for C programmers :) >> But of course it's a matter of "how much we really want TrueCrypt >> volumes support in a GUI" vs. "the UX regression of adding a tool with >> duplicated functionality". > Right. In my experience, TrueCrypt is something many users miss in > Tails. The most obvious use case is securely sharing files via storage > devices with non-Tails / non-Linux systems. For example users who want > to use Tails to edit documents and share them with others who do not > (yet) use Tails. This is possible with cryptsetup, but I would like to > support this via a GUI, because if this is too hard to do, some users > will instead use less secure systems for this purpose. ACK Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [tor-dev] [GSoC] Tails Server - status report
sajolida: > segfault: >> I sent my first GSoC report only to tor-dev and forgot to send it to >> tails-dev too. I quote it in full at the end of this mail. > > I'll answer on tails-dev only and add George in explicit copy to avoid > crossposting across mailing list. > >> sajolida: >>> segfault: * I began implementing the CLI, the current code (not ready for review yet) is also available on gitlab [2] Next I plan to continue the design of the GUI, after others commented on the new prototype. There are still some features missing which I will implement in time. In parallel I will continue implementing the CLI and discussing the design decisions. >>> >>> Maybe the call for review for the CLI should be sent to >>> tails-dev@boum.org instead of tails...@boum.org :P >> >> I didn't send a call for review for the CLI yet. Actually I wrote that >> it's not ready for review yet (see the quote above). > > I understood this and was mainly pointing out, partly as a joke, that > once it was ready it should be sent to tails-dev and not tails-ux. Sorry > I was unclear. Oh, I didn't get that joke :) > >>> Also, just out of curiosity, when are you planning to work on "Design an >>> extensible and robust format describing the services and how they >>> integrate into Tails"? >> >> I think this discussion has already started with anonym's mail [1]. I >> discussed this further with him in XMPP because I had a different design >> in mind but I think his is better, so I didn't write a mail about this >> after the chat. I already started implementing and extending the design >> (I think most shortcomings only become obvious during implementation). >> Maybe I should send another mail about this. >> >> [1] https://mailman.boum.org/pipermail/tails-dev/2016-March/010506.html > > You're right and I actually didn't read this thread very carefully > myself because it was going out of my department. I was thinking that > for example it would be good to have a blueprint that specifies how to > describe a new service (the options specific to this service, what needs > to be made persistent, how to start and stop it, etc.). And anonym's > email looks like a good start indeed. > > This will be useful during the design phase to allow people other than > anonym and George to review it. For example, I really want intrigeri to > review your specification because his vision is usually nicely > complementary to anonym's but I don't expect him to follow our threads. Ack. > > This blueprint will also be easy to transform into a design document at > the end of your project for more people to develop services. Because > you're developing something like an API or a plugin mechanism here and > this needs to be documented for others to use. Ack. > > That's something we do quite often while working on complex features: we > elaborate blueprints as working documents and reference for reviews > during the process, and then we turn them into design document once the > project is over. And it will also be nicer to you not to have to write > all this documentation once you delivered and want to go do something > else more exciting than writing doc. Ack. I'm convinced and will start working on a blueprint for the TailsService and TailsServiceOption designs. :) ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] An update to zuluCrypt status in debian
intrigeri: > Is anyone here excited in working on this topic? I am, but I have a lot of other things to do :/ Maybe in late summer I will have time for this. > > Personally, I'd much rather see work towards having TrueCrypt volumes > supported in udisks2 and GNOME Disks, than adding a second GUI to > manage encrypted volumes: having to choose between two tools with > overlapping functionality seems like a recipe for bad UX, to me. I agree and I already planned to work on TrueCrypt / VeraCrypt support in udisks and GNOME Disks. > But of course it's a matter of "how much we really want TrueCrypt > volumes support in a GUI" vs. "the UX regression of adding a tool with > duplicated functionality". Right. In my experience, TrueCrypt is something many users miss in Tails. The most obvious use case is securely sharing files via storage devices with non-Tails / non-Linux systems. For example users who want to use Tails to edit documents and share them with others who do not (yet) use Tails. This is possible with cryptsetup, but I would like to support this via a GUI, because if this is too hard to do, some users will instead use less secure systems for this purpose. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [Reproducible-builds] tails binary and source packages lists URL has changed…
Holger Levsen wrote (18 May 2016 08:27:05 GMT) : > On Tue, May 17, 2016 at 06:48:49PM +0200, intrigeri wrote: >> > I'll gladly merge this whenever you tell me I should. >> Please go ahead :) > cool, done. thanks! > https://jenkins.debian.net/view/reproducible/view/Debian_misc/job/reproducible_create_meta_pkg_sets/401/console > worked nicely, so yay! :) ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Can help me？
Nin hao, 东湖海: > hello dear friend！ > > > I am in china tor and tor Bridge can not use，ordinary proxy can not > use too，I want use shadowsocks as tor proxy，but tails can not direct > networking，I don‘t know how can I do？ In China obfs4 bridges should work as well as fte bridges. Other bridges did not seem to work there when I tried last time. I am sending you a bridge which is supposed to work. I will do this by email, but off-list. Directly connecting to the Tor network also does not work, as you say, as all public Tor nodes are blacklisted. This is done through DNS, so using a public DNS resolver (You cannot do that from Tails, but from any other operating system), such as 8.8.8.8 (which belongs to Google) can help you connect to websites which are blacklisted. I don't know shadowsocks and we do not support it in Tails. It is packaged for Debian and thus, it is installable in Tails. But the package which is in Debian is outdated and the upstream developers have removed the source code for this package. This does not inspire confidence to me. If you want to, I'd be glad if you could report back if this information helped you. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [Reproducible-builds] tails binary and source packages lists URL has changed…
Hey, On Tue, May 17, 2016 at 06:48:49PM +0200, intrigeri wrote: > >> I'm working on it and hope to fix it today. > Repaired! > > I'll gladly merge this whenever you tell me I should. > Please go ahead :) cool, done. https://jenkins.debian.net/view/reproducible/view/Debian_misc/job/reproducible_create_meta_pkg_sets/401/console worked nicely, so yay! Thanks! -- cheers, Holger signature.asc Description: Digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
