So I converted a usb live linux install (Tails) from USB to virtualbox using VBoxManage convertfromraw. For it to boot in virtualbox, I need to remove one thing from the boot commandline (live-media=removable). This option is not in the usual /etc/default/grub or grub.d locations. I did find it in: /lib/live/mount/medium/syslinux/live.cfg. I'm not sure how that ends up in the grub commandline. In fact, there is nothing in /boot/grub except unicode.pf2, so I think there is some other mechanism going on here. This is EFI, also. I'm reluctant to run update-grub in case this command line is being put together in a different manner.

I'm running Tails. - Can't use the settings menu to do it, there's only one option there and it's like 600x800 which is the problem, I think - Can't figure out what the display name is for my monitor, have tried using w but it tells me my console's not wide enough to do it. I cannot make the window bigger because of my screen resolution. It already looks huge. - All the solutions I've found involve using xrandr, but I need to know the display name of my monitor to do them. I have run out of ideas.

im getting this error while booting tails from a usb stick. i tried the same usb with another laptop it works fine. but trying with my asus g14 its not working, the error is shown in the screenshot. please help. thankyou :)

I am trying to create bootable live tails usb. I downloaded tails-amd64-6.10.img from here . I verified the download: I used balena etcher and got this error: - Since it did not work, I also downloaded from torrent but still same error. - I used different usb but still same error. I tried using ventoy. ventoy does not see the image file. I put kali linux iso file into the ventoy and ventoy recognized it when I booted.

The latest tails comes with nodejs v10.24.0. Trying to get tails to run a newer node has been unsuccessful even after running script from deb.nodesource.com/setup_14x which said buster was unsupported. I think updating node was a red herring anyway. npm is not included so I use

apt install npm

to install npm. I get version 5.8.0. I need npm to install create-react-app and other node tools. All npm commands return warning Npm does not support node.js v10.24.0 (hence the red herring to update that) In persistant storage I create a directory "foo" and cd to foo, I run

init

And then

install

And in addition to the warning above it seems to fail to connect to registry.npmjs.org:443 with getaddrinfo EAI_AGAIN Putting that url into the tor browser connects just fine. My current working theory is that I need to configure npm proxy and npm https-proxy, but for that I seem to require proxy credentials, url, and port. I don't know what those are or how to find them in tails. I am not behind any other proxy besides tor running in Tails. Question: how to make npm work in tails.

