Re: [Tails-dev] How to build tails for testing purposes?
Sorry, it is me again. There is so much to learn. I am now able· to get clear
with these
vagrant, rake and virsh stuff. That is a great step and I am happy, I can help
myself now.
But I believe, I now stumbled over a new issue with broken package. For me it
looks like
some settings are wrong in the pre-image file. As far as I understood, the
crash is in the
step, where the basic image is build, or say, filled with the packages.
This is the output, just at the basic installation step:
- snip --
I: Configuring gnupg...
I: Configuring tasksel-data...
I: Configuring tasksel...
I: Configuring libc-bin...
I: Configuring systemd...
I: Base system installed successfully.
P: Begin caching bootstrap stage...
P: Begin unmounting filesystems...
P: Setting up cleanup function
P: Begin caching chroot stage...
P: Begin mounting /dev/pts...
P: Begin mounting /proc...
P: Begin mounting /sys...
P: Configuring file /etc/debian_chroot
P: Configuring file /sbin/start-stop-daemon
P: Configuring file /usr/sbin/policy-rc.d
P: Configuring file /usr/sbin/initctl
P: Configuring file /etc/hosts
P: Configuring file /etc/resolv.conf
P: Configuring file /etc/hostname
P: Configuring file /bin/hostname
P: Configuring file /etc/apt/apt.conf
P: Configuring file /etc/apt/sources.list
gpg: WARNING: unsafe permissions on homedir '/root/.gnupg'
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: agent_genkey failed: Inappropriate ioctl for device
gpg: key generation failed: Inappropriate ioctl for device
cp: cannot create regular file 'cache/': Not a directory
P: Begin unmounting filesystems...
real4m14.338s
user1m14.028s
sys 0m19.934s
+ kill -9 10276
+ cleanup
+ [ -n /tmp/tails-build.Tj3YvUfU ]
+ cd /
+ remove_build_dirs
+ + tac
old_build_dirs
+ mount
+ perl -ni -E say $mountpoint if (($mountpoint) = ($_ =~
m{^(?:tmpfs|devpts-live|proc-
live|sysfs-live) on (/tmp/tai
ls-build(?:-tmpfs)?\.[/[:alnum:]]+)}))
-i used with no filenames on the command line, reading from STDIN.
+ sudo rm -rf /tmp/tails-build.Tj3YvUfU
No build artifacts were found!
- snap --
Ok, the directory here called /root is not the /root of my system, so it must
be in the
imagefile, that is mounted /dev/loop (I suppose so, am I wrong?).
What I do not understand, is that ioctl, but everything is looking for me as a
problem with
rights. However, I am building as root, so I should have all the rights, I
need.
I am sure, I have missed something.
For the explanation, I am building on an extra ssd, which is mounted
to /space, but this worked on building kali-linux. So this should work here,
too. Especially
at this step of building.
Any idea, what I am doing wrong? Or is this just a bug???
Thanks for being so patient.
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.
[Tails-dev] bridges
Hello. There is no place to store the obfs4 bridges in my Tor browser; the instructions about Settings, Tor, Store a bridge don't apply to my Tor browser. Since I do not have persistent storage setup, not sure how I could store the obfs4 bridges anyhow. Could possibly write-in the obfs4 at start-up but they are kind of long. Thanks, Aristophrenes ___ 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 Upgrade
I think Tails should have a BLANK homepage. Loading a website with Javascript enabled is EXPLOIT FRIENDLY NO website should be loaded, Javascript should be Disabled, Security shield maximum or at least medium/Safer by default. ___ 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 4.20
Hello, I can not at all deal with new version, can you help me and write step by step what I should do? Kind regards OpenPGP_0xCA9B0C1329097254.asc Description: OpenPGP public key 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?
Hans: 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. The proper way to reset and start over is to run: rake clean_all 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. The basebox in ~/.vagrant.d are unpacked and the virtual machine images imported by libvirt and stored somewhere else, hence the "already created" above. List images with: virsh -c qemu:///system vol-list default Detele with: virsh -c qemu:///system vol-delete --pool default VOLUME_NAME So I suspect you will fix your issue with: virsh -c qemu:///system vol-delete --pool default tails-builder-amd64-buster-20210710-de2318f3ae_vagrant_box_image_0.img 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. I believe you! Our documentation about this is a bit lacking, and naturally we'd be thrilled to receive your patches improving them! :) OTOH, I don't think there was any good reason for you to start over like you did. Good luck! ___ 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)
Hi, ignifugo (2021-07-19): > On 19/07/21 14:17, intrigeri wrote: >> ignifugo (2021-07-19): >> In the future, I would be grateful if you could do minimal fact >> gathering, before you express such judgments: as you can see above, >> since you did not do that, facing public accusations, I felt urged to >> do that homework myself, which I find unfair. > > yes, you are agree. I have to put more attention to search information > in the gitlab. In general. It's true. Well, in this case, what I meant with "minimal fact checking" is reading the email thread you're replying to, and following the links it contains. To be clear, I don't expect anyone to *search* for such information when it's my job to make it readily available :) > sorry that I bothered you. Thanks! I appreciate this. [slightly reordering quotes to answer similar topics in 1 single place: ] > My opinion was related to "replace XMPP with..." and I thought from your > tone (so probably really opinable, sorry), that there was a concrete > plan to drop xmpp and you feel unhappy to lost time now deciding on xmpp > platform because we have to drop soon. But is not the real future... and > present. > […] > Ah, ok so drop XMPP is not in the possibility and not in a short future. > it is? > […] > So we are choose again for a long time," a solid public platform for > xmpp chat "... There's no concrete plan indeed. We did not have this conversation yet so nobody can tell for sure if/when we're going to migrate away from XMPP (altough if we pick systemli.org, this does tip the balance quite a bit — see below). I personally wish we'll migrate both our public and internal chat rooms away from XMPP within a year or 2, which indeed makes me want to spend the least possible amount of work on picking the XMPP server we'll migrate to next week: I need my work to be meaningful to me. > to clarify I think that you put a lot of attention to record every step > and I appreciated a lot you in this. :) > Or 2) move to systemli.org .. that: > […] > - a nice an running service xmpp :P … for another couple years but maybe not much longer ⇒ sooner or later this will give us a deadline to migrate away from XMPP (unless we pick another server again, but please let's not do that again in 2 years!), which IMO is a benefit, but I would understand if some other people saw it as a drawback. > I'm available to start test on this. Great! If you or someone else wants to test this by the end of the week, you need to be aware that one needs a systemli.org account to create a chat room (MUC) on their server. ___ 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.
