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] 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] How to build tails for testing purposes?
Sadly this does not work. Although it is now building, my changes are ignored. So it does install gnome again although it is commented out in tails-common-list, and it did not install XFCE, which I put into this file. Additionally the deb-package, I put below ~/chroot_local-packages/ is not going to be installed (maybe, because XFCE is not installed, as kali-undercover.deb needs got XFCE dependencies). Before build, I started export TAILS_BUILD_OPTIONS="ignorechanges" but got no success. My changes are ignored. I also tried export TAILS_BUILD_OPTIONS="ignorechanges nomergebasebranch rescue keeprunning" but again got no success. Same result as before. What do I do wrong? Is there anything I have to do, so that my downloaded gittree accepts and recognizes my changes? I do not understand, how the build is working. The doc says, it is using live-build from debian, so it should work similar to it and look into the configuration files (also those, I changed), but obviously, it is looking somewhere else. Thanks for any help. Best reagrds Hans > > > As the output tells you, you need to set TAILS_BUILD_OPTIONS: > > > > signature.asc Description: This is a digitally signed message part. ___ 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: Additionally the deb-package, I put below ~/chroot_local-packages/ is not going to be installed (maybe, because XFCE is not installed, as kali-undercover.deb needs got XFCE dependencies). The chroot_local-packages feature has frequently been broken, but I suspect there is another problem... Before build, I started export TAILS_BUILD_OPTIONS="ignorechanges" but got no success. My changes are ignored. I also tried In your previous email I see that you did some changes inside the tails folder without committing them to Git. Tails will only include changes that are in Git, and will refuse to build when you have uncommitted changes -- the ignorechanges option is just for disabling that check (only recommended if you know what you are doing), and proceeds to build without those uncommitted changes. If you are not too familiar with Git, you can try this (at the root of your tails folder) to add all files to Git: git add . git commit -m "Did some stuff" And then just `rake build` as usual. 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] How to build tails for testing purposes?
Am Dienstag, 20. Juli 2021, 13:49:47 CEST schrieb anonym: > In your previous email I see that you did some changes inside the tails > folder without committing them to Git. Tails will only include changes that > are in Git, and will refuse to build when you have uncommitted changes -- > the ignorechanges option is just for disabling that check (only recommended > if you know what you are doing), and proceeds to build without those > uncommitted changes. > > If you are not too familiar with Git, you can try this (at the root of your > tails folder) to add all files to Git: > > git add . > git commit -m "Did some stuff" > > And then just `rake build` as usual. > > Cheers! Ok, I could do this. But does this not kill the original stuff? My purpose is, to build my own tails version with XFCE and kali-undercover and without gnome. Just to make it as small as possible. 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. Best Hans signature.asc Description: This is a digitally signed message part. ___ 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] How to build tails for testing purposes?
Hans: Am Dienstag, 20. Juli 2021, 13:49:47 CEST schrieb anonym: In your previous email I see that you did some changes inside the tails folder without committing them to Git. Tails will only include changes that are in Git, and will refuse to build when you have uncommitted changes -- the ignorechanges option is just for disabling that check (only recommended if you know what you are doing), and proceeds to build without those uncommitted changes. If you are not too familiar with Git, you can try this (at the root of your tails folder) to add all files to Git: git add . git commit -m "Did some stuff" And then just `rake build` as usual. Cheers! Ok, I could do this. But does this not kill the original stuff? Nothing is ever lost when using Git. :) It keeps the history of how files have changed. My purpose is, to build my own tails version with XFCE and kali-undercover and without gnome. Just to make it as small as possible. Understood. That is compatible with the instructions I gave you above. However, removing Gnome is likely very hard. I suggest you install XFCE in addition to Gnome to save you tons of work (potentially weeks, I'd guess). Are saving ~100 megabytes really worth it? :) 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. Don't worry, your local changes are not published anywhere by default (that requires the `git push` command). And you do not have permission to publish changed on Tails' GitLab any way. :) 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. That's awesome! "Try, fail, repeat" is a surefire recipe for learning! :) If you didn't already, have a look at HACKING.mdwn for some quick explanations of how to modify Tails! 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] Unable to connect on tor
Now putting Odran in copy as they might not be subscribed to the mailing list. boyska: > 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? Also, which options did you choose in the Tor Connection assistant? Could you tell us in more details what you did and what happened? > 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 Odran is telling us that they had no problem before 4.20, I'm tempted to think that this is rather another occurrence of: https://gitlab.tails.boum.org/tails/tails/-/issues/18481 >> 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. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing 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] Problems with 4.2
Now putting Neil in copy since they are not subscribed to tails-dev. 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! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing 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] How to build tails for testing purposes?
Yeah, yeah, sigh, it's me again
Now I am running into a new issue, but I believe, something external happened.
For learning I removed all the downloaded things completely. Then I deleted
also
~/.vagrant.d/ in my home and started from the beginning with a new git clone
and a new,
but unchanged build.
But now there is a new issue, related to vagrant. Please take a look at the
last output.
snip -
/tmp.debootstrap-gnupg-i9oekjha
*==> box: Box file was not detected as metadata. Adding it directly...*
*==> box: Adding box 'tails-builder-amd64-buster-20210710-de2318f3ae' (v0) for
provider: *
box: Unpacking necessary files from:
file:///space/tails-linux/tails-amd64/tails/tails-
builder-amd64-buster-202
10710-de2318f3ae.box *==> box: Successfully added box 'tails-builder-amd64-
buster-20210710-de2318f3ae' (v0) for 'libvirt'!*
Bringing machine 'default' up with 'libvirt' provider... *==> default: Creating
image
(snapshot of base box volume).*
Volume for domain is already created. Please run 'vagrant destroy' first.
rake aborted!
VagrantCommandError: 'vagrant ["up", "--provision"]' command failed with exit
status 1
/space/tails-linux/tails-amd64/tails/Rakefile:113:in `rescue in run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:110:in `run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:703:in `block (2 levels) in '
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `'
Caused by:
CommandError: command ["vagrant", "up", "--provision", {:chdir=>"./vagrant"}]
failed
with exit status 1
/space/tails-linux/tails-amd64/tails/Rakefile:78:in `run_command'
/space/tails-linux/tails-amd64/tails/Rakefile:111:in `run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:703:in `block (2 levels) in '
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `'
Tasks: TOP => build => vm:up
(See full trace by running task with --trace) *==> default: Domain is not
created. Please
run `vagrant up` first.*
snap
I wasa not lazy, and searched the web. vagrant destroy does not work, and
vagrant
global-status is telling me, there is no session running.
And I repeat: I did everything from scratch, reinstalling vagrant and its
dependencies,
reinstalling the git-tree and so on.
As everything worked before, and I made no changes, the only conclusion is,
that
something external must have changed. Something, I have no influence on.
If I am wrong, please apologize, any help is appreceated.
Best regards and happy hacking.
Hans
signature.asc
Description: This is a digitally signed message part.
___
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.