I tried to download [Tails](https://en.wikipedia.org/wiki/Tails_(operating_system)) on my computer, however, I couldn't do it because in grub there were 2 errors: > error:/live/vmlinuz has invalid signature > > error: you need to load the kernel first Can anyone please help me with that because I have no idea what to do.

I am trying out [Tails](https://tails.net/index.de.html) and disabled the [MAC address randomization](https://tails.net/doc/first_steps/welcome_screen/mac_spoofing/index.en.html#index5h1) feature during boot, but when doing ip addr in the terminal, the MAC address of wlan0 (WiFi adapter) keeps changing regardless. This is extremely annoying and means e.g. that I cannot access WiFi hotspots employing a MAC filter. Is there any way to disable this feature e.g. from a root terminal and force Tails to use a static MAC address?

I've been trying for days to connect a live [Tails](https://tails.net/) system to a mobile WiFi hotspot on an Android 9.0 device without success. What I have done so far: 1. Set up a mobile WiFi hotspot in Android protected by a WPA2 password and MAC filtering 2. Boot Tails with the MAC address anonymization feature disabled 3. Read out the hostname and static MAC address of the Tails system by doing cat /etc/hostname and ip link, respectively 4. Using the hostname and MAC address, add the Tails system to the hotspot's white list of allowed devices 5. Try to connect to the hotspot using its SSID and WPA2 password Step 5 keeps failing with the error message > Connection failed > > Activation of network connection failed I quadruple-checked every single setting, checked and changed the WPA2 password, tried disabling MAC filtering, switched between 2.4 GHz and 5.0 GHz, switched between visible and hidden SSIDs etc., all without success. There are zero issues connecting other Linux systems to the exact same hotspot using exactly the same procedure, and I also have been connected to other public WiFi networks using this exact Tails system before. FWIW, the network controller according to lspci -v | grep "Network controller" is Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) What am I missing here? Is there a way to get some real-time, verbose terminal output with detailed error messages etc. from the WiFi adapter while it is trying to connect?

I downloaded the official tails 6.6 image file [here](https://tails.net/install/windows/index.en.html) . And followed all the steps mentioned and made my bootable usb drive. But when I booted it on my laptop it did not boot for hours. I checked the log by pressing Escape and saw this in the console -

134.00170 systemd: modprobe@dm_mod,service: Deactivated successfully. I l34.004731 systemd: Finished modprobe@dm.mod.service - Load Kernel Module dm_mod► t ","N I Finished modprobe@dm.mod.service - Load Kernel Module dm_mod. I 1 .013,S21 systemd: modprobeOefi_pstore.service: Deactivated successfully. I 134.0141111 ,stemd[11: Finished modprobellefi_pstore.service - Load Kernel Module efi.pstore► t I Finished modprobeeefi_pstore.service - Load Kernel Module efi_pstore. [ 1314.01.5.66$1 systemd: modprobeeloop.service: Deactivated successfully. t 134.416171] systemd: Finished modprobe@loop.service - Load Kernel Module loop. t Q I Finished modprobOloop.service - Load Kernel Module loop. t 134.0184831 systemdt11: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmoty./sys/fs/pstore). t 134.018M systemd: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. t 134.1782451 systemd: Finished ferm.service - ferm firewall configuration. [ OK I Finished ferm.service - ferm firewall configuration. t 134.1796611 skistemdfl]: Reached target network-pre.target - Preparation for Network. I _ I Reached target network-pre.terget - Preparation for Network. 134.236501] systemd: Starting networking.service - Raise network interfaces... Starting networking.service - Raise network interfaces-t 134.3795861 sd 0:0:0:0: Attached scsi generic sg0 type 0 134.526498] systemd: Finished networking.service - Raise network interfaces. [ OK I Finished networking.service - Raise network interfaces. I Job systemd-journald.service/start running (1min 26s / 1min 26s) ] Job systemd-journald.service/start running (1min 31s / lmin 31s) [ 226.102265] systemd: systemd-journald.service: State 'stop-sigterm' timed out. Killing. [ **,] Job sastemd-journald.service/start running (lmin 37s / 1min 37s) [ .1,] Job systemd-journald.service/start running (1min 42s / 1min 42s) [ 236.602216] systemd: systemd-journald.service: State 'final-sigterm' timed out. Killing. I , ] Job systemd-journald.service/start running (lmin 47s / 1min 47s) [ 241.852215] systemd: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 241.854586] systemd: systemd-journald.service: Failed with result 'timeout'. [ 241.858583] systemd: systemd-journald.service: Unit process 646 (systemd-journal) remains running after unit stopped. [FAILED] Failed to start systemd-journald.service - Journal Service. See 'systemctl status systemd-journald.service' for details. [ 241.865415] systemd: systemd-journald.service: Scheduled restart job, restart counter is at 1. [ 241.866111] systemd: Stopped systemd-journald.service - Journal Service. [ OK ] Stopped systemd-journald.service - Journal Service. [ 241.867922] systemd: systemd-journald.service: Found left-over process 646 (systemd-journal) in control group while starting unit. Ignoring. [ 241.867927] systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 241.905246] systemd: Starting systemd-journald.service - Journal Service... Starting systemd-journald.service - Journal Service... [ 241. 29] systemd-journald: File /run/log/Journal/Bafbee1b601542bb908b095e9aef3d91/system.journal corrupted or uncleanly shut down, renaming and replacing. [ ] Job systemd-journald.service/start running (1min 11s / lain 30s) [ 332.102488] systemd: systemd-journald.service: start operation timed out. Terminating. [ 337.352241] systemd: systemd-journald.service: State 'stop-sigterpe timed out. Killing. [ 337.354842] systemd: systemd-journald.service: Killing process 11 (systemd-journal) with signal SIGKILL. [ ] Job systemd-journald.service/start running (lmin 40s / imin Os) [ ] Job systemd-journald.service/start running (lmin 45s / lmin 45s) [ 347.852233] systemd: systemd-journald.service: State 'final-sigterm' timed out. Killing. [ 347.855173] systemd: systemd-journald.service: Killing process 4031 (systemd-journal) with signal SIGKILL. [ ] Job systemd-journald.service/start running (lmin 50s / imin 50s) [ 353.1019721 systemd: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode. [ 353.104411] systemd: systemd-journald.service: Failed with result 'timeout'. [ 353.107123] systemd: systemd-journald.service: Unit process 646 (systemd-journal) remains running after unit stopped. [ 353.: .1 systemd: systemd-journald.service: Unit process 4031 (systemd-journal) remains running after unit stopped. [FAILED] hailed to start systemd-journald.service - Journal Service. See 'systemctl status systemd-journald.service' for details. [ 353.116852] systemd: systemd-journald.service: Scheduled restart job, restart counter is at 2. [ 353.117378] systemd: Stopped systemd-journald.service - Journal Service. ] Stopped systemd-journald.service - Journal Service. [ 353.124921] systemd: systemd-journald.service: Found left-over process 646 (systemd-journal) in control group while starting unit. Ignoring. [ 353.124934] systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [ 353.125005] systemd: systemd-journald.service: Found left-over process 4031 (systemd-journal) in control group while starting unit. Ignoring. [ 353.125017] systemd: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 353. 1 systemd: Starting systemd-journald.service - Journal Service... Starting systemd-journald.service - Journal Service... 353.167892] systemd-journald: File /run/log/journalaafbee1b601542bb908b095e9aef3d91/system.journal corrupted or uncleanly shut down, renaming and replacing. 1 Job systemd-journald.service/start running (29s / lmin 30s)

