[Tails-dev] Release schedule for Tails 6.8
Hi, anonym will be the RM for Tails 6.8 The current plan is: - Monday, October 7: build images, start testing - Tuesday, October 8: release Developers, please: - Book time for automated and manual QA during office hours, from Monday 15:00 to Tuesday 11:00 (Europe/Berlin). If you can't, please let the RM know. - During these 2 days, don't push any change to the branch used for the release. -- boyska (he/him) ___ 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] Cron /usr/local/bin/tails-website-last-month-stats '/var/log/nginx/tails.net'
CronDaemon via Tails-dev: Boots in July: 598388 Downloads of the OpenPGP signature in July: 2668 I understand that the actual number is given by the sum of this email + the one sent by www2, right? -- boyska ___ 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] Siging tails binaries yourself in a custom secureboot environment
So, I want to sign tails with my own keys since I have enrolled my own secure boot keys. I signed /live/vmlinuz and /EFI/BOOT/BOOTX64.EFI and ../GRUBX64.EFI. Upon starting tails, it tells me that something has gone wrong with shim-lock. I know that tails uses shim to work with microsoft-keyed secureboot environments out-of-the-box, but I would prefer just signing tails and not fiddling around with shim. Can I skip shim so that GRUB/syslinux directly boots? (-> maybe as a second EFI entry?). I don't know. I haven't spent much time on it, but, while this looks like interesting research, I think this usecase is really outside of our personas: https://tails.net/contribute/personas/ happy hacking! -- boyska ___ 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] Cron /usr/local/bin/tails-website-last-month-stats '/var/log/nginx/tails.net'
Cron Daemon wrote: Boots in March: 873028 Downloads of the OpenPGP signature in March: 6574 those numbers are going up! -- boyska ___ 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] Release schedule for Tails 6.0
Hi, We still don't know who will be the RM for Tails 6.0 The current plan is: - Monday, February 26: build images, start testing - Tuesday, February 27: releasing @testers, please let the RM know how much time you'll have for manual QA from Monday 17:00 to Tuesday 11:00 (Europe/Berlin) -- boyska ___ 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 for arm64 (with support for Apple Silicon)
During the last few weeks I've been working on porting Tails to the arm64 architecture, with the aim to ultimately being able to run Tails on Apple hardware again wow, that seems to be really good hacking! Thanks for doing that. While right now we have no upcoming plans for developing and maintaining Tails on arm64, this will help us in assessing how hard it could be to have one. -- boyska ___ 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] patch to fix #20079
On 12/01/24 18:14, g4kw via Tails-dev wrote:> I guess I don't have write access to the repo, so I can not create a MR... So I will do as stated on your website: " "You can submit small, easy changes as Git patches (prepared with the |git format-patch| command) over email to tails-dev@boum.org " Thanks for this! I reported your patch on https://gitlab.tails.boum.org/tails/tails/-/issues/20079#note_223596 -- boyska ___ 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] Linux kernel hardening checker
On 06/10/23 18:31, David A. Wheeler wrote: FYI: I've learned of a "Linux kernel hardening checker": https://github.com/a13xp0p0v/kernel-hardening-checker thanks for this! > It might be interesting to run & see if there are missing hardening measures that > should be applied in Tails. I run it into a regular Tails, using sysctl -a > sysctl.txt kernel-hardening-checker -s sysctl.txt It gives us 4 suggestions: - user.max_user_namespaces should be 0. I think we disagree on this. - dev.tty.legacy_tiocsti should be 0. we don't have this option - fs.protected_fifos should be 2 instead of 1. sounds good. - kernel.yama.ptrace_scope should be 3 instead of 1. sounds good. When it comes to kernel-hardening-checker -m show_fail -l /proc/cmdline -c /boot/config-6.1.0-12-amd64 | grep cmdline there are some more cmdline options we could consider using. I haven't investigated those, though. bye, -- boyska ___ 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] Release schedule for Tails 5.16
Hi, intrigeri will be the RM for Tails 5.16 The current plan is: - **Sunday**, August 6: build images, start testing - Monday, August 7: releasing @testers, please let us know how much time you'll have for manual QA from Sunday 17:00 to Monday 11:00 (Europe/Berlin) -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] Release schedule for Tails 5.15
Hi, I will be the RM for Tails 5.15 The current plan is: - Monday, July 10th: build images, start testing - Tuesday, July 11th: releasing @testers, please let me know how much time you'll have for manual QA from Monday 16:00 to Tuesday 11:00 (CEST) -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] Tor Browser 12.0.7 Candidate Builds Available
On 01/06/2023 17:41, Richard Pospesel wrote: Tor Browser 12.0.7 release candidate builds are now available for testing: https://tb-build-05.torproject.org/~richard/builds/release/unsigned/12.0.7/ Thanks richard! Do you still plan to release on Wednesday, right? -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] Release schedule for Tails 5.14
Hi, I will be the RM for Tails 5.14 The current plan is: - Monday, June 12th: build images, start testing - Tuesday, June 13th: releasing @testers, please let me know how much time you'll have for manual QA from Monday 17:00 to Tuesday 11:00 (CEST) -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] CHANGE SOURCE CODE OF TAILS
On 05/05/2023 19:25, Marco Benato wrote: EN: I get in touch as an enthusiast ^-^; I'm doing my TCC(Completion of course work) theme on TAILS-OS and I would like to know if it is possible to modify its source code, I don't understand much about OS-Linux programming but I would like to know if it is possible to change some parameters, settings and interface. Hi Marco, you can find more info here: https://tails.boum.org/contribute/how/code/ -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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: Add support for curl (does ALL_PROXY fix it?)
On 08/03/2023 18:12, sajolida wrote: I wanted to try adding curl by default to see the impact on the image size but ... it seems to be installed already: https://gitlab.tails.boum.org/tails/tails/-/commit/8aa013f3b549d90609fb2a4dd7e2bd14e3439151 ah! thanks for making me notice. I didn't remember, and indeed we don't really use the curl binary itself. I created #19488 to fix this. I'm even more convinced that we should fix that :) @david: Do you want to give it a try? @boyska: Any concern about that since curl is already installed? no specific concern, but of course, this moves the needle towards making it work out of the box. -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] Release schedule for Tails 5.10
On 2/14/23 18:47, boyska wrote: On 2/14/23 14:56, intrigeri wrote:> intrigeri (2023-02-13): Things are still in flux, but at this stage it seems we'll need the manual QA to happen on Tuesday (late afternoon / evening UTC) or Wednesday (morning UTC). … or rather Wednesday (afternoon / evening UTC) or Thursday (morning UTC). Or maybe even later: TorBrowser is preparing new builds, so the one we were testing right now are not the one we will ship. forget about it: 12.0.3-build1 was good enough, so tomorrow morning we can start releasing -- boyska ___ 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] Release schedule for Tails 5.10
On 2/14/23 14:56, intrigeri wrote:> intrigeri (2023-02-13): Things are still in flux, but at this stage it seems we'll need the manual QA to happen on Tuesday (late afternoon / evening UTC) or Wednesday (morning UTC). … or rather Wednesday (afternoon / evening UTC) or Thursday (morning UTC). Or maybe even later: TorBrowser is preparing new builds, so the one we were testing right now are not the one we will ship. I'll try to keep you posted. -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] Question: Intel SGX disabled in BIOS
On 2/9/23 19:24, Ashutosh Pandey wrote: does tails use SGX?? I don't think so. -- boyska ___ 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] Little support question
On 2/10/23 20:31, neal caffrey via Tails-dev wrote: Hi I’m new to tails and am having some trouble? Hi neal, thanks for using Tails. This (tails-dev) is not the user support address. You can refer to https://tails.boum.org/support/ to find ways to fix your problems. -- boyska ___ 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: Add support for curl (does ALL_PROXY fix it?)
On 2/6/23 19:00, David A. Wheeler wrote: oh yeah, we all like curl. I wonder what kind of user needs curl, though. You mentioned that some packages in Debian will "just work" if curl is working. Can you name any of them? I think that would be very valuable info! Sorry, what I meant was, "I expect that some packages in Debian will "just work" if curl is working". I don't have a specific list. However, we try to add feature to Tails when they are improving something for our personas (see https://tails.boum.org/contribute/personas/ ). In this specific case, I think we don't have an example of how can curl, directly or indirectly, help our personas. It's really easy to add the configuration you propose to Tails. But it will add to our QA process: if we tell our users that they can expect curl to work fine, we'd better test it regularly! All in all, the cost is low but not negligible, while the benefit for our personas seems to be zero. So my personal opinion is that it's not worth it *until* there is a clear use case that is helped by supporting curl. Bye, -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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: Critical Usability Issue due to which I Haven't Used Tails in Years
Hi, Tails runs without any swap space (obviously, to maintain amnesia), the entire system may lock up at any moment due to heavy memory usage and opening of many Web browser tabs (which I usually do), the Magic Sysrq functionality of manually invoking the OOM killer in such emergency situations is disabled by default in Tails (and there's no way to enable without rebooting, and it's not recommended to enable it when connecting to the Internet as it's insecure), and Tails bundles no userspace early OOM daemon enabled out-of-the-box (such as systemd-oomd). *The very least you can do is ship a new version of Tails *with a slightly modified configuration value under /proc *to enable the Magic Sysrq-F key combination*. I request that you also consider shipping *systemd-oomd enabled by default* in the next major release of Tails (i.e. version 6.0). Thanks for the suggestion. Would you mind explaining in what kind of scenarios relying on Linux kernel built-in OOM killer gave you a bad UX? I have a USB flash drive with Tails, installed using Tails installer, with an encrypted persistence, up-to-date as of around 2019-2020, with an early (stable) version of Tails 4.x if I remember right. My question is this: Can I do a manual upgrade to the latest stable version of Tails 5? yes *Should I back up my encrypted persistence *before doing anything, yes -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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: Add support for curl (does ALL_PROXY fix it?)
On 04/02/2023 20:18, David A. Wheeler wrote: Currently Tails includes and supports wget. I propose *also* adding support for curl. Curl is widely-used and is the "go-to" tool for many people at the command line. Thus, including it would make Tails more convenient for some. In addition, enabling curl would make a number of added packages in Debian "just work", oh yeah, we all like curl. I wonder what kind of user needs curl, though. You mentioned that some packages in Debian will "just work" if curl is working. Can you name any of them? I think that would be very valuable info! -- boyska ___ 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] xfce, second option graphic interface in tails?
On 2/1/23 16:54, David A. Wheeler wrote: I suspect even people with stronger computers would appreciate snappier response & more resources for "actual work". If it involves removing extensions or other services by default, that's less running code to worry about. I haven't checked anything out in Tails specifically, but there are various guides that might be useful: * https://linuxhint.com/memory_optimize_gnome/ * https://askubuntu.com/questions/1266498/gnome-shell-is-taking-a-lot-of-ram Thanks for this research! Their most practical suggestion is to "trim extension", which we did. By the way, we have regular QA tests to check that Tails is usable with 2GB of RAM. While I'm all for saving resources, I don't think it's realistic to bring down the requirement to 1GB. The best we can do is to try hard to not bump the requirement to 3GB. -- boyska ___ 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] Release schedule for Tails 5.10
Hi, Tails 5.10 should be released on February 14. intrigeri will be the RM Dear manual testers, please let tails...@boum.org know how much QA you can do on February 14 (afternoon/evening CET) Cheers! -- boyska OpenPGP_signature Description: OpenPGP digital signature ___ 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] Tor Browser 12.0.2 Candidate Builds Available
On 1/17/23 21:52, Richard Pospesel wrote: Hello All, Tor Browser 12.0.2 release candidate builds are now available for testing: thanks for pinging us! ___ 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] Tor
On 1/16/23 11:06, jakob.brannstrom via Tails-dev wrote: Dear sirs and ladies! Please, if I have questions about the tor hops and circuits, whom would you direct me to? Hello, Tor user support page is https://support.torproject.org/ bye, -- boyska ___ 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] Release schedule for Tails 5.8
Hi, Tails 5.8 should be released on December 20. we still don't know who will be the RM. Dear manual testers, please let tails...@boum.org know how much QA you can do: - preferably on December 19 (afternoon/evening CET) - if needed, on December 20 (morning CET) Cheers! -- boyska signature.asc Description: PGP signature ___ 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] Release schedule for Tails 5.7
intrigeri: Tails 5.7 should be released on October 22. boyska will be the RM. November 22 :-) -- boyska signature.asc Description: PGP signature ___ 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] Release schedule for Tails 5.6
Hi, Tails 5.6 should be released on October 25. intrigeri will be the RM. Dear manual testers, please let tails...@boum.org know how much testing you can do: - preferably on October 24 (afternoon/evening CEST) - if needed, on October 25 (morning CEST) Cheers! -- boyska signature.asc Description: PGP signature ___ 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] Javascript question
Ahmed Chakik via Tails-dev: Hi, if I connect to VPN first then start Tor browser with javascript enabled to visit a clearnet website, can javascript see my true IP address? Thanks VPNs are not supported in Tails. See: https://tails.boum.org/support/faq/#vpn -- boyska ___ 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] Release schedule for Tails 5.5
Hi, Tails 5.5 should be released on September 20. I will be the RM. Dear manual testers, please let tails...@boum.org know how much testing you can do: - preferably on September 19 (afternoon/evening CEST) - if needed, on September 20 (morning CEST) Cheers! -- boyska ___ 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] Release schedule for Tails 5.4
boyska: Tails 5.4 should be released on August 23. I will be the RM. this is getting postponed by some day. I don't exactly know *when* this will happen. The current best bet I can make is August 25. Dear manual testers, please let tails...@boum.org know how much testing you can do: - preferably on August 22 (afternoon/evening CEST) - if needed, on August 23 (morning CEST) this accordingly changes to: - preferably on August 24 (afternoon/evening CEST) - if needed, on August 25 (morning CEST) bye -- boyska ___ 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] Release schedule for Tails 5.4
Hi, Tails 5.4 should be released on August 23. I will be the RM. Dear manual testers, please let tails...@boum.org know how much testing you can do: - preferably on August 22 (afternoon/evening CEST) - if needed, on August 23 (morning CEST) Cheers! -- boyska ___ 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] Tails report for June 2022
TAILS REPORT FOR JUNE 2022 [1] Here are a few highlights about what we did in May, among many other things: * Our helpdesk email [2] now has auto-reply (#17935 [3]). * Improved the UX of _Tor Connection_: people that were "exploring" the interface going back and forth used to find the wrong boxes to be automatically checked #18546 [4] * We partecipated in Tor hackweek. It was very fun and very useful! * We implemented QR code scanning #18219 [5]. This seems to work, but it still isn't ready for inclusion. * We added support for Snowflake #5494 [6]. Again, this is a PoC: it's nice to see it working, but don't expect it to be released so soon. RELEASES Tails 5.1 was released on June 4 [7]. It fixed an important security vulnerability [8], but it also brought many improvements, among which: * Improvements for users who leave east of UTC: _Tor Connection_ now automatically fixes the computer clock if you choose to connect to Tor automatically; also, the time displayed in the top navigation uses the time zone selected when fixing the clock in _Tor connection_. * _Unsafe browser_ got a new homepage, which makes it easier to understand how to sign in to the local network using a captive portal. After that, Tails 5.1.1 was released on June 23 [9] as an emergency release. METRICS Tails has been started more than 772283 times this month. This makes 25742 boots a day on average. Links: -- [1] https://tails.boum.org/news/report_2022_06/ [2] https://tails.boum.org/support/index.en.html [3] https://gitlab.tails.boum.org/tails/tails/-/issues/17935 [4] https://gitlab.tails.boum.org/tails/tails/-/issues/18546 [5] https://gitlab.tails.boum.org/tails/tails/-/issues/18219 [6] https://gitlab.tails.boum.org/tails/tails/-/issues/5494 [7] https://tails.boum.org/news/version_5.1/index.en.html [8] https://tails.boum.org/security/prototype_pollution/index.en.html [9] https://tails.boum.org/news/version_5.1.1/index.en.html___ 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] 11.5a13 release candidate builds
Richard Pospesel: >Hello! Hello Richard! >I just sent out the email to tor-qa, but you can find unsigned release >candidate builds for the next alpha here: nice, thanks! Having more time to test major releases is always useful to us :) >If all goes well, the next major stable release 11.5 will be pretty >close to this + some minor bug fixes. 11.5 is *scheduled* for June >5th, but I honestly expect that to slip given some of the craziness at >the end of this Month. You mean July 5th, right? :) Indeed that's what I see on https://nc.torproject.net/apps/calendar/p/Dy5spytzmYoJPieT/dayGridMonth/now However, on that same calendar, I don't see the TorBrowser release corresponding to Firefox ESR 91.11, to be released on June 28th. We were assuming that a TorBrowser release would have been prepared on June 28th; should we change our plans? bye! -- boyska ___ 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] 11.5a13 release candidate builds
Richard Pospesel: Hello! Hello Richard! I just sent out the email to tor-qa, but you can find unsigned release candidate builds for the next alpha here: - https://tb-build-05.torproject.org/~richard/builds/alpha/unsigned/11.5a13-build1/ nice, thanks! Having more time to test major releases is always useful to us :) If all goes well, the next major stable release 11.5 will be pretty close to this + some minor bug fixes. 11.5 is *scheduled* for June 5th, but I honestly expect that to slip given some of the craziness at the end of this Month. You mean July 5th, right? :) Indeed that's what I see on https://nc.torproject.net/apps/calendar/p/Dy5spytzmYoJPieT/dayGridMonth/now However, on that same calendar, I don't see the TorBrowser release corresponding to Firefox ESR 91.11, to be released on June 28th. We were assuming that a TorBrowser release would have been prepared on June 28th; should we change our plans? bye! -- boyska signature.asc Description: PGP signature ___ 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] Release schedule for Tails 5.2
intrigeri: tails-manual-testers@, please tell boyska how much manual QA you'll be able to do for 5.2 (likely June 27, later afternoon CEST; and/or June 28, earlyish morning CEST). ping! -- boyska ___ 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] Very concerned about messages while attempting to shut down.
James Griffin: I have tails 5.1 and when I attempted to shut down, it did not shut down completely and I received the following messages on a black screen: [SKIP] ordering cycle found, skipping WPA supplicant [SKIP] ordering cycle found, skipping prepare namespaces [SKIP] ordering cycle found, skipping network manager [SKIP] ordering cycle found, skipping anonymizing overlay network [SKIP] ordering cycle found, skipping wait for Tor to have bootstrapped I have no idea what this means but it doesn't sound good. Should I be concerned? I had turned off my wifi in tails prior to this; would this have had something to do with it? Hello, and thanks for reporting this! For sure the fact that Tails was not shutting down properly is not nice. Does this happen often? If so, can you give us more details? Anyway, those messages are not worrying: you're just seeing the system logs. bye! -- boyska ___ 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] Release schedule for Tails 5.1
Hi, Tails 5.1 should be released on May 31. intrigeri will be the RM. Dear manual testers, please let tails...@boum.org know _how much_ manual testing you do on May 30 (evening CEST) and May 31 (morning CEST). Thanks in advance! Cheers! -- boyska signature.asc Description: PGP signature ___ 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] Release schedule for Tails 4.30
Hi, Tails 4.30 should be released on May 3. I will be the RM. Dear manual testers, please let tails...@boum.org know _how much_ manual testing you do on May 2 (evening CEST) and May 3 (morning CEST). Thanks in advance! Cheers! -- boyska ___ 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] Tails report for February 2022
Tails report for February 2022 [1] We have refactored our installation [2] documentation! This is one of the results of user research we are doing (#18074 [3]). We believe this will make installation easier, encourage more people to verify Tails image, and improve the SEO of it. You can read all the details on #16808 [4]. We're actively working on releasing Tails 5, based on Debian Bullseye, soon. We published calls for online training and user research in Mexico [5] and in Brazil [6]. RELEASES Tails 4.28 was released on March 08 [7]: This was mostly a bugfix release, with upgrades to the Linux kernel, Tor Browser and tor METRICS Tails has been started more than 717702 times this month. This makes 25632 boots a day on average. Links: -- [1] https://tails.boum.org/news/report_2022_02/ [2] https://tails.boum.org/install/ [3] https://gitlab.tails.boum.org/tails/tails/-/issues/18074 [4] https://gitlab.tails.boum.org/tails/tails/-/issues/16808 [5] https://tails.boum.org/news/ciclo_de_autodefensa_digital_mexico/ [6] https://tails.boum.org/news/ciclo_de_autodefensa_digital_brasil/ [7] https://tails.boum.org/news/version_4.28/index.en.html___ 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] Release schedule for Tails 4.29
Hi, Tails 4.29 should be released on April 5. I will be the RM. Dear manual testers, please let tails...@boum.org know _how much_ manual testing you do on April 4 (evening CET) and April 5 (morning CET). Thanks in advance! Cheers! -- boyska ___ 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] Release schedule for Tails 4.28
intrigeri: Tails 4.28 should be released on March 8. At this point we don't know who the Release Manager for that release will be. I will be RM for 4.28 -- boyska ___ 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] Python 3.10? ...
OLIVER BELL: Hi, I’m very sorry to disturb you. hi! I’m wondering why the browser breaks when I install python 3.10.0 from source. I have to compile it because it isn’t available through apt. I’m pretty sure I compile correctly. I didn’t want to alter apt sources in any wayI’m not confident to securing apt properly. I don't know the exact answer to this, but yes, I don't expect that every python program in Tails is 3.10-compatible. We never tested that. -- boyska ___ 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] Release schedule for Tails 4.27
Hi, Tails 4.27 is scheduled for February 08. intrigeri will be the Release manager. Dear manual testers, please tell tails...@boum.org how much manual testing you can do on: - February 7, later afternoon CET - February 8, morning CET 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] Release schedule for Tails 4.26
anonym: Tails 4.26 is scheduled for January 11. We haven't decided who is gonna be the release manager yet. I will be. Release will begin on Monday 10. -- boyska ___ 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] Novice using Tails after looking for answers to a Tor Error in Tails (no issues when using Tor without Tails)
Sheridan Thorn: Hi there! hello! Tails set up at Greenwich time, which used to work just fine. Now "Error connecting to Tor" with the one and only viable option for me is to Fix the Clock (which doesn't seem like a good idea). [...] 2. Wary about fixing the clock as it identifies my time zone thanks for explaining your concern! Fixing the clock is actually *not* a security problem at all (quite the contrary): those informations are only used by the system internally, and never sent to anyone else. 3. Issue is persistent and requires manual changes each time I enter Tails. Indeed this is a known usability problem. 5. IF I don't use default bridges, the one attempt I tried allowed access. Still...not helpful for what I want to do. Let me see if I understood correctly: - if you connect to Tor directly, it works without setting the clock - if you connect to Tor with default bridges, it will fail. If you fix the clock, it will then work - you prefer using default bridges for security reasons The choice is yours, but from my security perspective the two options as being equivalent: you are not hiding that you are using Tor. Default bridges are only used because sometimes they can evade censorship when a direct connection wouldn't work. When you need to hide the fact that you are using Tor, you need to choose the appropriate option in the "Tor Connection" window. See https://tails.boum.org/doc/anonymous_internet/tor/#index3h1 What I did: Verified after download - reinstalled twice on new stick (of 3 usb sticks, 1 is kingston and the other 2 are sandisk cruzer blade I use an att gateway, and did not see adjustments to allow unsafe browsers, yet will look again. Unfortunately I don't know what an "att gateway" is. Would you mind explaining? Any suggestions or links for me, please? Alternative safety measures I could try out? I'm sorry but I'm not sure I got what exactly you are trying to be safe from, so I don't know how to help you. cheers -- boyska ___ 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] Release schedule for Tails 4.24
Hi, Tails 4.24 is scheduled for November 2. We haven't fully decided who is gonna be the release manager yet: I am listed as RM in the calendar, but this might change. Dear manual testers, please tell tails...@boum.org how much manual testing you can do on: - November 1, later afternoon CET - November 2, morning CET 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] Bridges
Gilles: I have received 2 Tor bridges but I have a message « Tor connection error » when trying to use it. Hello, thanks for your feedback! It's very useful to us. Are you using 4.21? 4.22~rc1? or an older version? Have you any advice concerning this event ? Yes! If you are using 4.22~rc1, you can use the "Fix Clock" button, set the appropriate timezone and local time, and see if that works. You can also try using one bridge only instead of two. If one fails, then try the other one. I know that's boring, we are tracking this in https://gitlab.tails.boum.org/tails/tails/-/issues/18298 Please report to us how that goes! -- boyska ___ 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] Release schedule for Tails 4.22~rc1
Hi, Tails 4.22~rc1 is scheduled for August 19. Yes, this is very soon! I will be the release manager. Dear manual testers, please tell tails...@boum.org how much manual testing you can do on: - August 18, later afternoon CEST - August 19, morning CEST Cheers! -- boyska ___ 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] Keybase
laroc via Tails-dev: is it possible to implement Keybase(chat tool)? hello, thanks for the suggestion! This is not planned, so don't expect it to happen anytime soon. But if you think we should consider it, would like explaining why you would love this to be included in Tails? bye bye -- boyska ___ 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] Wont connect to tor
lees lees: Hello, After the new update (4.21) i keep on having an issue when connecting to tor, even when i try to put the bridge i receive over email. hello lees lees! thanks for reporting this, this helps us prioritizing work. Some questions: - 4.21 is not out yet. Do you mean 4.20? - Were you using bridges on earlier versions? - Can you connect without bridges? - When you use Tails, is your clock ahead of the GMT time? I know this is a strange question, but yes, this is important for us. bye, -- boyska ___ 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: migrate our public chat rooms to another friendly XMPP server (#17956)
intrigeri: FWIW I was asked such questions on esiliati.org, but not when I joined tails-...@chat.disroot.org. Perhaps someone else had created that MUC already? If it's one of us and they can transfer ownership when it'll be time to set up the ACLs, great. Else, we have a problem. boyska, ignifugo, can you confirm whether one of you currently "owns" tails-...@chat.disroot.org? me and you are listed as the owners of that room. The same applies to ta...@chat.disroot.org -- boyska signature.asc Description: PGP signature ___ 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: migrate our public chat rooms to another friendly XMPP server (#17956)
intrigeri: We can do those in parallel: a. start testing disroot.org chat rooms. intrigeri, can you be the one creating the chat rooms? As far as I understand it, in this context "creating" is essentially equivalent to "being the first to join". true. that, and setting all the right settings for the room (title, description, access control settings, history...) However, I tried to join ta...@chat.disroot.org and got an error: "Could not connect to chat.disroot.org". I understand you successfully tested this sort of things already at disroot.org, so perhaps you know better than me how to do it? ooops, I can reproduce it. I tested the server a bit, and it worked, but indeed tails@ is behaving differently than other room names. I'm writing to disroot.org staff -- boyska ___ 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: migrate our public chat rooms to another friendly XMPP server (#17956)
intrigeri: I have also dubts about esiliati.org, I'm not sure that is more than a person, I used some of their tools, but I used safely only the stateless service. They have not explicit policy, not founding plan, not decision making, not comunication channel with the users. for what I know... maybe someone can say that I'm wrong... please. On the one hand, you know that project better than I do, so I'm inclined to trust your judgment (although I have difficulties balancing it with boyska's, so perhaps you 2 can sort it out? :) we did. The discussion was long, but I feel it was useful. What are we asking? --- Our ideal server is well maintained, has a commitment to be maintained for "long time" (we don't know how much that really is; 5 years?), is run by a vibrant community, has an help desk that actually helps users in many languages (which ones? eurocentrism is a problem!), the availability of such an help desk is well communicated to users. Deciding if having an help desk is important was hard to do; it is not clear if any user will complain with the MUC server if something doesn't work. Perhaps they'll complain with their XMPP provider? or with us? we aren't really sure, but help desk is clearly a bonus point. Having a clear policy is also appreciated. Is there anything like that? --- the esiliati.org vs systemli.org was stuck. One was lacking in user support, the other was lacking in commitment over long time. This tie was broken observing that we had problems joining and talking in some systemli.org chat room. Maybe that was just the wrong day? but that was it: as of now, systemli.org falls off the list of candidates. We found that disroot.org runs an XMPP server that apparently works well. Of course more testing is good, but at least a first batch of joining channels and talking was done. Their website has multi language support. It's still mostly european languages, but that's the best we could find. They have some support channels advertised. So everything seems good with them, except we don't know much about their commitment with XMPP over the next years. Our proposal --- We can do those in parallel: a. start testing disroot.org chat rooms. intrigeri, can you be the one creating the chat rooms? b. ask them about their future plans. I can do that. By next week, or shortly after, we'll draw a conclusion. If both (a) and (b) are good, then disroot.org will be the winner! As for timings: the deadline of August 1 is approaching. It's a hard deadline, meaning that the server will be shut down after that. But is not as hard in terms of the consequences for the Tails project: one week without public channel is not the end of the world. with love, -- boyska ___ 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] How to build tails for testing purposes?
Hans: If I commit my personal changes to git, as you requesting, then (please correct me, if I am wrong) my changes will change the sources in github, what is the last thing I want to do. I still do not even know, if this, what I want to do, is really working. At the moment I am trying things, step by step. And I want to be sure, these things are only done on my own systems. This must be confirmed. sure! there is no way you can accidentally change Tails' sources like this. so feel free to experiment and don't worry about it :) -- boyska ___ 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] Problems with 4.2
N Pitceathly: I have upgraded 4.19 to4.2 and have unfortunately struck problems signing into Tor. I like to keep my anonymity so have usually signed in using Tor bridges added and have presumed that's what happened. With 4.2, I am unable to connect in anyway other than a straight connection. ooops, sorry to hear that, and thanks for reporting us! I understand you were already using bridges with 4.19, right? I have emailed Tor for bridges, and copied then into the space allocated for them, but there is always an error message. Also, once I get an error message there is no way to go back so that I can change my method of connecting to straight through. Let's see if we can understand why this happens: - have you copied the whole (very long) bridge line? an example is obfs4 76.74.178.195:9443 406A8B5869B72221036291407EC3688C69995F80 cert=FY2R16JOoE2VNCU2gVLWBj6Gg+YBP7mTLU5zl12Fz9iC5TQG6SqE71CFhD3zIuJcEFrcMQ iat-mode=0 - is Tails clock accurate? Is it more than an hour greater than UTC? https://time.is/UTC unfortunately we have this bug which might affect you if this is the case: https://gitlab.tails.boum.org/tails/tails/-/issues/15548 bye! -- boyska ___ 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] Unable to connect on tor
Odran Ligneul: Hello there, hello, and thanks for sharing your feedback with us! I just updated my tails with the most recent version and I need now to configure my Tor. I am using my personal WiFi without any issues in the past and now, I am not able to connect on tor anymore. I used different bridges downloaded from your website and your email addresse but none of them work when I enter them, I always get the "error connecting to tor" were you already using bridges before, with other versions of Tails? I think you hit this bug: https://gitlab.tails.boum.org/tails/tails/-/issues/15548 the good news is that we are working on it :) the bad news is that there's not much you can do about that, right now. Since I am not using a public or a corporate network, I should not struggle to connect on tor right ? If you use the "easier" option on Tor Connection first choice, that should work for you, then, and fix the problems you are seeing. But keep in mind that *will* reveal that you are using Tails. see https://tails.boum.org/doc/anonymous_internet/tor/index.en.html for more info on this choice. bye! -- boyska ___ 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] Socks5 is missing on tails 4.20
wpajsk6sjq via Tails-dev: Hello, I just updated tails to 4.20. When I configute the tor bridge, the option to conect a sock5 or http option are missing. hello! Place, tell me how to do it on tails 4.20, or I will lose the ability to use tail conecting network thanks for sharing your experience. Don't worry, you can still connect to Tor using Tails! - at the first screen, select whatever option you find more appropriate - type the bridge that you want to use - press Connect to Tor - you will get to an error screen. from this error screen, you can click on a button to configure socks proxy - click on Connect to Tor again and that should now be working! if you find this is inconvenient, and want to share your thoughts... your suggestions are really welcome! bye -- boyska ___ 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: migrate our public chat rooms to another friendly XMPP server (#17956)
intrigeri: I have also dubts about esiliati.org, I'm not sure that is more than a person, I used some of their tools, but I used safely only the stateless service. They have not explicit policy, not founding plan, not decision making, not comunication channel with the users. for what I know... maybe someone can say that I'm wrong... please. On the one hand, you know that project better than I do, so I'm inclined to trust your judgment (although I have difficulties balancing it with boyska's, so perhaps you 2 can sort it out? :) well, I can't say that any of this is far from true. But is there any requirement we have that esiliati.org is missing? 1) https://www.systemli.org/en/service/xmpp/ - https://jabber.systemli.org/ (https://compliance.conversations.im/server/jabber.systemli.org/) It was indeed the other candidate. Quoting details from the blueprint: - happy to host us - XMPP server will run another 2+ years but not forever. - They host a (beta as of today) Matrix server. - They can help us transition to Matrix when their XMPP server goes away. I think what made the difference was commitment. Although no realistic project is going to ever promise that any service will last _forever_, esiliati.org gave us a commitment of working to keep it functional to our needs as they care about XMPP a lot, and that XMPP is not easily going away. Personally, I'm OK with migrating these 2 chat rooms to systemli.org. I have no strong objections, too. -- boyska ___ 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: migrate our public chat rooms to another friendly XMPP server (#17956)
syster via Tails-dev: The compliance tester says some XEP's that are recommended are missing. Some of them might not bring a feature to a Tails user, while others might. This is the test: https://compliance.conversations.im/server/esiliati.org/ The single part that bugs me the most is XEP-0313: MAM + MUC. This was among our requirements. However, I think I've seen that working on that server, so I wonder if results are accurate. I've notified esiliati.org's sysadmins about it, asking them to please check if MAM + MUC works. -- boyska ___ 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: use a Label instead of a Milestone to track our roadmap
sajolida: Last year, we encoded the items on our roadmap using the Milestones %2021 and %2022: The problem is that we lose this information as we assign issues to the version numbers that we use as milestones to organize our work on a shorter time frame. right. I propose that we change this to using labels, for example ~2021 instead of %2021. This way, changing milestones wouldn't lose the roadmap info. It would make it easier to track and evaluate progress without having to go back to the canonical version of the roadmap from Mural. seems good to me. -- boyska ___ 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] NSA tails and closed code
Georg Koppen: anonym: Romper Stomper via Tails-dev: and why are there closed codes in “tails”? I guess you are referring to the firmwares required for hardware support? If we didn't ship these firmwares Tails would not run on most hardware. It's a necessary trade-off. Is there a list of those firmwares somewhere (I couldn't find anything on the Tails website about that topic after searching a bit) or is it "just" a Debian package taken 1:1 from upstream? https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-packageslists/tails-common.list#L247 this is the list of debian packages Tails installs to have firmwares -- boyska ___ 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: use the "Reviewer" field in GitLab MRs
intrigeri writes: A few months ago, GitLab Inc. open-sourced the "Reviewer" feature for Merge Requests. This allows keeping track _independently_ of: - Who's responsible for bringing the MR to completion: the Assignee. - Who's responsible for reviewing the MR: the Reviewer. Some teams have been experimenting with this workflow in the last months, instead of our previous — and still documented — workflow in which we would assign a MR to its Reviewer. The feedback that came my way has been entirely positive so far. yay, it's very nice to be able to easily distinguish MRs in which you are the "author" and MRs in which you are the reviewer. I think it's now time to make a decision and adjust either our documented process or our actual practices to match it. I propose we start using the "Reviewer" field in MRs, as described above and in the GitLab documentation. sure! Zen Fu: Another thing that could be explicitely documented is whether a reviewer should/could merge code after a review or not. This may differ from team to team because not always the assignee has privileges to merge. Maybe we could explicitely say when we expect the reviewer to merge? Or maybe the MR should then be re-assigned to someone that can actually merge? I don't think we need to make this very complex, but as it's a question that has popped up for me I'm raising it here. I don't think we need to dive into full details here (per-team conventions, plus written words on the issue itself can help!) but my understanding is that setting $person as reviewer means that $person needs to do something on this MR. It's typically review, but in some cases it might be merging or what not: in such cases, a comment explaining what $person is asked to do is probably enough. -- boyska ___ 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] [brainstorm] What are our public XMPP chat rooms useful for? (#17956)
intrigeri: The server we currently use for our public XMPP chat rooms will stop operations later this year. First, I would like to better understand what these public chat rooms are currently useful for, for our project and its contributors. This will help decide whether we keep public chat rooms at all. And if we do, it'll tell us what we expect from such a service. My feeling is that tails-...@conference.riseup.net is a good place for people that want to mostly lurk, see that there's "something ongoing" and know that they can step-in when they want to contribute somehow in an informal manner. I'm not a fan of bringing most activity to private places, but I agree that is hard to find a specific answer to this question: What new problems would we face if we did not have any public chat room? ... but let me try: - Usecase "wet your feet". If someone wants to contribute to tails, I think that the current best way to make questions about typical problems related to building, testing, etc. is tails-dev room. Where should we point his/her if we lose this room? - Usecase "collaboration with dev of other projects". Let's say that A is a developer of the ever-important software FooBazzer. She finds that there is something that she'd like to discuss with us: for example, she wants to remove a feature that we currently use; or is interested in knowing if we are interested in some improvements. What opportunities does she have? - GitLab! But, are people comfortable with filing issues for things that are not bugs but just discussions? - Tails-dev ML. Though mailing lists are definitely slower than instant messaging, they also work better on different timezones and are still a viable way of doing so. have a nice week! -- boyska ___ 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] Getting rid of review'n'merge email on this list
On 04/05/2015 17:35, intrigeri wrote: > Besides, I bet that some list subscribers would be glad if such > notifications were opt-in. Hello, I'm a lurker on this mailing list, therefore my opinion is barely important. I actually read 10% of such review'n'merge emails with interest. It's a good way for me to follow what's going on, take a look at the code, etc. > A) Decide that the Atom feed is good enough and document it, with its >aforementioned limitation (so that people can adjust their config). >I volunteer to do that if we decide to go this way. > > B) Decide that it's not good enough, and then look into a push >notification solution. Or, set up a dedicated mailing-list that >a rss2email instance will email. That rss2email will need to run as >often as reasonably possible, so that it misses as few Ready for QA >tickets as possible.. any of these solutions will be just as good for me. -- boyska gpg --recv-keys 0x58289ca9 ___ 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] GNOME Keysign 0.2 released
On Thu, Jan 08, 2015 at 03:49:27PM +0100, Tobias Mueller wrote: As you might know, GNOME Keysign tries to make OpenPGP Keysigning an easy task. It attempts to be as "one-click" as possible, while following best practises. hey, that's interesting! In the same spirit, you could have a look at https://github.com/boyska/coffer/ which tries to solve only the "get every other key" part of the keysigning. It is not mature, not widely tested, not user friendly, etc. but you may find it useful anyway. look at https://github.com/boyska/coffer/blob/master/README.rst#many-to-many--a-command for how it can be useful for gpg keysigning! If you think it can be useful, then be assured that I will make it even easier to use it as a library. I'm interested in opinions and feedback. unfortunately I do not have the time to test&review it properly. But I am very interested in something like this, so I'll look it better, sooner or later. -- boyska ___ 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] git (submodule) security
On Sat, Nov 01, 2014 at 08:07:04AM +, Patrick Schleizer wrote: By chance I found https://github.com/boyska/git-verify repo. hey, that's me :P as you can see, it's a very simple script. I'm not completely sure that it works exactly as I expect, and I am not even sure that what I expect for "verification" is what everyone would. I'd like to do some unit tests about the code, but it is quite hard/boring to do that. Any contribution about better code, better testing, etc will be really appreciated. Actually, I was very surprised to not being able to find some script similar to what I wrote. At Whonix we're currently discussing various aspects of git security. Especially since git still uses SHA-1 and if git (submodule) verification is safe against adversaries, that can produce SHA-1 collisions. Seems a really good point, but... can't you just recursively run git-verify? I was wondering, if you might be interested to join the discussion? [1] I am really interested, thanks for sharing! -- boyska ___ 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 broken due to expired key (Tor#12988)
On Fri, Aug 29, 2014 at 10:06:44AM -0700, intrigeri wrote: I think all Tails builds are currently broken due to: https://trac.torproject.org/projects/tor/ticket/12988 I can confirm that builds of Freepto are broken, too! -- boyska ___ 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] Fwd: [tor-talk] carml: tasty treats from your Tor
On Sun, Aug 03, 2014 at 07:55:55PM +0200, intrigeri wrote: I would really love feedback on whether the "downloadbundle" command is doing the right thing with certificate-checks. well, that seems _really_ interesting. In our meeting at HackIT we considered that "finding a better way to put torbrowserbundle inside the ISO would be great. torbrowser-launcher --batch-download is what we'd like". I know, I assigned it to me, but it was really a pain, and it went down on my priorities. While I still am interested in patching torbrowser and making it far less dependant from UI... I will experiment with carml! -- boyska ___ 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] Good news wrt. nested virtualization
On 18/07/2014 14:59, intrigeri wrote: > FWIW, Intel Haswell architecture adds features (Shadow VMCS, nEPT) > that, when using a recent enough qemu/kvm, make nested virtualization > actually usable to run our test suite. Works fine for me :) we're also experimenting with nested virtualization. For what I could see, it basically works, but actually I have not done extensive testings, nor I managed to setup tails unit tests inside a virtual machine. > The bad news is that one needs a super-recent Intel CPU to take > advantage of this. Others will still need to either run the test suite > directly on their usual system, or to get a dedicated machine to > run it. I think there's room for colaboration at a "hardware level", then ;) We have one of those. -- boyska gpg --recv-keys 0x58289ca9 ___ 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] minutes of a tails/freepto meeting
At hackmeeting we had some good chat about sharing more work between freepto&tails (and, if possible, any other distribution). I'll be sketchy here. Low-hanging fruits are good to enjoy the benefits of sharing things without getting into too much complicated projects. Packaging small shell scripts or simple parts of the distribution is probably a good example of that. For example, we'd like to package the "random nick chooser". We also talked about how to share "hooks" or other parts of live-build process, and our conclusion was that there is no simple way to do that, and it isn't that much important, since they're typically very short and simple scripts. On configurations = Iceweasel - We observed that preconfiguring applications can be ugly, and tried to see what we could do about that. The most problematic seems to be mozilla's one, since their complex configuration, multiple databases, embedded plugins can make that a nightmare. We decided not to write any wrapper script to create configurations: it would add complexity without making the configurations process considerably simpler. Freepto has one binary extension (Disconnect) and will try to get that into debian: RFP are cool! SQL files should be transformed into SQL scripts. Mumble -- mumble has a sqlite-based configuration; instead of copying the sqlite file, it's better to create it with a script TorBrowser: TBB and TBL === We discussed the benefits and cons of having a "launcher" (TBL) instead of the whole TBB inside the image. Of course putting it inside will ensure shorter 'opening' times; this is especially true for live systems. We ended up saying that having the TBL pre-downloading the TBB during image building (with a chroot-hook) would be the best solution. Boyska volounteered on that: this would require something like torbrowser-launcher --batch-download To make TBL more robust, we also need to get in touch with TBB sysadmins, to ensure a sane way of getting the latest browser and signature. Unit testing Unit tests are cool, tails has, and freepto wants them, too! We also would benefit from running daily builds which (in case of error) will send notification email: this will ensure that no change in debian is breaking the build. Hosting === We don't like github, so we need to find a better hosting. This could require a different organization. Boot persistence-media - persistence-media=removable-usb is not very reliable: it will not work on some usb sticks (sandisk). The proposed way of doing this is using a syslinux hook to append a cmdline parameter that clarifies which disk we're in to the initramfs (which does not have udisk to inspect it). Then, we should change live-boot method of filtering devices. Intrigeri is working on the first part (changing syslinux), while boyska will work on the live-boot part. EFI --- ... but freepto has TWO boot loaders (grub for EFI). We decided to move everything to syslinux. This will bring us: * less maintainance * more similar to tails * cleaner (.efi images are inside git code, right now!) * support for the persistence-media hack explained above. I think that's all, I surely forgot something, but it's anyway a lot of stuff. Cheers! -- boyska ___ 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] Sharing wiperam package between Freepto and Tails?
On Thu, May 15, 2014 at 12:46:11PM +0200, vinc3nt wrote: but the equivs (or similar stuff) configuration files are still missing it's all a bit "raw", but some "tar + ar" will do its job. I don't know why ono-sendai did it that way, but it's not difficult to change. By the way, just for this reason we have not included it in freepto repository, yet. So solving this is required for freepto, too. Or, each of our project could take care of hosting their binary package, and we would "only" share maintenance of the source package. the last option sounds good for me.. probably create a new dedicated repository would result in additional effort. completely agree. -- boyska ___ 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.