Re: [Tails-dev] Mounting the Tails LUKS partition on Android tablets?
Hi! On 07.12.19 03:08, Teqleez Motley wrote: > On Fri, Dec 6, 2019, at 6:26 PM, u wrote: >> On 06.12.19 15:24, Teqleez Motley wrote: >>> IMO, it would be incredibly practical to be able to mount the Tails LUKS >>> partition on Android tablets. >>> This might also open up the use of Tails to more purposes/user groups. >> >> What are you trying to achieve exactly? Accessing data to share it using >> apps on the Android device for example? Why do you think this is useful? >> > > Using LUKS in/for/with Android is useful by itself, regardless of Tails. > > For those of us that use both Android and Tails, it would also be very > practical to be able to do this; use the same LUKS partition without having > to synchronize anything anywhere; just use the same one for both. > > I am thinking that it would be possible to kill two birds with one stone > here, so to speak. I'm always a bit wary of such shortcuts, because in my experience this often leads to forget about benevolence, and thus forget about what your actual (technological) needs were. > Why not make Tails useful for this as it is one of the most easy ways to get > LUKS on a USB stick without any technical knowledge or ditto setup? It may > help spread the word of Tails and its otherwise useful functionality as well. As explained in my previous email, there are solutions for exchanging data between two devices (and more). Any such exchange might compromise your disk, potentially, as Tails cannot protect you from compromised hardware. And again, I think it's up to Android (app) developers to provide a means to decrypt LUKS partitions on Android, not up to devices using LUKS, such as Tails' encrypted persistent partition, to provide any kind of technical means to do so. It's thus out of scope of Tails development. Cheers, u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Mounting the Tails LUKS partition on Android tablets?
Hi! On 06.12.19 15:24, Teqleez Motley wrote: > IMO, it would be incredibly practical to be able to mount the Tails LUKS > partition on Android tablets. > This might also open up the use of Tails to more purposes/user groups. What are you trying to achieve exactly? Accessing data to share it using apps on the Android device for example? Why do you think this is useful? For the record, I think this is something you can try to solve with Android (opening a LUKS partition), but to me it looks like this is not something that Tails can solve. I would share files between the two devices like that: - Use Tails and then use an unencrypted USB stick to transfer data to an Android device for example. - Plug the Android device while using Tails and mount the device disk in Tails to transfer data between the two. u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Reddit Account
Hi! On 25.11.19 22:04, thenerdyanarchist--- via Tails-dev wrote: > Please let me know if it was any of you. Not that I know of. Thank you for taking care of this channel! :) u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Fwd: Converting ikiwiki to hugo
Hi! (I'm putting the author of the blog post in Cc:.) On 21.11.19 21:44, Daniel Kahn Gillmor wrote: > On Thu 2019-11-21 11:49:53 +0100, u wrote: >> Oh my! That's pretty cool: >> >> On Debian Planet: https://bisco.org/notes/converting-ikiwiki-to-hugo/ >> >> With regard to the translation platform and the Linguine effort, there >> were a lot of ideas about moving to another static site generator which >> would allow us to have translated markdown files instead of po files for >> example. This blog post seems to be a very good start. And would build >> the Tails website within seconds instead of within 11 minutes :) > > That does look cool, but just as a heads-up, i recently found a concern > with hugo and its reliance on an outdated and unmaintained version of > mmark: > >https://github.com/gohugoio/hugo/issues/5124 > > Now, it's quite possible that ikiwiki has comparable problems (i haven't > looked into it), so i don't want to suggest that tail making such a > switch would be strictly worse, but from what i can see, hugo does have > a vaguely-bad "smell" to it given this ecosystem stagnation. Thanks for this link! I don't use Hugo myself, and (I personally would opt for another tool) we'd always need such decisions to be made collectively anyway :) - u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Fwd: Converting ikiwiki to hugo
Oh my! That's pretty cool: On Debian Planet: https://bisco.org/notes/converting-ikiwiki-to-hugo/ With regard to the translation platform and the Linguine effort, there were a lot of ideas about moving to another static site generator which would allow us to have translated markdown files instead of po files for example. This blog post seems to be a very good start. And would build the Tails website within seconds instead of within 11 minutes :) I see no urgency to do that, but wanted to mention this on our list for reference :) - u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [Tails-ux] Working group to define the "core Tails system" (#16531)
Hi! On 05.08.19 16:56, intrigeri wrote: > Hi, > > intrigeri: >> So I thought we could try this: > >> 1. Create a working group of a few people who are interested in this >>topic and want to be involved in every step of this process. > >>→ If you want in, please let me know by the end of July. > > I would love if more folks could get involved so I'll happily wait > until mid-September. I would like to be part of that group. >> 2. Gather initial input from everyone (not just members of the >>working group) > >>→ Feel free to send me, by the end of July, a list of statements >>such as "I think feature X / application Y should be part of the >>core Tails system because $REASONS" or the opposite. > >>While doing so, please consider taking our personas into account >>since that's the closest thing we have at the moment to >>collectively defined priorities: >>https://tails.boum.org/contribute/personas/ > >>I will collect this input. It will help the working group take into >>account diverse point of views right from the beginning. > > Same here: you now have until mid-September to share such input. I did not reply previously because I felt like I did not have time to prepare a list of statements. I would also like to suggest to also gather input during a short online meeting, on top of asking people to provide it by email. I believe this will be more efficient. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Steghide
Hi Damian, On 24.06.19 19:58, Damián Chaban wrote: > I was wondering whether you could add steghide to the next version. It's > compatible with Debian and I think it would fit in tails since it's used to > hide sensitive files. It's not that big of a deal but it would be nice to > have it there. Thanks for the suggestion. We do not want to bloat Tails too much for everyone, however, you can use our Additional Software Feature to install this package automatically every time you boot Tails: https://tails.boum.org/doc/first_steps/additional_software/index.en.html#index4h2 Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Call for testing: USB image second boot failure
Hi! some time ago, we started distributing USB images alongside our ISO images, so that the installation process would get easier (especially for Windows and macOS users) and faster (by getting rid of the need to install an intermediary Tails device). Using the USB image, on first boot the system partition is resized automatically. This seems to fail on some computers, but we have very little data about the usefulness of a proposed fix. You can help This is why we ask you today to help us test a fix, even and _especially_ if you did _not_ encounter this bug of a Tails device not booting a second time. The idea is that we want to see if our fix results in regressions for users for whom it initially worked. [1] Interested? === - Please download the .img file from https://nightly.tails.boum.org/build_Tails_ISO_bugfix-16389-recompute-chs/builds/lastSuccessfulBuild/archive/build-artifacts/ - Install the image to a USB key, following the procedure indicated here: - from Windows https://tails.boum.org/install/win/usb/ - from macOS https://tails.boum.org/install/mac/usb/ - from Linux https://tails.boum.org/install/linux/usb/ - Boot your computer with this Tails device once. Shut down. - Boot your computer with this Tails devide again. - Please report back in reply to this email (public mailing list): - Brand and model of the USB stick and the computer used for testing - Did the device boot a second time? - If not: did you see an error message on boot? What did it say? Thank you for your help! u. [1] If you're interested in the details: https://redmine.tails.boum.org/code/issues/16389 ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge] typo on unlock_veracrypt_volumes
Hi! On 29.04.19 18:21, intrigeri wrote: > sajolida: >> I've seen no answer to your email on tails-dev. > >> Foundations Team, should this be part of your mission? as per: >> « reviewing code contributions that are on nobody else's plate [...] » > > It definitely is part of our job. segfault asked me for guidance > a couple weeks ago wrt. how to handle this and I replies. I suspect > this fell through the cracks since. segfault, are you still on it? > > (As we can see, email is slightly suboptimal to track such things.) Maybe emmapeel can create a ticket on Redmine? Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Security implications: moving code from Verification Extension to our website
Hi all, In summary of this discussion, I would conclude that we agree that we can and should abandon the Verification Extension and move the code to our website. Thank you all for your insightful ideas & comments. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Security implications: moving code from Verification Extension to our website
Hi! On 26.04.19 14:51, intrigeri wrote: > u: >> On 16.04.19 14:29, intrigeri wrote: > >>> One rather minor implementation note, that's relevant in this context >>> only because any software is only as secure as the _version run by >>> actual users_: this migration increases the need to ensure web >>> browsers use the correct version of the relevant web resources (such >>> as JavaScript files), to replace the extension version check we >>> currently have, which is done for every download. At the moment JS can >>> be cached for 24h. We have a ticket about this already; I think it >>> needs to be part of the migration plan. > >> I don't think this increases this need: it's still the same as it is >> now, as the Installation Assistant already uses Javascript files hosted >> on the server. > > Fair point, a component of the big picture is already subject to this > problem, so perhaps having even more code subject to this problem does > not change anything substantially. I don't know and I don't feel > competent to analyze the consequences of this further myself. The best > I can do is to clarify some technical details that might be useful to > whoever wants to dig deeper. So, this proposal replaces: > > A. code, that currently lives in the current extension, and does its >own version checking independently of JS caching policy: it only >relies on data it gets from a HTML page that should not be cached >by browsers > > with: > > B. code that can be retrieved from the browser cache > > And in both cases, as Ulrike mentioned, there's another piece of > cooperating JS code, that lives on our website and can already be > retrieved from the browser cache. I've noted some of your remarks (cross-origin policy + file caching) this on the ticket description of https://redmine.tails.boum.org/code/issues/16128 However, currently we do this version check to check if the extension verification is up to date on user's browsers. When implementing the code on the website instead, the worst that will happen is that some users live with 24 hours of cached JS code - that we can actually force to be reloaded with methods described in the ticket I linked previously, hence I believe the concern is even less concerning than in the current setup (that requires intervention from users to update their extension). >> Is the ticket you are talking about this one: >> https://redmine.tails.boum.org/code/issues/16091? (It's about CSS, not >> JS, but I suspect the exact same issue applies.) > > Yes. I've just made it more generic :) Seen :) Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Security implications: moving code from Verification Extension to our website
Hi! On 16.04.19 14:29, intrigeri wrote: > jvoisin: >>> General security implications >>> - >>> >>> The question we are asking ourselves is: are there any predictable >>> downsides to move the verification code from an extension to the website? > >> I don't see any significant downsides. > > I could not find any either, as long as the threat called [H] in the > design doc of the current system can be mitigated, either in the same > way as what we currently do (see Cross-origin communication and > Content Security Policy paragraphs) or in other ways. Noted. I think that we would need to and we'll be able to tighten the Cross-origin policy compared to what the extension currently does. > One rather minor implementation note, that's relevant in this context > only because any software is only as secure as the _version run by > actual users_: this migration increases the need to ensure web > browsers use the correct version of the relevant web resources (such > as JavaScript files), to replace the extension version check we > currently have, which is done for every download. At the moment JS can > be cached for 24h. We have a ticket about this already; I think it > needs to be part of the migration plan. I don't think this increases this need: it's still the same as it is now, as the Installation Assistant already uses Javascript files hosted on the server. Is the ticket you are talking about this one: https://redmine.tails.boum.org/code/issues/16091? (It's about CSS, not JS, but I suspect the exact same issue applies.) Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Updated to latest version automatically, locked out of persistent storage
Hi! I'm forwarding this to our help desk, in Cc: On 23.04.19 15:02, Ash Goodman wrote: > It won’t accept my password to get into my persistent storage , all i did was > a upgrade automatically. > Passsword is correct , > Please help > Thanks ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Security implications: moving code from Verification Extension to our website
Hi! On 26.03.19 12:01, sajolida wrote: > u: > It's good to see you on our discussion channels :) > >> On 22.03.19 15:47, Nicolas Vigier wrote: >>> On Fri, 22 Mar 2019, sajolida wrote: >>>> Whether there's a security loss for the 20% of users who currently use >>>> the extension is precisely what we are asking more opinions about. >>>> >>>> For example, jvoisin's primary reaction on this thread is that it's >>>> doesn't have any significant downsides. >>>> >>>> What makes you think that doing the verification in the extension would >>>> be less secure than doing the verification on the website? What kind of >>>> attacks are we talking about here? >>> >>> It seems the extension is currently only downloading an unsigned json >>> file with https to verify the checksums, so someone controlling the >>> website could return a bad json file. >> >> Correct. >> >>> So it looks like in both cases (the extension and javascript on the >>> website), an attacker controlling the website could make it possible >>> for a bad download to be seen as good by the user. However there is >>> still maybe a small difference: >>> - with javascript on the website, an attacker controlling the website >>>could just disable the verification and claim that any download is >>>good. >> >> Correct. >> >>> - with the extension, an attacker controlling the website could replace >>>the json file with one that contain a different checksum. However >>>they have to guess what the user will have downloaded from the mirrors, >>>which is maybe not easy if only one of the mirrors is bad. This is >>>assuming that the extension only accepts json files containing only >>>one value for the checksum, which I don't know if it is the case. >> >> The JSON file can technically contain many files and their checksums. > > Or the same attacker controlling the website can pretend that the > verification is done by the (genuine) extension but display a malicious > result on the page, pretending that the download is correct. > > With my very little understand of JavaScript and browser security, I > think that the question here is whether the web page is a more risky > environment to run our JavaScript than the extension. But either way, we > can't protect from an attacker controlling the website or what is > displayed on our download page. > >>> With the current version of the extension, I don't know if it makes a >>> big difference. However if there was some plan to improve the extension >>> to make it verify gpg signatures, then that could be a big difference. >> >> Agreed. > > The first version of the extension was actually doing certificate > pinning: verifying that the SSL certificate of the website was signed by > the correct certificate authority. We dropped this security feature last > year when switching to Web Extensions. Having the extension do other > kind of verification (eg. OpenPGP) would achieve something similar. > > But since we can't protect anyway from an attacker who can control the > website or what is displayed on our download page, having the extension > do more elaborate verifications might not bring much. …unless the logic of the verification extension changes substantially: it could alert the user differently than by using postMessage and display failure messages in the browser using some sort of ugly browser popup instead of displaying the information on our website. Then the website can not interfere. I did not check if this is possible technically. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: Redmine workflow change
Hello, On 25.03.19 10:10, Daniel Kahn Gillmor wrote: > On Sun 2019-03-24 11:36:11 +0100, intrigeri wrote: >> Thoughts? >> >> I'll be happy to implement this proposal. > > I'm not a regular contributor, so you should weight my opinion very > lightly, but this all sounds quite to me. > > The more i see technical systems in actual use, the more i think that > simpler tooling is better and more likely to be used effectively, even > if it is not as nuanced. > > The argument for nuance is that it can typically represent reality more > closely than the simpler view. But if, in practice, that nuance isn't > widely understood, or is accidentally misused, then that particular > advantage is actually a disadvantage. > > Your proposal sounds simpler and therefore more likely to be accurate. I'm all for simplifications of workflows :) Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Security implications: moving code from Verification Extension to our website
Hi!
On 22.03.19 02:24, Daniel Kahn Gillmor wrote:
> Is the concern that it's too expensive to maintain both the extension
> and the javascript going forward?
Ideally we'd only maintain one of those, but I think your idea is good:
if we could increase verification by having an internal mechanism, this
would be an improvement. However, the question remains: what happens if
an attacker controls the website?
> If the expense of maintaining the extension is too much, i wonder
> whether image verification is the ultimate concern at all. For example,
> should we be considering other approaches like external, spot-checked
> download verification with monitoring and reporting, as some measure of
> resilience against non-targeted attack? (maybe this is already in place
> and i just don't know about it)
I'm not quite sure what you mean but we regularly and automatically
check that all the mirrors serve correct images ({IMG, ISO} + SIG are
checked), independently of the individual verification that users should
do when downloading an image. But there might be a delay with us
reacting to this if a mirror is compromised.
Cheers!
u.
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Security implications: moving code from Verification Extension to our website
Hi! On 22.03.19 15:47, Nicolas Vigier wrote: > On Fri, 22 Mar 2019, sajolida wrote: >> Whether there's a security loss for the 20% of users who currently use >> the extension is precisely what we are asking more opinions about. >> >> For example, jvoisin's primary reaction on this thread is that it's >> doesn't have any significant downsides. >> >> What makes you think that doing the verification in the extension would >> be less secure than doing the verification on the website? What kind of >> attacks are we talking about here? > > It seems the extension is currently only downloading an unsigned json > file with https to verify the checksums, so someone controlling the > website could return a bad json file. Correct. > So it looks like in both cases (the extension and javascript on the > website), an attacker controlling the website could make it possible > for a bad download to be seen as good by the user. However there is > still maybe a small difference: > - with javascript on the website, an attacker controlling the website >could just disable the verification and claim that any download is >good. Correct. > - with the extension, an attacker controlling the website could replace >the json file with one that contain a different checksum. However >they have to guess what the user will have downloaded from the mirrors, >which is maybe not easy if only one of the mirrors is bad. This is >assuming that the extension only accepts json files containing only >one value for the checksum, which I don't know if it is the case. The JSON file can technically contain many files and their checksums. > With the current version of the extension, I don't know if it makes a > big difference. However if there was some plan to improve the extension > to make it verify gpg signatures, then that could be a big difference. Agreed. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Security implications: moving code from Verification Extension to our website
Hi security people, after working on the Verification Extension for the USB image project, I proposed to get rid of it and integrate the Javascript code that performs the verification directly into our website [1]. Today I'm writing to you because we need your valuable input on the security implications that such a move might have. We lack these skills in our team and would appreciate your help. Below, I'll describe the current state of things, the possible benefits of this move and then I'll try to outline the security question we have. Current state of things --- Users download Tails images via mirrors operated by volunteers. When installing Tails, we advise users to verify the files downloaded using the Verification Extension, that currently works in Firefox and Chrome. The extension only downloads a JSON file located at tails.boum.org over HTTPS, and checks that the hashsum we provide matches that of the user downloaded Tails image. We know from Javascript statistics of our download page that roughly ~20% of the downloads of Tails images are verified by users using the verification extension. The optional OpenPGP verification accounts for 9% of downloads (computed using the number of downloads of the OpenPGP signature). This means that >70% of Tails downloads might currently not be verified at all. Benefits of moving this code directly into our website -- - More users could more easily verify the images they download. (Note that we don't have metrics for the percentage of users affected, because we lack a detailed analysis of why so few users verify their download.) - It will increase usability for users, as they won't have to install an extension anymore. - Downloads could possibly be verified using other browsers, like Safari and recent versions of IE. (Note however that these browsers currently represent only 1% of visitors to the download pages.) - There'll be a bit less maintenance work for us, but not much: as we would still have to test the code regularly. General security implications - The question we are asking ourselves is: are there any predictable downsides to move the verification code from an extension to the website? If needed, details about the security threats and measures of the extension can be found in our design documentation [2]. Cost Replacing the extension is going to cost money: A rough estimate is that it'll require ~100 hours of work from developers, UX designers, technical writers, managers, and accountant to make this happen, in two iterations (see [1] for a detailed implementation plan). Glad to read your thoughts! Thank you for your input, u. [1] https://redmine.tails.boum.org/code/issues/16128 [2] https://tails.boum.org/contribute/design/verification_extension/ ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails vs Electrum
Hi! On 20.03.19 01:15, segfault wrote: > sajolida: >> Summary of the situation >> >> [...] > > Thanks a lot for the comprehensive summary! > > This sounds like a serious issue. I share your concern regarding losing > users (and good donors). So I think we should avoid removing Electrum > without at least documenting a workaround. > > I would be willing to spend some hours on helping with this. I could > start with looking into whether it's feasible to ship the AppImage. > > Other ideas: Could one of our Debian Maintainers sponsor a Electrum > 3.3.2 upload? Or could we package and upload it to our own repositories > until it's updated in Debian? As far as Debian is concerned, there is an RC bug that has been opened for this issue on Feb 7th, without reply from the maintainer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921688 I sent him an email yesterday, but I think at this point we can probably assume that he's not going to handle this issue fast. I have looked into the packaging [1] a bit, it seems doable to prepare a new upstream version for 3.14. Cheers! u. [1] https://salsa.debian.org/cryptocoin-team/electrum ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails vs Electrum
Hi! On 19.03.19 18:07, sajolida wrote: > If we decide not to ship the AppImage, we could also try to contact the > Debian maintainer. I'll do that right away. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Less ticket triaging → better self-organized views
Hi! as we are in the progress of refining the ticket gardening role, to make it use less valuable time and energy, we created two views to help everyone prioritize their work better. I'm sending you the links to these views so you can have a look. You can also find both views in Redmine's "Custom queries" bar for future reference. 1. *Stalled: unblock other people's work* https://redmine.tails.boum.org/code/projects/tails/issues?query_id=317 This provides you with a view of tickets assigned to you where QA Check is "Ready for QA" or "Info Needed", i.e. someone else is waiting for your input and you can help unblock their work. 2. *Stalled: work marked in progress without updates for a while* https://redmine.tails.boum.org/code/projects/tails/issues?query_id=316 This view shows you tickets assigned to you that have already seen progress but then have not been updated for a long time. When looking at tickets in this view, please ask yourself if you can realistically come back to them and finish the work in the next 6 months. If yes: please add a suitable target version and when relevant, add a "blocks" relationship to the "Core work: $team in $quarter" ticket. If no: deassign yourself, then: if relevant for a core team [1], bring it to their attention; or else, forget it, make some tea and relax :) You don't have to do that now, in the future we plan to send automated reminders regularly to everyone concerned. Don't hesitate to ask me on the list or in private if you're not sure what to do. Cheers! u. [1] https://tails.boum.org/contribute/working_together/roles/ ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails 3.12.1 does not start on Dell XPS 8930
Hi Chris, I'm forwarding this to our help desk, in copy of this mail. On 23.02.19 17:03, Chris Harrington wrote: > I tried launching Tails 3.12.1 from a DVD on a new Dell XPS 8930. I get to > the screen where it says Start Tails (or Shutdown). When I click on Start > Tails a terminal window pops up: > > ath10k_pci :03:00.0: firmware: failed to load > ath10k/pre-cal-pci-:3:00.0.bin (-2) > > Then it goes back to the Start Tails screen. Happy to help > test/troubleshoot if I can. I'm guessing Tails doesn't have the support for > the Ath chipset used for Bluetooth. > > --Chris > > > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. > ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Ticket triaging session: you can help
Hi! starting on March 4th, I'll be triaging tickets on Redmine for a week. If you can, please go through your tickets before this date and try to - add all relevant metadata (are you working on it: mark in progress, are you blocked: write a comment with details, are you waiting for review: mark ready for QA etc.) - unassign yourself from those that you don't want to work on anymore - close tickets that are done Don't hesitate to ask here or in private for clarification if you don't know what to do with a ticket, or just leave them as they are → I'll go through all of them one by one in March anyway. Cheers, u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] new public Tails mirror (Hungary)
Hi! I'm forwarding your email to the mirror list (in Cc:). Peter Makk: > Dear Tails Developers, > > > This is Peter Makk from Hungary. > > I would like to inform You that I have started a new public Tails mirror . > > Rsyncing from mirrors.rsync.tails.boum.org::amnesia-archive every hour. > > > _Mirror details:_ > > > mirror's operator: > Quantum Mirror > > URL of the mirror's operator: > https://quantum-mirror.hu > > > The base URLs to the "tails" directory: > > *http://tails.quantum-mirror.hu/* > or > *https://tails.quantum-mirror.hu/* > > > http://quantum-mirror.hu/mirrors/pub/tails > or > https://quantum-mirror.hu/mirrors/pub/tails > > > The name and contact address of the mirror operator: > > Peter Makk > *r...@quantum-mirror.hu* > > > Additional information about the mirror: > > *quantum-mirror.hu (78.131.56.189)* > > It only serves IPv4 connections. > > Not providing FTP service, but it has a public rsync service up to 60 > concurrent connections. > > > *rsync://quantum-mirror.hu/tails* > > > > The mirror has *200Mb/s* international upload bandwidth. (in a few weeks > it will be 1Gb/s) > > (also accepts connections from other countries, regions and does not > limit their bandwidth) > > If You need more information or have any questions, please feel free to > write an e-mail to r...@quantum-mirror.hu or check out the distribution page > https://quantum-mirror.hu/web/distributions_en.html#tails . > > > Best regards, > > Peter Makk > > Sysadmin > quantum-mirror.hu > Hungary > > > > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. > ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Wifi card Re: GDM
Hello! > I must report also that while booting 3.11 on my HP DM4 laptop is successful, > Tails does not detect the laptops internal WiFi card. All other Tails > releases since 3.9 have detected the internal card on the DM4. Could you run in a terminal lspci | grep Network and send the output either here (public list) or to our help desk (https://tails.boum.org/support/). Thank you, 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] GDM
Hi! alienpup: > rajer bosho wrote: >> 2. secondly,the error stated as " Error starting GDM with your graphics >> card: Intel corporation core processor Integrated Graphics Controller >> [8086:0046] (rev 02). > Sadly, I must report the same problem with 3.11 on my Lenovo T420 laptop. > v3.11 boots to a blank screen. The "xorg-driver+intel" boot switch (and > removal of "quiet") reveals the same warning regarding the failure to launch > GDM. > > The T420 reports the same graphics controller as rajer's computer does > ([8086:0046] (rev 02)). Thank you for your reports. We now have a ticket to track this issue that unfortunately hits many users (https://redmine.tails.boum.org/code/issues/16224) and seems to be related to a problem in the Linux kernel (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914980). Cheers! u. 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.
[Tails-dev] Monthly meeting November
Hi! unfortunately the (inofficial?) quorum of three people to actually have a monthly meeting was not reached tonight. I've thus canceled the meeting. 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] New Tails Mirror
Hi Adam, thank you for setting up a mirror. Please use tails-mirr...@boum.org for future communication about a mirror. I am forwarding your message there. 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] [Tails-project] Tails contributors meeting: Saturday November 03
Do we agree that because this meeting is scheduled on a Saturday, it should rather happen on November 6th, ie. Tuesday? ___ 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] 问题
Hi! For some reason I forgot that helpdesk is reachable under tails-support-priv...@boum.org :) Sending to the correct address now. u: > Dear Zhongling Miao, > > I am sending your email to our help desk: tails-supp...@boum.org. > >> 我的中介tails系统成功安装，但在安装final tails中提示要输入管理员密码认证设备，但我之前是从来没有设置过管理员密码的，这个问题如何解决呢？ >> My intermediary tails system was successfully installed, but I was prompted >> to enter the administrator password authentication device in the final >> tails installation, but I have never set an administrator password before. >> How to solve this problem? > ___ > 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 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] 问题
Dear Zhongling Miao, I am sending your email to our help desk: tails-supp...@boum.org. > 我的中介tails系统成功安装，但在安装final tails中提示要输入管理员密码认证设备，但我之前是从来没有设置过管理员密码的，这个问题如何解决呢？ > My intermediary tails system was successfully installed, but I was prompted > to enter the administrator password authentication device in the final > tails installation, but I have never set an administrator password before. > How to solve this problem? ___ 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] Tails 3.9 mouse glitch (mouse stopped working)
Hi! Ty Petronack: > Just sent all my money to my tails persistence usb while downloading the 3.9 > update , after the update got done loading tried waiting some time for > another screen to prompt me to restart tails but it disconnected me from wifi > so I figured I’d try to just restart it anyway after waiting some time to > make sure it doesn’t prompt me to restart , so I restart my pc and every time > I boot tails my usb mouse no longer works. Tried switching multiple USB’s . > Please help Forwarded to our help desk. 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] Please upgrade to the new MAT2
Hello, Anonymous Democracy: > @Tails developers: We'd be more than really happy to see MAT2 in the upcoming > *Tails version 3.9 on September 5th*! :) It's not in Debian yet [https://0xacab.org/jvoisin/mat2/issues/16] and won't be usable without fixing [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907591]. 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] Release schedule for Tails 3.9
Hi! > intrigeri: >> - August 15: feature freeze > >>Everything you want to see in Tails 3.9 must be merged into our >>devel branch by 17:00 CEST that day. > > The path was not the sweetest RM'ing hike I've ever experienced but > somehow we got there! All the major branches that had to make it into > 3.9~rc1 are now merged \o/ Amazing ! :) ___ 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] Suggestion: Determistic key generation option for completely read-only systems
Hi Sebastian, > And that is having, when the Tails OS starts up, there will be a password > prompt. What problem would your solution solve? I often see in nerd communities a strong capacity for problem solving, but often people find solutions before actually having a problem defintion. In order to understand how useful such a solution might be, maybe you could give a bit more background information on your thoughts? 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] Please test pre-commit hook for po files
Hi! intrigeri: > intrigeri: >> Now, this hook runs wiki/src/contribute/l10n_tricks/check_po.sh so the >> problem I'm describing above is still there. This could not fixed in >> pre-commit hook by calling submodules/jenkins-tools/slaves/check_po >> directly instead of going through the symlink. > > Was this fixed? > > Also, I'd like to do a code review before we merge this. > Happy to do that once I have a confirmation that the last problem I've > mentioned was fixed! It was now. A code review is welcome. 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.
[Tails-dev] Deadline 2018-06-29 Please test pre-commit hook for po files
Fellow translators and developers, three weeks ago I've asked on your lists to test a Git hook we've implemented. We've improved this hook and created a script to make your po files comply with this hook. Before we merge this and enable it by default please test this. Deadline Friday 23:59 Berlin time, June 29th 2018. Git hook for PO files = (Assuming tails.git is called `tails` as a remote.) In order to enable the git hook (& assuming you have none enabled yet): git checkout -t tails/translation_platform_hooks git submodule update --init cd .git/hooks ln -s ../../bin/pre-commit-translation pre-commit The hook will only run when you try to commit a PO file, not when working on other files. Expected format === Now, running it as it, will likely result in errors, because the hook assumes a certain format of PO files and its headers: - PO files are supposed to be wrapped at 79 chars per line, this is POedit's default. - empty Project-Id-Version - Last-Translator: Tails translators - Language-Team: Tails translators This is because we want to avoid merge conflicts when automatically merging files on and from the translation platform. Your name is still in the Git commit, so there is no need to worry about attribution. Make your files comply: unify PO headers In order to make all files in your language comply you can run our script in the same branch, where $LANG is your language code, for example portuguese: LANG=pt git checkout -t origin/translation_platform_hooks ./wiki/src/contribute/l10n_tricks/unify_po-headers.sh $LANG Now, look at the `git diff`. Commit all modified files locally. Then try to edit a PO file like you usually do and see if you can commit. If you can't: - try to understand the error message, - fix it or report back here if it's impossible or you do not understand the error. I've also asked for a merge into tails/master of PO files in all languages cleaned with this unification script but this did not yet happen. When it will, I'll let you know. In the future, you could decide to run the unify_po-headers script every time you want to commit PO files and it'll take care of reformatting your files. 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.
[Tails-dev] merge? Re: [Tails-l10n] Please test pre-commit hook for po files
Hi! intrigeri: > u: >> I'd like to see this branch merged in to master after review: > >> tails.git:feature/10034+unify_po_files > > I think your branch includes unintended changes such as: > > --- a/submodules/aufs4-standalone > +++ b/submodules/aufs4-standalone > @@ -1 +1 @@ > -Subproject commit 84295fc49a4778dd60a4a3e9b3075e1b341a356d > +Subproject commit caea84a33dce187ad77f9ee524d7ec46acc69c63 > > Once this has been fixed, I'm happy to review any code changes > introduced by this branch via submodules :) I think this should be fixed. I've force pushed there because I needed to update all files again. 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] Searching documents in an airgap Tails
Hi! sajolida: > drw...@riseup.net: >> On 2018-06-09 05:34, sajolida wrote: >>> drw...@riseup.net: >>>> On 2018-06-04 16:20, u wrote: >>>>>> The discussion we had maybe in the open or maybe in the backchannels >>>>>> was, could we maintain some kind of "journalist pack" for persistence >>>>>> where we package these tools somewhat and these things install when you >>>>>> setup your persistence. >>>>> >>>>> I think it'd be useful to identify some of these tools, and propose them >>>>> when people launch the Additional Software Feature GUI for the first >>>>> time. Also see https://tails.boum.org/news/test_asp-beta/index.en.html >>>> >>>> Sure thing! Could you create a blueprint for this? Thanks! >>> >> >> Could you call it: searching_documents_additional_software > > Here you go! > > https://tails.boum.org/blueprint/searching_documents_additional_software/ Hmmm, my proposal was not only about searching documents, but about a list of software useful for journalists. I will thus rename this blueprint to https://tails.boum.org/blueprint/additional_software_for_journalists Next time I'll try to be more reactive upfront. 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] [Tails-l10n] Please test pre-commit hook for po files
Hi! I've prepared a branch that unifies all the PO headers of our PO files and makes them follow our new rules. I'd like to see this branch merged in to master after review: tails.git:feature/10034+unify_po_files It will likely create conflicts on Weblate, but I can help with this if necessary. If we manage to merge this now, people can test our git commit hooks for real :) What do you think? 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] [Tails-l10n] Please test pre-commit hook for po files
Hi! sajolida: > u: >> sajolida: >>> u: >>> If you're adding validity checks to our current PO files it would be nice >>> to also make them comply >>> with them, otherwise: >>> >>> - Translators (and mergers) will have to fix them one by one >> Actually, the cool thing is that we have a script for it :) See ./wiki/src/contribute/l10n_tricks/unify_po-headers.sh de Where "de" is the language code of the files you want to fix. I've prepared a branch with clean files nevertheless: tails.gittranslation_platform_clean_po > And I guess you also checked (or have a plan so) that the "Update PO > files" of ikiwiki on the production server are compatible with your new > validation rules, right? This will happen. Please update again branch tails.git:translation_platform_hooks to get the latest version of our scripts and git hooks. 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] Build Tails on MacBook 2015?
Hi Marco, Marco Betschart: > A quick heads up on the „Waiting for IP address…“ issue: > > Seems like this is macOS/VMWare Fusion related. Trying to vagrant up a > regular debian/stretch64 shows the same symptoms. > Conclusion: VirtualBox does not support passing VT-x, VMWare Fusion does not > seem to handle vagrant up as it expects. That's "good" news, or at least we now know what happens. > Any chance to build Tails natively on macOS, without any VM? Unfortunately I > don’t own any other hardware as of now. I cannot answer this question, but I believe not. 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] Searching documents in an airgap Tails
Hi! DrWhax: > The discussion we had maybe in the open or maybe in the backchannels > was, could we maintain some kind of "journalist pack" for persistence > where we package these tools somewhat and these things install when you > setup your persistence. I think it'd be useful to identify some of these tools, and propose them when people launch the Additional Software Feature GUI for the first time. Also see https://tails.boum.org/news/test_asp-beta/index.en.html > We would also maintain some sort of deb repo for this. Maybe this could > even be a way to get some funding in from bigger organisations and a way > to support them in software! (crazy thought) I don't think we should maintain a deb repo for this. Instead, let's identify some useful candidates we could propose to install in our documentation on top of what I said above. 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] Searching documents in an airgap Tails
Hi! > On 2018-02-03 07:25, ghostla...@autistici.org wrote: >> Is there a reason Catfish isn't being considered for this? It's in >> Debian and works exceptionally well, with a clean and intuitive >> interface. It has never been requested by many people to include this tool. We currently work on a GUI for the additional software feature in Tails. This feature allows to better choose which package to install to a Tails device on top of the default software. We're currently in the Beta stage and we wondered if it was useful to propose to users to install certain packages, when they run this GUI for the first time. Maybe catfish would be a good candidate. I did not check on it's dependencies though not verify how the search suggestions provided by zeitgeist would work in the context of Tails. If you want to try this feature and install catfish for example please read https://tails.boum.org/news/test_asp-beta/ and report back :) >> A more advanced tool is Pfilesearch, but I don't believe it's >> currently in Debian or Ubuntu (it was invented for Puppy Linux). It's >> extremely simple though, and probably could be added and thereafter >> maintained by Tails itself without any meaningful overhead. Correct, it's not in Debian. 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] Please test pre-commit hook for po files
Hi! sajolida: > u: >> Upon a technical remark, I moved the pre-commit file to >> bin/pre-commit-translation instead. See updated instructions below. >> >> git fetch tails translation_platform_hooks >> git submodule update --init >> cd .git/hooks >> ln -s ../../bin/pre-commit-translation pre-commit > > Doing only `git fetch` doesn't change my checkout and nor creates > ../../bin/pre-commit-translation locally. Indeed! > So instead I did: > > git checkout -t origin/translation_platform_hooks > git submodule update --init > cd .git/hooks > ln -s ../../bin/pre-commit-translation pre-commit Thanks for the updated version of the instructions. > Then I did a dummy change to index.es.po and tried to commit it. > > I got the following: > > Project-Id-Version header is not empty for following files: > wiki/src/index.es.po > > The po files you're trying to commit contain errors. Please fix them > and try again. > > Which make me believe that you didn't run your new PO file validator on all > the current PO files. Absolutely, as said in my email, we did not do that yet and we'll do it once people have tested it and we are ready to merge. At least that was the initial plan. > If you're adding validity checks to our current PO files it would be nice to > also make them comply > with them, otherwise: > > - Translators (and mergers) will have to fix them one by one So, would you suggest we do that on master right now? Or should we instead wait for more comments before making such a modification? > - Ikiwiki on the production server might not be able to do the automatic > "Update PO files" ikiwiki on the production server is currently not impacted by this hook and we are aware that we will have to fix this, but it'll happen at a later stage. > I'm also curious about what `git submodule update --init` does. Are you using > submodules for that? > I'm asking out of curiosity because I don't know much about submodules but I > couldn't find spot what > is specific to your work under .git/modules/submodules. check_po.sh lives in a submodule and we have updated this script in a branch of the same name. So people need to update - at least in case they've never checked out the repository. I'm not 100% sure it's needed in the case you have checked out the submodules, but I've put it in the instructions to be sure. 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] Please test pre-commit hook for po files
Hi! intrigeri: > u: >> intrigeri: >>> u: >>>> ln -s ../../wiki/src/contribute/l10n_tricks/pre-commit . >>> >>> This caught my eye before I could test this. >>> >>> I'd rather not ask all Tails contributors to run code, on every >>> commit, that lives in a section of our website that's publicly >>> writable. Please consider moving this script to bin/ :) > >> With a notion of 'public' that allows only some people to write here, right? > - I believe that the only thing that prevent ikiwiki.cgi from >allowing anyone with an Internet connection to edit arbitrary files >under wiki/src/ is our lockedit plugin configuration. >There's already been security issues in this part of the ikiwiki >code so I'd rather not rely on it when we can cheaply avoid it. Oops. I was not aware of that. > So yeah, in theory, assuming no software bugs, it's safe to put such > code under wiki/src/; but it increases attack surface a fair bit, with > no substantial benefit I can think of, so let's err on the safe side, > as you did already, thanks! If there's a place for such scripts, let's put them there :) > Now, this hook runs wiki/src/contribute/l10n_tricks/check_po.sh so the > problem I'm describing above is still there. This could not fixed in > pre-commit hook by calling submodules/jenkins-tools/slaves/check_po > directly instead of going through the symlink. Agreed. I'll modify this, this will be transparent for the testers. 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] Please test pre-commit hook for po files
Hi! Upon a technical remark, I moved the pre-commit file to bin/pre-commit-translation instead. See updated instructions below. git fetch tails translation_platform_hooks git submodule update --init cd .git/hooks ln -s ../../bin/pre-commit-translation pre-commit 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] Please test pre-commit hook for po files
Hi! intrigeri: > u: >> ln -s ../../wiki/src/contribute/l10n_tricks/pre-commit . > > This caught my eye before I could test this. > > I'd rather not ask all Tails contributors to run code, on every > commit, that lives in a section of our website that's publicly > writable. Please consider moving this script to bin/ :) With a notion of 'public' that allows only some people to write here, right? I moved it to bin/ and will resend the email now. 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.
[Tails-dev] Errata Wednesday June 06 Re: [Tails-ux] Tails contributors meeting: Sunday June 03
Note that as the 3rd is a Sunday, the meeting is rescheduled to Wednesday 06 June, same time same place. sajolida: > The next Tails contributors meeting is scheduled for: > > Sunday 03 June > tails-dev on conference.riseup.net (XMPP) >7 pm in Paris >6 pm in London >1 pm in New-York > 10 am in San Francisco > > Everyone interested in contributing to Tails is welcome! > > If you want to propose a discussion: > > - Make sure that it corresponds to a Redmine ticket with: > > - *Discuss* as its *Type of Work* > - You as its *Assignee* > - Detailed enough information on the ticket > > - Add it to the blueprint of the agenda: > > https://tails.boum.org/blueprint/monthly_meeting/ > > If you want to get involved but don't know yet how, please introduce > yourself during the meeting, and be sure to tell us what you are > interested in. > > The meeting might not be the most adequate time and place to properly > introduce newcomers to the development process, but at least it should > be a fine place to know each other, and schedule a better > suited event. > > We need two volunteers each month to facilitate and take notes. Please > add your name for each role on the blueprint. ___ 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] [review'n'merge] report april
emma peel: > ey there: > > please review/publish the monthly report, i think it is ready: > > https://tails.boum.org/blueprint/monthly_report/report_2018_04/ Published, thanks! 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] [review'n'merge] core files
Hi! emma peel: > ey there: > > please review and merge this super tiny commit: > > [afef14bd10] remove install/os from core_files > > Available at git.tails.boum.org:emmapeel/tails > > * [new branch]corefiles_update > > > I take out the deleted page install/os from the core_files.txt, as it makes > > `wiki/src/contribute/l10n_tricks/language_statistics.sh` fail. Merged! Thanks, 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] Torbirdy version bump for Tails 3.7?
Hi! A spoonful of sugar: > Package xul-ext-torbirdy in Tails 3.6.2 is version 0.2.1. The > current version is 0.2.5. > > * Changelog: > http://metadata.ftp-master.debian.org/changelogs/main/t/torbirdy/torbirdy_0.2.5-1_changelog > > Version 0.2.1 was released Thu, 01 Dec 2016! > > There are a number of important changes since then. Please consider > updating to the newest release. Agreed. I think Tails uses the package from Debian Stretch (0.2.1) and it should use the one from Debian unstable or stretch-backports (currently in NEW queue). 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] [review'n'merge] changing the distro on the docs
Hi! emma peel: > Today a user reported that the additional software repositories doc still > mentions > jessie instead of stretch. > > Here a little patch with also the changes in the translation files. > > > Please review and merge if suitable! reviewed & merged. Thanks! 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.
[Tails-dev] Rescheduled today 16:00 CEST Re: Tails contributors meeting: Tuesday April 03
Hi! anonym: > sajolida: >> intrigeri: >>> u: > Personally I just read this -- while I read tails-project@ I do not do it > often, so next time, please send such proposals to all lists. Also, for this > reason I do not think we can expect most people to have seen this, and should > consider u's 16:00 CEST proposal invalid => today's meeting happens at the > normal time (19:00 CEST). Sorry about not sending this to all lists. I've sent it to our internal list where active contributors hang out and to the public -project list and thought that this would be enough, because it is here that I assumed reaching the people who generally participate in these meetings. > Personally I would greatly prefer 16:00, and will be present then (by > default, since that still is "office hours") to see what happens. I think I've just received an email by intrigeri on -project stating that this proposal has indeed passed. However, it is an exception for this month only So, the contributor meeting *will* indeed happen at 16:00 CEST today. 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] [review'n'merge] small patch fixing the date
Hi emmapeel, thanks for this patch. I will correct this myself a bit differently if you permit - and I'll try to fix this in the report template as well. 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] SecureDrop and Tails vs Qubes
Hi!
Loic Dachary:
> On 12/14/2017 11:31 AM, sajolida wrote:
>> Loic Dachary:
>>> It was suggested to launch a thread
>>> (https://labs.riseup.net/code/issues/15052#note-3) about the reasons
>>> why SecureDrop is working on a Qubes based workstation for
>>> journalists as an alternative to using an airgap tails. Conor & Jen
>>> are cc'ed so they can comment on this.
>>
>> Thanks for starting this discussion!
>> Given that Tails will probably remain relevant in the SecureDrop
>> ecosystem for a while (for example on the source's side), my intention
>> with this thread is to:
>>
>> * Have more feedback from SecureDrop about the Tails in general,
>> hopefully opening communication channels that can be fruitful for the
>> future. I don't remember much discussion on public channels between
>> Tails and SecureDrop in the past.
>>
>> * Understand what Tails should do to be more relevant in similar
>> contexts ("Tails for journalists and their sources").
>>
>>> IMHO the most prominent ones are>
>>> * Qubes is not amnesic and the user can customize it more easily than
>>> Tails
>>> * Tails is amnesic, usable with an airgap workstation and more
>>> secure than Qubes
>>>
>>> * Adding a software distribution channel to a Qubes workstation is
>>> easy while creating and distributing tails derivatives is
>>> challenging and discouraged
>>
>> I agree with "challenging". I partly disagree with "discouraged".
>
> I meant to say I was discouraged by
> https://tails.boum.org/contribute/derivatives/ not that tail discourages it,
> sorry about that. My hunch is that it would take me at least three months
> full time to come up with a derivative addressing all problems (i.e. security
> releases, quality assurance process, automatic upgrades, ...). And most
> likely another three months before recommending that someone uses it for
> real. This is taking into account that I have experience with packaging, Q/A
> automated or manual and release management.
Creating a derivative does not only involve creating the derivative, but
maintaining it. As you might know, we release Tails every 6 weeks, based
on the TorBrowser & FF ESR schedule.
I believe that this is not necessarily the way to go. Instead, it would
be useful to know what SecureDrop is missing in Tails that it finds in
Qubes, and how this might be addressed. So instead of creating a
derivative, it seems more interesting to me at first sight to try to
contribute improvements to Tails.
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.
[Tails-dev] Meeting notes of December meeting
Hi! Please review and merge the meeting notes, available in my repo 451f:tails/monthly_201712 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] Improving ikiwiki upstream [was: CSS fixes]
Hi! intrigeri: > u: >> sajolida: >>> intrigeri: >>>> sajolida: > I say let's skip the meeting and the features request that essentially > ask ikiwiki to change its paradigm in depth to be more adequate to > what we do with it, and instead spend the smallest possible amount of > time reporting more specific issues such as those u listed above. I'm totally fine with your summary and I will report these bugs/feature requests upstream - despite the horrible authentication mechanism of the website (non function on FF, blocked as XSS by Chromium) which made me lose quite some time today already. Worst case, I'll send an email. 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] Review of verification-extension
Hi, Uzair Farooq: >> - What kind of comments does this remove: >>44 data = data.replace(/^[^'"]*#.*/gm, ''); // remove most comments >>I don't see any in >> https://tails.boum.org/install/v1/Tails/amd64/stable/latest.yml > > We copied it from old extension: > https://git-tails.immerda.ch/ma1/download-and-verify-extension/tree/tails-download-and-verify/lib/df.js Hm, but if it's not needed, why don't we remove this piece of code? Can you try? Also make sure that the input we receive here can be trusted. Thanks for the other modifications :) 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] Security of postMessage between Tails Verification and the download page
Hello, intrigeri: > sajolida: >> The work on Tails Verification (the replacement of DAVE) and the new >> download page is almost done and it's work fine. Still, I got quite >> scared reading about the security implications postMessage: > >> https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage > - u: please tell me how deep you have already looked into the safety >of this aspect of the code, and if you did, explain why you think >the current code is safe; I only did basic verifications of escaping inserted code and regexps as well as what I've sent on the list - and what Uzair has now fixed, i.e. replacing * by our URL. I ran the code through JSLint as well and reported my findings in the public email "Review of verification extension". And as said in private, I'd be glad if intrigeri could take a look from more of a security pov. 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] Verification extension [was: HTML prototype for new download page]
Hi! >> - contentscript/verify.js: >> - fetchConf(): please wrap the regexps. > > Not sure what you mean by this. Do you want me to convert them to 'new > Regex()' format? Just put them into parentheses, if this works. >> - manifest.json: >> - "permissions": [ >> "http://*/*;, >> -> please deactivate HTTP. We only want to download over HTTPS. > > Fixed this. Also, I removed 'http://*/*' permission and added only > tails.boum.org permission as we don't require permission for all sites. Great! 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.
[Tails-dev] Review of verification-extension
Dear Uzair,
so here is a more complete review of the extension.
As said, I think there are two urgent matters:
- manifest.json:
- "permissions": [
"http://*/*;,
-> please deactivate HTTP. We only want to download over HTTPS.
- contentscript/verify.js:
- fetchConf(): please wrap regexps.
And here are some other points I realized. If you think that any of
these points are not applicable, please don't hesitate to comment. I'm
not an expert in webextensions.
- contentscript/conf.js:
- change the descriptor file to
https://tails.boum.org/install/v1/Tails/amd64/stable/latest.yml (I think
sajolida created a ticket on our bugtracker already. It's not urgent,
because the other files currently contains the same contents.)
- contentscript/verify.js:
- are we sure that no other URL could be injected here: ajaxData.url=
this.conf.descriptor; ?
- if not let's try to at least verify that the URL starts with
https:// and comes from tails.boum.org
- What kind of comments does this remove:
44 data = data.replace(/^[^'"]*#.*/gm, ''); // remove most comments
I don't see any in
https://tails.boum.org/install/v1/Tails/amd64/stable/latest.yml
- setVerifyListener(){
let self = this;
this.$(this.document).on("change", this.conf.verifySelector, (e) => {
self.calculateHash(e.target);
});
}
-> So here we assume that the person clicks nicely on our button to
verify and that nobody will interfere.
- Can we not verify automatically once the download is finished?
- Also, can we have a listener for the hash in the URL?
For example, if I closed the window but now I want to come back
and just do the verification without downloading again?
- manifest.json:
- "description": "Verify downloaded file", -> please make it clear
that this verifies a Tails ISO image using a SHA256 checksum. (I think
sajolida will handle this.)
- origin of files:
vendor/forge.js: please add a URL of origin for this script as well as
a version number so that we can update it in the future.
- JSLint http://www.jslint.com/ - this is a tool to write JS code which
is not error prone and I think it would be nice to follow the
requirements of JSLint.
- Please use double quotes instead of single quotes.
- convert tabs to spaces
- fart operator =>
- example: this.fetchConf().done()=>{
JSLint requires the parens around the parameters, and forbids a {
left brace after the => fart to avoid syntactic ambiguity. See:
http://www.jslint.com/help.html#function
- replace for loops with foreach (low prio)
- Consider using strict-mode:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode
We want this code to be forwards compatible as much as possible as
well as as secure as possible.
- Integrated jquery library. Can we get rid of it and use only vanillaJS?
- Whishlist: please document how to test the extension locally in a
README file.
- Exclude this README file from the resulting XPI.
- See as example the HACKING file in tails
ta...@git.tails.boum.org:download-and-verify-extension
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] Logo broken on tails.boum.org/install
Hello! sajolida: > u: >> sajolida: >>> segfault: >>>> I just noticed that the logo looks broken on every page under >>>> tails.boum.org/install/ (see attached screenshot). >>>> >>>> I suspect that this has something to do with the "Removing the subtitle >>>> in our logo" threat, maybe a test version was accidentally pushed to >>>> master? >>> >>> Oops, thanks for letting me know! >>> >>> This doesn't happen to me here (see attachment) and I don't see any >>> change to the logo been merged by accident so I think that this has been >>> like this forever. Still, it's definitely not good! >> >> It has been like this forever. When I asked about it last time, I was >> told this is on purpose. It's the design of these pages. > > Ha ha! That's what we get from "innovative" design: we don't even know > ourselves what's broken and what's not :) > > - It's on purpose that the *bottom* of "Tails" and "Installation > Assistant" is cut out (tchou's idea not mine). > - It's not on purpose that "Installation Assistant" collapses with > "Tails" on small screens. > >>> I think I will get rid of the special CSS treatment on the installation >>> assistant because I don't see the point anymore → #14852. >> >> Ok, please do that only once #14557 has been merged as I made some >> modifications to assistant.css (very slight because there was some >> illogical CSS styles in there which broke my donation banner). > > I clearly won't work on this in October :) I.. just did it in 01bb8cf57aa594e776b1e7b466cadcb53d6cbf5d. -- after launching our donation banner. Please revert if you think I should have waited or done it differently. 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] Improving ikiwiki upstream [was: CSS fixes]
Hi! sajolida: > intrigeri: >> sajolida: >>> CSS is notoriously painful to work with in the project because nobody >>> likes it, our CSS are super messy, ikiwiki is crap in this regard, etc. >> >> Taking a step back. >> I'd be happy to help translate "ikiwiki is crap in this regard" into >> actionable bug reports, but I can't do it alone. > > I admit that I'm very bad at reporting bugs to ikiwiki but in my > imaginary at least, ikiwiki is not a very active upstream project > either. So I thought that the bugs that I might fill would just rot > there forever. Same here. > Now: > > - Improving our website in general, like reporting and fixing bugs in > ikiwiki is nowhere in our core budget so it would have to be volunteer > time, and at least to me, not at all exciting time. Maybe that's a > problem in our core budget but right now changes happen on the website > mostly through technical writing (which is about content), ideally > through UX (tiny tiny bits), as side effect of other work > (installation assistant, donation campaign, etc.). But right now > nobody is really responsible for this work I think. > > - The limitations I suffer the most from in ikiwiki seem, at first > sight, too deep to deserve a bug report. The "templating" system > extremely primitive and my suggestion would be to replacing > completely, it has no CSS framework, it's not designed for content > reuse, etc. But I trust you intrigeri to help me frame this as > more pragmatic fixes that can happen before the year 2525. What my problems with ikiwiki were while working on the donation campaign: - make it easy to add parameters to URLs when building links, i.e. [[linktext|path/to/link]] should be able to also build links that resemble [[linktext|path/to/link?param=something]] and let's go crazy: [[linktext|path/to/link?param=something]] - the template language can only check for boolean variables while it should be possible to check for a value, i.e. @if var == (string) value@. Currently ikiwiki can only either print variables or check if they are set or not. This is the part I found extremely limiting. - I want to be able to include template parts, or to be more precise, .mdwn files, within page.tmpl based on some if statement. These template parts should be translateable. > What's the next step here and who will do it? Call for a voice meeting > with intrigeri, u, and me? Take a few hours during a sprint to talk > about this? I'm at least not ready to take long hours to write emails > about this and would need synchronous communication. I can create bug reports out of these three things I guess. No need for a meeting from my POV. 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] Logo broken on tails.boum.org/install
Hi! sajolida: > segfault: >> I just noticed that the logo looks broken on every page under >> tails.boum.org/install/ (see attached screenshot). >> >> I suspect that this has something to do with the "Removing the subtitle >> in our logo" threat, maybe a test version was accidentally pushed to master? > > Oops, thanks for letting me know! > > This doesn't happen to me here (see attachment) and I don't see any > change to the logo been merged by accident so I think that this has been > like this forever. Still, it's definitely not good! It has been like this forever. When I asked about it last time, I was told this is on purpose. It's the design of these pages. > I think I will get rid of the special CSS treatment on the installation > assistant because I don't see the point anymore → #14852. Ok, please do that only once #14557 has been merged as I made some modifications to assistant.css (very slight because there was some illogical CSS styles in there which broke my donation banner). 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] CSS fixes
Hello, sajolida: > u: >> sajolida: >>> u: >>>> sajolida: >>>>> u: > So I procrastinated for about one hour on removing the subtitle from our > canonical logo. This allowed me then to reuse it as such in the banner > and have the exact same version work on mobile as well. We're down from > 3 variations to 1! > > I pushed that in feature/smallCSSfixes. > > Tell me what you think. I think it's nice BUT there needs to be more space on top and bottom. Stuff needs to breathe.. So please don't add a padding or anything, because this will break other stuff I did in the donation banner branch, but instead make the image slightly smaller. Now it's 100px in height and the the whole banner is 114px high. I think we need at least 10-15px on top and below, so the logo should not be higher than 90px. Also, what I find weird is that the USB stick is not horizontally aligned with the text. You see, the stick is higher than the T and lower too. I can live with this. But I can't live with the missing breathing space. > And regarding your branch, I'm fine merging it once we agree on > something regarding the logo (or even before if you think it will be a > complicated discussion). > > Still, I spotted one little detail (see attachment): in the Farsi > version the search box is much taller. I narrowed the problem down to > having a bigger line-height in the input field in there (34px instead of > 22px reported by Tor Browser). Then I couldn't see where this was coming > from... But I think we can ignore that, unless you find a quick way of > solving it. I cannot confirm that I see this. And I think you did not push your modification. Please note that in the donation banner branch I did some other modifications, like giving a unit to the line-height on body. Which was actually never taken into account... because of the missing unit :) ANd I think this fixes quite a lot of stuff. Please let me know if you need anything else from me before merging this branch. 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] CSS fixes
Hi! sajolida: > u: >> sajolida: >>> u: >>>> sajolida: >>>>> u: > So I procrastinated for about one hour on removing the subtitle from our > canonical logo. This allowed me then to reuse it as such in the banner > and have the exact same version work on mobile as well. We're down from > 3 variations to 1! > > I pushed that in feature/smallCSSfixes. > > Tell me what you think. > > The ticket about removing the subtitle from the logo: #14835. > But I'll raise the issue on tails-project@ as well. > > And regarding your branch, I'm fine merging it once we agree on > something regarding the logo (or even before if you think it will be a > complicated discussion). I find it quite problematic to have this discussion now :( I really don't want this to stop us from launching our donation campaign. So let's please not do that. It's been way too complicated already to make some tiny CSS fixes. Not only is my build wiki setup problematic, but every time we start moving something somewhere, new issues come up, and ground discussions are ignited which makes it very very hard for me to keep my motivation when waiting and working for over three weeks to get some lines of CSS merged. > Still, I spotted one little detail (see attachment): in the Farsi > version the search box is much taller. I narrowed the problem down to > having a bigger line-height in the input field in there (34px instead of > 22px reported by Tor Browser). Then I couldn't see where this was coming > from... But I think we can ignore that, unless you find a quick way of > solving it. I'll look at that later today. 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] CSS fixes
Hi! u: > intrigeri: >> u: >>> intrigeri: >> Given the amount of comments sajolida made + a bunch of new changes >> since he looked at the branch last, I'd like to see him check your >> reply to his review + the current state of the branch, so I'm not >> going to merge this myself. Created https://labs.riseup.net/code/issues/14821 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] CSS fixes
Hi! intrigeri: > u: >> intrigeri: > Indeed, I like it, it's look mch more polished and precise to me! Good! > One comment/question though: in RTL languages, the action toolbar > behaves in a somewhat weird way vs. breadcrumbs. It partly overlays > the breadcrumbs, which produces a weird result in itself, but I can > see some tiny bits of of breadcrumbs text in the empty/transparent > space between actions (e.g. between "Preferences" and "History"), > which is a bit confusing. > I've noticed this on doc/first_steps/persistence/configure.fa.html. I fixed this for RTL languages and some other details while I was at it. > It's a regression compared to what we have on our live website at the > moment. I don't know if that's a blocker, but I want to make sure > you're taking this regression into account when requesting this > merge :) Your call! > > This might also happen on LTR pages if the breadcrumbs are wide > enough, but I didn't check. For LTR languages, this is expected to overlay the breadcrumbs. The actions toolbar being visible only once we hover it I don't see this as a problem, it's a feature :) >> So I hope it is mergeable now :) > > Given the amount of comments sajolida made + a bunch of new changes > since he looked at the branch last, I'd like to see him check your > reply to his review + the current state of the branch, so I'm not > going to merge this myself. Fine with me. > Apart of the aforementioned RTL issue, I personally only have one tiny > comment left on this branch. Commit 7363d4a (that's really not atomic > enough for my taste BTW, but well, whatever) fixes some indentation > but introduces another buggy one: > > @@ -887,7 +883,9 @@ background:#EE; > white-space: nowrap; > font-size: 0.9rem; > line-height: 2.2em; > + height: 31px; > } > + Fixed. I will modify my dotfiles to stop doing this. 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] CSS fixes
Hi! intrigeri: > Hi, > > u: >> intrigeri: >>>> intrigeri: > Done. Everything looks fine to me except the actions toolbar change > that I've just reported in another sub-thread. I've fixed this now and made it much cleaner and nice IMO. So I hope it is mergeable now :) 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] CSS fixes
Hi! intrigeri: > Hi, > > u: >> intrigeri: >>>> intrigeri: > Done. Everything looks fine to me except the actions toolbar change > that I've just reported in another sub-thread. I did not do that on purpose, no, so I have to check what's going on. > Once that last problem (?) is addressed, shall I merge myself or do > you think sajolida should take a look? On the one hand he did not > comment since a week here, but OTOH this branch is modifying a few > tricky bits he implemented in the first place, so I'm a little bit > worried that it could have unintended consequences in corner cases we > didn't think about. But anyway, if anything breaks, we can always > hotfix it, so one option could be that I merge at a time when you're > ready to follow-up if needed during the following week or so. What do > you think? I have the feeling that sajolida does not have time atm for this kind of thing. So I'd rather go for the hotfix option. 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] CSS fixes
Hi!
intrigeri:
> Hi,
>
> u:
>> intrigeri:
>>> u:
>>> commit d2d5d8d76449eab066bb1e992724d13b0b24496f seems to add a black
>>> border-bottom to the links to translations, while the commit message
>>> says "Make other languages stick to the correct place", so perhaps
>>> that was not intended?
> I do see a border, both in Chromium 60.0.3112.78-1 and Firefox
> 52.3.0esr-2.
>
>> I don't see that border
>
> Weird. So either your website build system / process is buggy, or mine
> is. Unless that's because we run different versions of ikiwiki. I have
> the one from sid.
> Firefox developer tools tell me that the black border comes from
> ikiwiki's style.css, that reads:
>
> .pageheader #otherlanguages {
> border-bottom: 1px solid #000;
> }
Interesting. This did not show up when I compiled ikiwiki.
Anyhow, I fixed that now. Thanks for the screenshot.
> That was last changed on 2009-08-15 so I doubt the "we run different
>> I'll convert all tabs to four spaces. Done.
>
> Thanks! Now I see a new kind of inconsistencies though: 4-spaces vs.
> 8-spaces indentation, sometimes in the same block.
Fixed too and pushed to the same branch and my repository.
> I'm not commenting on each individual fix you did as a follow-up to my
> initial review, but they all look good to me :)
Good.
Ready for another round of reviewing? :)
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] CSS fixes
Hi1 intrigeri: > Hi again, > > oops, I forgot — please make sure you test the last version of your > changes with ikiwiki-cgi.setup as well as ikiwiki.setup: the div > class="actions" that's only displayed when the CGI is enabled has > great potential to mess with the div id="otherlanguages". I think this is why the border did actually not display when I compiled the wiki. 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] CSS fixes
Hi! intrigeri: > u: > Meta: I'm not a CSS person so I'll only nitpick^Wcomment on stuff I am > at ease with. Very good :) > commit d2d5d8d76449eab066bb1e992724d13b0b24496f seems to add a black > border-bottom to the links to translations, while the commit message > says "Make other languages stick to the correct place", so perhaps > that was not intended? Uh, "it *seems* to add a black border-bottom" or it does add a border? I don't see that border and git show d2d5d8d76449eab066bb1e992724d13b0b24496f shows indeed that I removed a border, but there is no border which this div inherits, and thus, this line is not necessary. Care to send me a screenshot? > Please use ./wiki/src/contribute/how/documentation/compress-image.sh > on the new images and rewrite history (so we don't import two > versions of the same image into .git :) Ack. Ok, that's done, rather poorly though, it mixes part of CSS commit with these images. I'm not the queen of rewriting history apparently! But well. I'll do better next time. > It looks like lib/banner.png is not used anymore. Remove it? Right! Done. > I see a few indentation (e.g. tabs vs. spaces) inconsistencies > introduced by this branch. I'll convert all tabs to four spaces. Done. > While you're doing house-cleaning, I see "0,5s" transitions in a few > places you don't touch. Is the comma supported there (as opposed to > "0.5s") or do we have code that doesn't do what one might think? :) No, a comma is indeed not supported, so I will clean this. Done. >> I would appreciate if this >> could be merged before starting the donation campaign, that is.. quite >> soonish :) > > I've built the website and noticed no obvious problem, so once these > issues have been fixed I'm happy to merge, unless you think it's more > reasonable to let sajolida review first. Now, something more specific > than "quite soonish" would help me prioritize my work :) Soonish was supposed to mean that I'd like to merge this into my donation banner branch, which will also have to be reviewed at some point early in October latest delay. So the earlier the better, without stress though. 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] CSS fixes
Hi! u: > Hi! > > for the future donation campaign I need a clean start.. > That's why I implemented some small CSS fixes. Please review and merge: > > 451f:tails/feature/smallCSSfixes I've added some more fixes on topright now. I would appreciate if this could be merged before starting the donation campaign, that is.. quite soonish :) 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] Questions regarding DAVE
Hi! sajolida: > Uzair Farooq: >> Hey sjolida and anonym, > >> - What is the location of firefox addon in the repository? > > I'm not sure to understand your question so maybe I'll miss your > point... Right now the only Git repo I could find is: > > https://git-tails.immerda.ch/ma1/download-and-verify-extension/ The code lives here: ta...@git.tails.boum.org:download-and-verify-extension And there are two repositories of previous contributors to this extension, one is Giorgio's, one is mine: maone ta...@git.tails.boum.org:ma1/download-and-verify-extension u ta...@git.tails.boum.org:451f/download-and-verify-extension But you can discard fetching code from there. The main repository is up-to-date! 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.
[Tails-dev] CSS fixes
Hi! for the future donation campaign I need a clean start.. That's why I implemented some small CSS fixes. Please review and merge: 451f:tails/feature/smallCSSfixes 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] Support meek in Tails
Hi! iry: > I am curious about why meek is not available in Tails. My guess is > Tails prefers running meek as a standalone application, which is not > the case so far? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76400 > 7 We'd like to have meek in Tails, and we even have a ticket about it, see https://labs.riseup.net/code/issues/8243 However, as you might read there, it needs to be available in Debian first, which it currently is not. 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] Tails .onion package repo question!
Hi! Nomen Nescio: > I'm seeing this in Tails when I refresh the package repositories: > > Failed - 0B - InRelease - tor+http://vwakviie2ienjx6t.onion/ debian stretch > InRelease > > Why is this happening and how may I fix it please? I'm forwarding your email to our helpdesk who will hopefully be able to help. 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] Reproduction of Tails 3.1 failed
Hi Kevin, thank you very much. > note that I did redact a number of environment variables as well as the > hostname from the system-info output. I would be glad to share the > redacted contents privately if they turn out to be relevant. You can send the unredacted version to ta...@boum.org which is a private encrypted email list, accessible only to few people. See https://tails.boum.org/doc/about/openpgp_keys/index.en.html#index1h1 for the fingerprint of this key. We will collect some more feedback and will send an update out when we have made progress. 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] Replacing Florence with GNOME's own on-screen keyboard?
Hi! Alan: > Hi, > > intrigeri: >> We have issues with Florence design, implementation, and its poor >> integration into GNOME; it's not getting any better over time. One >> option we have is to simply drop it and instead rely on GNOME's own >> on-screen keyboard. > > I've starting looking at GNOME OSK at GUADEC, and updated the ticket with my > findings and opinions so far. Thanks! At the monthly meeting we decided that we do want to switch to Gnome OSK on the long run and intrigeri will prepare a branch for 3.2. 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] Weird commits on stable
Hi, Austin English: > How is spam getting committed somewhere that requires credentials? it happens on the blueprints, which are freely editable. 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] [internal]1st week post-release help desk report
Hi! tails-b...@boum.org: >> and a user reported that with firefox 55, downloading the IOS with the >> add-on doesn't work due to a certificate mismatch (I still need to try >> to reproduce before opening a ticket. > > nor that. I've seen a screenshot from this user (puh, don't ask me where that was) and the URL was a mirror (it was 13.dl.amnesia.boum.org in the image), which we had switched to HTTPS in the meantime and changed its URL. So I suppose that this was the problem. 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] Wrong links in last report
hi! xin: > Hello, I think two links are wrong in "Reproducible website build" part > of the last report. > It should be issues 12566 and 12625, not 12526 and 12525. Oops, modified. Thanks & 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] Changing Tails 3.0 release date? [Was: Planned release of stretch on 2017-06-17 and the last weeks up to the release]
Hi! intrigeri: > ni...@thykier.net: >> Release date >> > >> We plan to release on 2017-06-17. > > I see two options: > > A. Coordinate Tails 3.0 and Debian Stretch releases > >We can prepare two releases at the same time: 2.12.1 and 3.0. >Both should be ready (including release notes, uploading ISO, >manual testing) on June 13. But on June 13 we release 2.12.1 only >(we have to release _something_ on that day anyway due to the >Firefox security updates), and we wait until June 17 to publish >Tails 3.0, at the same time as Debian Stretch. > > B. Don't bother and proceed as our calendar says > >I.e. simply release Tails 3.0 on June 13. > > Pros and cons: > > - Option A costs us one more "Emergency releases" i.e. 2.25 days >of work (release management + manual testing). > > - Option A forces us to integrate Tor Browser 7.0 into Tails 2.x: >this work has been based on the Tails 3.x codebase so far. I don't >know if rebasing it onto the stable branch would be trivial, or >a lot of work. anonym, what's your feeling? > > - Option B is less work, therefore it increases the chances that we >manage to make 3.0 build reproducibly, which gives us good >communication opportunities. So: > > * Ulrike (who committed to handle such communication) and sajolida > (who'll likely be needed to review it), do you think you can > realistically take advantage of this opportunity? I think option B being less work in general, for all of us, so IMO we should go this way instead. I can absolutely take the time to prepare communication next week so that sajolida would have enough time to review it. 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] Saving Additional Software
Hi! DanielBauer1989: > I recently created a post on the TAILS subreddit hoping that someone with > experience could help solve my issue: > https://www.reddit.com/r/tails/comments/6cwail/need_help_saving_additional_software/ > > Sadly, I am yet to conclude/solve this issue and I was hoping that you were > the right people to ask. Are you the right people to ask for help, if not, > who should I be asking? I've forwarded your message to tails-bugs [AT] boum.org. We also have a public support mailing list where you could ask. See https://tails.boum.org/support 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] Ethereum Wallet Request + Funding
Hi, Zach: > I am writing because I would like to see the Tails OS include an Ethereum > Wallet application along side the Electrum Bitcoin wallet that is already > included. I'm aware of the fact that the developers are busy with other > priorities, and additional feature will require additional funding. Please > let me know the amount of funds that would be required to make this feature > a reality. I am very confident in the Ethereum communities ability to raise > the required funds for this feature. Ethereum seems to be the second most trending Cryptocurrency after Bitcoin. We have decided some time ago that while many new cryptocurrencies keep popping up we shall wait and see how this landscape evolves. In any case, in order to get such a client included in Tails, it should first be available as official Debian package, not simply in a PPA. Please read more about this here: https://tails.boum.org/support/faq/#new_software A request for package has already been issued it seems: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860434 We do not have the manpower to work on this ourselves, as it is outside of Tails mission to get this software packaged. 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.
[Tails-dev] May 2017 Contributors meeting notes
Hi, I've pushed the meeting notes from todays short meeting to https://tails.boum.org/contribute/meetings/201705 and updated the tickets that we've discussed accordingly. Four people attended the meeting. We've deleted some tickets from the agenda: [[!tails_ticket 11882 desc="disable recent usage and history in privacy settings by default"]] This tickets seems to have been discussed previously so it's unclear what's left to do here. [[!tails_ticket 12214 desc="Consider documenting a way to manually backup persistent data"]] This ticket is not marked "Discuss" and does not ask for a specific question to discuss. [[!tails_ticket 12442 desc="Define a process how to become a sponsor/partner"]] I added this myself and then deleted it because I've already received valuable feedback which I will work on and share with everybody once I'm ready. [[!tails_ticket 12402 desc="Include Yubico Authenticator in Tails"]] We skipped this ticket because it was late and we started the meeting late. 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] French news index screwed up
Hi, intrigeri: > u: >> the news index in french is completely screwed up : >> https://tails.boum.org/news/index.fr.html > >> Seems to work in other languages though. What's the problem here? > We've been aware of this for years, but I don't think there's any plan > to address either the root cause of the problem in ikiwiki, nor to > acknowledge these limitations and stop using buggy combinations of > features; so for the time being we'll have to live with how > things are. Yes, I was aware that this is an old problem, but I did not know exactly what it was due to. > Sometimes forcing a refresh of the page (e.g. by fixing some minor > issue in one of the inlined pages) is enough to fix the problem. > I've just done that, and it worked. > But https://tails.boum.org/index.fr.html is still buggy :/ How do you do that "fix some minor issue on one of the inlined pages" ? Or should I just look at that myself in Git? :) So I can do it myself next time.. 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.
[Tails-dev] French news index screwed up
Hi, the news index in french is completely screwed up : https://tails.boum.org/news/index.fr.html Seems to work in other languages though. What's the problem here? 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] Please help coordinate the work on Tails 3.0
Hi, intrigeri: > tl;dr: please clarify by the end of April if you can handle your 3.0 > and priority >= Elevated Redmine tickets by May 15. I will handle the rc one (fontconfig in reproducible ISO), and the 3.0 one is about the sponsor page. It's doable too. 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] Maintaining I2P
Hi, anonym: > Alexandre Trottier: >> Sounds good I'll start reading > > I have written the specific requirements here: > https://labs.riseup.net/code/issues/12264 > > Note that what we need in Tails doesn't include Debian packaging, although > someone taking over that part from zzz (the I2P Project Manager, who is not > so happy about having to do it at the moment) would be great! Let us know > what you think! Does that mean that there is a package already somewhere? And thus, that the code used to generate that package is available? That might be helpful for Alexandre I guess. 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] Wiki patches, fix dead links
Hi Arnaud, > here comes wiki patches. Thank you. I did not review this, I just wanted to answer your question: > BTW, what is the prefered way to contribute trivial wiki patches like these > ones ? I think the preferred way is to create a Git branch and publish it somewhere and then issue a merge request on this list like you just did with the patches. 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] Adding an event to monthly report?
Hi, > This was briefly mentioned on #tails-dev, but I gave a presentation > about Tails to the Austin (TX) Linux Meetup: > https://www.meetup.com/linuxaustin/events/233035224/ > > Slides are attached for anyone curious (apologies in advance for my > lack of Libreoffice skills). > > It was suggested that this should be included in the monthly report. > I'm not sure who normally does that, but if you think it's relevant, > please do so :). Thanks for sharing! I added it to our March report which will be public some time in April. See the blueprint for details https://tails.boum.org/blueprint/monthly_report/report_2017_03/ 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] (no subject)
Hi Justin, Justin Davis: > Hi, > Would it be possible to make the Tor bridge configuration readable with > Orca by applying the same thing that was used for Onion Circuits? no need to post twice, we've seen your message but nobody has taken the time to investigate yet. Please be patient. 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] Ticket 7500
Hi, Justin: > Hi, 15 days ago, ticket 7500 was updated. The target year was 2017, > but this was removed. What does this mean? Are we any closer to > having a greeter that can be used with Orca? No, that simply means that we removed this from the roadmap for 2017. 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] [review'n'merge] Remove useless alt in documentation
Hi! xin: >>> I'm a bit confused by this request. Either the pictures convey some >>> useful information, and then they need an alt text, or they don't, and >>> then perhaps they should not be present at all, no? (But I guess I'm >>> grossly over-simplifying :) I'll leave it to sajolida to handle this. > > Sometimes, images are only usefull to know what a thing looks like > (logo, some screenshots) and have no additional information who can be > add in a alt. > >> alt-tags are important for blind people, even when they just describe >> what the image says. >> >> I could not review the branch from the website because the repo is >> private or something, but I think accessibility in HTML always requires >> alt tags, even if they are simply 'logo'. > > I know the importance of alt, on lot of websites alt are misused and are > just noise to blind people. Sometimes, the alt value have to be empty. > > For exemple, in download page, I remove "Wait" alt because after you > have the text "Please wait". > Alt can be empty if the information was already in the text around. > > About web version of my repo, it's a known issue, you have to use git. From a web accessibility point of view, it's good to either have alt="Something descriptive" or an empty alt="" - as said by xin. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Img#Attributes. Quoting from there: "Setting this attribute to an empty string (alt="") indicates that this image is not a key part of the content, and that non-visual browsers may omit it from rendering." I did not look at the branch but it should not completely remove the alt, just its contents when necessary. 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] Our Torbirdy patches needs refreshing
Hi, bertagaz: > Since the 2.5 release, it seems one of our Torbirdy patches are fuzzy, which > makes the build of devel (and any branch based on it) fail. > I have not really followed this part of Tails development, so I can't really > take care of that myself. Would be very nice if someone from the Icedove team > took care of that. Question 1: how urgent is this? Question 2: Against which version of Torbirdy do you try to apply those patches? I've not worked on theses patches myself, but after a very quick glance I can see that they seem to apply to an older version of Torbirdy. I've created https://labs.riseup.net/code/issues/11619 and will look into it more in detail or ask anonym to do this. 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] Moving to 64-bit (x86_64) userspace (#8183)
Hi, intrigeri: > I'm proposing we switch to a 64-bit userspace in Tails 3.0. > I've summed up some of the pros & cons on the description of the > ticket: https://labs.riseup.net/code/issues/8183 > I've added this discussion topic to the August meeting's agenda, as an > additional opportunity to gather feedback about this proposal. With the currently available data this seems to be a sane proposal. 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] Changing default order in Nautilus
Hi, Ulrich Viefhaus: > I added a branch to my personal repo with additions to the > documentation, covering this conversation. > A new advanced topic for changing gnome settings is added that contains > the most common commands for the gnome configuration tool and a warning, > that changing settings could lead to lesser privacy. I let people who are into documentation writing take care of this. > Here is my branch: > https://github.com/UlrichViefhaus/dev-tails/tree/gnome-settings > Don't know how many people need this. But maybe it could reviewed and > added to the official docs? I could also write a German translation. Please don't hesitate to join the german translation team :)) 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.