Basically it is stuck in exiting and then retrying to start the systemd-journald.service. I tried different usb slot and drives with no success. When I tried to boot in a different laptop I was greeted with

shim SBAT data failed: Security Policy Violation
Something has gone seriosuly wrong: SBAT self-check failed: Security Policy Violation

I have tried enabling and disabling secure boot and fast startup. I am only booting Windows 11. And my device is Asus ROG Zephyrus G14 2021. Thank You

when the user read thier section of the Persistent Storage he will see they explain about Dotfiles as a way to save configurtion of the apps can it save the log in in websites or it just save the prefecne of useing the app so how can I use dotfile feature if the dotefile feature can not used to save log in so please suggest for me a distro that is live os (which only run from flash and dont fromat my laptop ) and at the same time save my logs

Running the latest Tails I have attached my hard-drive that got automatically mounted. However it seems only to be read-only. Is there a way to mount it in read/write ? Or is this not possible since the file system is Apple HFS/HFS+ ?

I want to install Tails on my Hard Drive alongside Kali Linux. So I installed Kali on the system and prepared Grub2. I also created a partition of 3GB for my Tails installation, formatted it to FAT32, named it Tails and dded the tails archive onto it. Now I went to my grub.cfg and put in the lines from the Tails grub.cfg file. Additionally I created a partition with the name "TailsData" of additional 3GB. Now, if I go to my bootloader, I may select Kali as well as Tails. Booting into Kali works fine, but now if I try to boot into Tails it rejects me with initramfs telling me

unable to find a medium containing the live file system

Now for the sake of helping out I inserted in grub.cfg the UUID of the partition as a fix - as it may never ever change... Still I do not get into the system, since I googled this issue I found lots and lots of initramfs errors like mine but none of them seems to fit my case unfortunately... Additional Data: This is my live64.cfg which is loaded to extend syslinux.cfg

include menu.cfg

label live
	menu label Tails 5.19.1
	kernel /live/vmlinuz
	append initrd=/live/initrd.img boot=live ignore_uuid config live-media=removable nopersistence noprompt timezone=Etc/UTC splash noautologin module=Tails slab_nomerge slub_debug=FZ mce=0 vsyscall=none init_on_free=1 mds=full,nosmt page_alloc.shuffle=1 randomize_kstack_offset=on  quiet
	sysappend 0x40000

label livefailsafe
	menu label Tails (Troubleshooting Mode)
	kernel /live/vmlinuz
	append initrd=/live/initrd.img boot=live ignore_uuid config live-media=removable nopersistence noprompt timezone=Etc/UTC splash noautologin module=Tails slab_nomerge slub_debug=FZ mce=0 vsyscall=none init_on_free=1 mds=full,nosmt page_alloc.shuffle=1 randomize_kstack_offset=on  noapic noapm nodma nomce nolapic nosmp
	sysappend 0x40000

#label floppy
#	localboot 0x00

#label disk1
#	localboot 0x80

#label disk2
#	localboot 0x81

#label nextboot
#	localboot -1

Here I added

