Re: [Tails-dev] I lost all my data on my back SSD drive
Am Mittwoch, 23. März 2022, 05:33:38 CEST schrieb Imnotgivingyoumyinfo via Tails-dev: Huh, that hurts. My advice: Do nothing else with this harddrive! I would secure the status as early as possible! Put the ssd into another computer, boot with a linux livefile system, then make an image of it to another harddrive like /dev/sdc1 dd if=/dev/sda of=/dev/sdc1/some_directory/myimage.dd So you can use this image for recovery. If everything fails, you may contact me directly. But to help further on, I would need to get the drive to me to have a closer look. Alternative you can upload the imagefile to megaupload.com or some other site. You can encrypt the file before upload and only sent trusted people the password. Sorry, at the moment I can not tell any more. Best regards Hans > I made a huge mistake uploaded the .img on my personal 500GB Samsung SSD > with all my personal belonging. I'm freaking out. I didn't pay attention to > what I was doing. There has to be a way to recover the lost data but my MAC > isn't even reading my SSD. Please, I beg you to help me! > > Blue > > Sent with ProtonMail secure email. ___ 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?
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.
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.
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?
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?
Ah, ok, this seem to work. I read this message, but understoood it in that way, that this command would ignore my changes. Building a tails live system is made in another way, like I know, so I am not very experienced with it. In the past I built my life-systems mostly with live-build (or ./build.sh when building my own optimized kali-linux livesystem). Thanks for the hint. Best Hans > As the output tells you, you need to set TAILS_BUILD_OPTIONS: > > export TAILS_BUILD_OPTIONS="ignorechanges" 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] How to build tails for testing purposes?
Hi folks, I am experiencing with building my own version of tails, but got stuck. I downloaded the git, installed all needed packages on my debian system, made my changes in ~/tails/config/ and then started rake build && rake vm:halt But this did not work. I got the message: snip You have uncommitted changes in the Git repository. Due to limitations of the build system, you need to commit them before building Tails: M config/chroot_local-packageslists/tails-common.list ?? config/chroot_local-packages/kali-undercover_2021.1.2_all.deb ?? vmdb2.log If you don't care about those changes and want to build Tails nonetheless, please add `ignorechanges` to the TAILS_BUILD_OPTIONS environment variable. Uncommitted changes. Aborting. --- snap - However, I do not want to commit anything yet, because I do not want to mess up with your git-sources! How can I build just for me, without interfering your tails-git? Changes I made: 1. edited ~/tails/config/chroot_local-packageslists/tails-common.list 2. added kali-undercover*.deb into ~/tails/config/chroot_local-packages/ If this is working, I will try to optimize things (maybe also build for 32-Bit). Maybe I will then ask for more help, but first let me try, if I can get it managed to build tails running with XFCE instead of Gnome and the possibility, to look XFCE like Windows10. Thanks for any hints. Best regards 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] Question: Tails in undercover mode?
Hi folks, ok, I have understood, that it is not easy to install a windowmanager looking like MacOS or Windows. Also, you told me, you are using Gnome. Well, thinking about this, please allow me a very personal feedback: 1. The choice of using Gnome is IMO not very lucky. Gnome is big, Gnome is eating much ressources. 2. I would use LXDE or better XFCE, because they are very small and tiny. XFCE also has the advantage, to use the very fine package "kali-undercover", which let XFCE look like Windows10. 3. The lack of TAILS in 32-bit is a great disadvantage, because it can not be used on netbooks, like EEEPC or others. I believe, many people are using these still. However, I agree, that journalists today might use all 64-Bit notebooks. 4. Tails should be for everyone, so it should be small and tiny, so it can be run smoothly also on older hardware. I am sure, especially in poorer countries, people are not able, to buy the newest hardware. Last but not least: Thank you for the documentation, how to build tails. This will allow me, to build a tails version according to my own needs. Of course, there is also much to learn. Generally: Thank you all for the hard work - it is really needed and appreceated in this corrupt world! Best regards 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] Question: Tails in undercover mode?
Dear list, I am wondering, why tails no more get an undercover mode. IMO it is very dangerous for users, if their window manager is not looking like the normal window manager used everywhere, especially in countries, where any "strange" desktop might cause attention on authorities. This problem could be easily solved. Most users are running either windows or MacOS. For windows you can just use XFCE + kali-undercover, for Mac-design there are several windowmanagers available (there is coming ElementaryOS in my mind). As you do only need the window-manager design, there should be no risk change. I might remember, tails got this option some years ago, but somehow this is gone. Dunno why Thanks for reading this, any feedback is welcome. Best regards 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] I would love Tails but...
Dear Tails-Developer,tails is good but it would be much better when you could use Tails"without" USB-Stick. Before I used Tails I used Parted Magic. When Parted Magicis booted you can unmount the USB-Stick and boot the next Computer with this USB-stick.I hope you read this E-Mail and you will work at this.Best wishes from Germany,your "Hans Hack" ___ 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 for added package: paperkey
I haven't touched it in a while since I got stuck while using Tails/squeeze for the uses we need it for. I have submitted a proposal for a project that includes a little work on cleanroom, so I do hope to get back to it in a focused way in the not-too-distant future. For the core use of creating a master GnuPG key and generating subkeys, I think that TAILS already has everything there. opensc is included, right? opensc will probably need to be backported to wheezy then included since they've recently made big strides in making it work a lot easier. For all of the uses that we have for cleanroom, I'm guessing there will be far too many packages to include. For example, we want to do Android signing key management, so that means Java keyrings, so that means default-jdk. But I'll keep this question in mind when I get back into it. .hc intrigeri: Hi, Daniel Kraft wrote (17 Dec 2014 19:29:03 GMT) : I would like to suggest adding paperkey (as in the Debian package repository) to Tails. This is a tool to export the raw secret part of a GPG key, for instance, to back it up on a paper print-out. First of all, thanks for the suggestion! Given this tool seems to be CLI-only, and meant to be rarely used, at first glance it doesn't seem appropriate to be installed by default, and instead advanced users can install it themselves whenever they need it. OTOH: * the manage an offline OpenPGP key with Tails use case would be improved if one could use this tool out-of-the-box, without needing to connect to the Internet and have APT download and install it; * the installed package takes a few dozens kB. Now, this would fit into the use case we've been asked by the cleanroom (Cc'd) folks to include apt-offline for. BTW, it's been waiting for their feedback since 4 months: https://labs.riseup.net/code/issues/7208 Hans-Christoph: it would be super useful if you told us what's the list of additional packages cleanroom needs, that are not provided in Tails yet. Then, we can decide whether we want to install all of them by default, or rely on apt-offline instead. Then, I suspect we'll want to do just the same for paperkey. Cheers, -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 https://pgp.mit.edu/pks/lookup?op=vindexsearch=0x9F0FE587374BBE81 ___ 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] Idea or something
Hi dear tails-team, first of all, I like your cd and think, it is the best way for anonymity. But there is something, I want to suggest to improve security. Although everything is sent over TOR, I think you should make sure, the MAC- address of every network device should be changed at boot. You ca do this by macchanger. Wireless cards and network cards (wlan0 and eth0) should at least got a changed MAC-address, but also should every new device get a new MAC (i think of bluetooth or usb-3g-devices). None of physical information of the used computer should be known to the outside. I do not know, if it is possible, to temporaryly change MAC-addresses of used routers, but this option would be nice, too. And of course (and I guess, this is already implemented) NONE, and really mean NONE services should get access to any parts of the used computer (no services!!!). Has tails a firewall active? (iptables). If yes, it should be completely (and mean COMPLETELY) closed, and should be opened by the user when he is needing it. I imagine a nice GUI choosing a whitelist in an understanding way: Either open ports (for experienced users) or open by description (i.e. sending mail , receiving mail or similar). Whjat do you think? I am looking forward to your answer. Have a nice weekend Hans-J. Ullrich ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