- but it doesn't change my outcome... Here is my grub.cfg

set root='(hd1,4)'
	search --no-floppy --fs-uuid --set=root ***UUID-XYZ***
	echo "Loading the Linux kernel..."
	linux /live/vmlinuz initrd=/live/initrd.img boot=live config live-media=removable nopersistence noprompt timezone=Etc/UTC splash noautologin module=Tails slab_nomerge slub_debug=FZ mce=0 vsyscall=none init_on_free=1 mds=full,nosmt page_alloc.shuffle=1 randomize_kstack_offset=on FSUUID=***UUID-XYZ*** quiet
	echo "Loading the initramfs..."
	initrd /live/initrd.img
	echo "Booting..."
	boot

If more information is needed, please ask. Note: For now I managed to run the ISO file through Grub... But the ISO may not access the "tailsData" partition for now.

Like the title, I want to make 32-bit program run on the 64-bit Tails OS, so I download a package named ia32-libs_2020.05.27_amd64.deb, then dpkg it, but it did't work, the terminal said I should install many packages like gtk2-engines-murrine:i386 and gvfs:i386. However, the Tails4.0 can't install those i386 package... So what should I do?

When Tails OS boots, you can press tab to modify the startup options. Is there any way I can save an iso with these options already set? It's a real pain to have to press tab and set them up every time. Surely there must be a better way?

Tails OS is distributed either via .iso or .img file. The only .img can have persistent storage, but only .iso can be mounted to VirtualBox and properly booted. I would like to have VirtualBox Tails machine with persistent storage and ability to install 3rd parties software. Below is what I did. In couple of words I decided to use flash drive emulator. I'm on Ubuntu 18.04. I built dummy_hcd.ko for my kernel and got flash drive via $ sudo modprobe dummy_hcd $ fallocate -l 8GiB /path/to/flash-drive-file $ sudo modprobe g_mass_storage file=/path/to/flash-drive-file idVendor=0x1d6b idProduct=0x0104 iManufacturer=Myself iProduct=VirtualBlockDevice iSerialNumber=123 Then I expand Tails OS .img file to that drive by using dd as to usual USB flash drive via issuing following (/dev/sdd is my virtual flash drive) $ dd if=tails-amd64-3.13.2.img of=/dev/sdd bs=16M After that I got /dev/sdd1 partition that I can mount and see the image content. It's size is exactly equal to tails-amd64-3.13.2.img file size. Then I created .vmdk VirtualBox file tied to /dev/sdd via $ sudo VBoxManage internalcommands createrawvmdk -filename ~/usb.vmdk -rawdisk /dev/sdd I created new virtual machine and selected this .vmdk file, and started it. Unfortunately, while booting it complaints to insufficient disk space and stop booting. I took gparted and resized this partition. gparted shows me a message where suggests to fix GPT table I accepted it. The same parted does. Warning: Not all of the space available to /dev/sdd appears to be used, you can fix the GPT to use all of the space (an extra 14364672 blocks) or continue with the current setting? Fix/Ignore? Fix Model: Linux File-Stor Gadget (scsi) Disk /dev/sdd: 8590MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 1235MB 1234MB fat32 Tails boot, hidden, legacy_boot, esp And after that (it's only enough to apply GPT fix and not actually use unallocated space) I, unfortunately, get this message from kernel. I suppose that it can't find the root file system to mount and continue booting init process from this file system maybe. But the shell is available and rootfs is mounted to ramdisk and can be listed.

*For major version upgrades, Tails recommends this convoluted upgrade path where you write an image on a fresh USB drive, then clone the OS partition onto your original USB drive. I'm trying to figure out a better way to do it:* I have a .img file that contains a partition table and a single partition: $ sudo kpartx -av tails-amd64-5.2.img add map loop12p1 (253:0): 0 2553856 linear 7:12 2048 $ sudo parted tails-amd64-5.2.img UNIT b print Model: (file) Disk tails-amd64-5.2.img: 1309671424B Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1048576B 1308622847B 1307574272B fat32 Tails boot, hidden, legacy_boot, esp And a drive with two partitions: $ sudo kpartx -av /dev/sdb add map sdb1 (253:2): 0 16777216 linear 8:16 2048 add map sdb2 (253:3): 0 43655168 linear 8:16 16781312 $ sudo parted /dev/sdb UNIT b print Model: Kingston DataTraveler 3.0 (scsi) Disk /dev/sdb: 30943995904B Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1048576B 8590983167B 8589934592B fat32 Tails boot, hidden, legacy_boot, esp 2 8592031744B 30943477759B 22351446016B TailsData I would like to restore the image over top of the first partition on that drive and leave the second partition untouched. I tried this command and the result will boot to GRUB but not the OS: $ sudo dd if=tails-amd64-5.2.img of=/dev/sdb1 bs=16M According to fsck, that's because the GPT partition is at the start. This command does nothing: $ sudo kpartx -d tails-amd64-5.2.img This command results in a drive that doesn't even boot to GRUB: $ sudo dd if=tails-amd64-5.2.img of=/dev/sdb1 bs=512 count=2 Is there a way to strip the GUID partition table and make this work?

[An issue](https://github.com/aforensics/HiddenVM/issues/22) was recently opened on the GitHub page for the privacy-focused VirtualBox wrapper HiddenVM. The opener posts what he claims to be indication of files from his local cache being sent to an external IP: > When i used dmesg i saw what it did in the background. I picked two > messages out of many: > > audit: type=1400 audit(1651914430.711:1128): apparmor="DENIED" operation="open" profile="torbrowser_firefox" > name="/home/amnesia/.cache/thumbnails/large/3678dc849747c84908498dd948db8f71.png" > pid=10995 comm="pool-firefox" > requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 > > Dropped outbound packet: IN= OUT=wlan0 SRC=i removed the adress DST=i removed the adress LEN=48 TC=0 HOPLIMIT=255 FLOWLBL=762031 > PROTO=ICMPv6 TYPE=133 CODE=0 UID=0 GID=0 > > So it looks like it sent files from my cache to some address. Like why > does a script that is supposed to change settings open cache files and > sends them somewhere? The opener doesn't say exactly what commands they used or give any further details. Do these two messages indicate files being sent from the local machine to an external IP?

I've been trying to run a wallet app in tails os ver 4.28 with no success. I'm getting denied error when using it with proxychains. Being a noob here, would someone assist me in letting me know what I'm doing incorrect here. I've included terminal & proxychain config info for reference here. amnesia@amnesia:~/Persistent$ chmod +x Neuron-v0.101.2-x86_64.AppImage amnesia@amnesia:~/Persistent$ proxychains ./Neuron-v0.101.2-x86_64.AppImage ProxyChains-3.1 (http://proxychains.sf.net) |S-chain|--127.0.0.1:9050--127.0.0.1:8114--127.0.0.1:9050-|DNS-request| localhost -127.0.0.1:8114--127.0.0.1:9050--127.0.0.1:8114-|DNS-request| localhost -127.0.0.1:9050-|DNS-request| localhost -127.0.0.1:8114--127.0.0.1:9050--127.0.0.1:8114-|DNS-request| localhost -127.0.0.1:9050--127.0.0.1:8114--127.0.0.1:9050--127.0.0.1:8114--127.0.0.1:9050-|DNS-request| localhost -127.0.0.1:8114--127.0.0.1:9050--127.0.0.1:8114--127.0.0.1:9050--127.0.0.1:8114-|DNS-request| localhost <--denied ^C|DNS-response|: localhost does not exist Aborted proxychain.config file #dynamic_chain strict_chain #random_chain #chain_len = 2 #quiet_mode proxy_dns # Some timeouts in milliseconds tcp_read_time_out 15000 tcp_connect_time_out 8000 [ProxyList] # add proxy here ... # meanwile # defaults set to "tor" socks4 127.0.0.1 9050 Appreciate any assistance in this matter.

I've had Tails OS installed on a USB drive for a couple of years. This summer an update made it unable to boot. I installed a fresh Tails OS after formatting the drive, and then realised that I never written the seed to my crypto wallet outside of Tails (I should have known better, I know). I'm not very experienced with data recovery tools, but I believe I can recover the wallet with some guidance, but I can't find anything online that has helped yet. I don't know if this is even possible, but I will offer a reward to anyone who's able to help me recover the wallet. Thanks!

I have a bootable USB drive with Tails and Kali Linux on it, among others. Kali boots fine. However when I try to load Tails, it manages to get past the Tails loading screen but then the Kali logo appears and freezes, making me reboot. It comes to a screen that looks like this However instead of "kali" it says "debian". Any ideas what's wrong?