The situation for most of the projects I am involved in, is that they want to install Tails to a VM/virtual disk image, not to a physical USB.
The situation(s) where the physical USB is relevant, is where we want to boot the physical Tails USB into a virt-manager VM, meaning that those have to move away from Virtualbox as that one cannot boot easily from physical media. This is desired when wanting to use/run/update Tails from/on the main computer/laptop, and subsequently use the updated Tails directly on another computer, either in such a VM setup, or by booting from the physical USB stick.
But yes, more and more are blocking and moving away from USB...
Just my 2c.
--
Regards,
Teqleez
On Tue, Oct 1, 2019, at 13:30, linux-service wrote:
> More and more organisations prevent (and disable) usb and sd ports on
> notebooks. So booting tails with usb is no option.
>
> Would this be good practice to use tails by booting the iso (on the
> internal disk) with grub to ram. When tails is running, the present
> harddisks are not mounted.
>
> so, Download official tails iso from the tails website, gpg verify the
> iso and after this booting the iso with grub.
>
> for example with(warning, not working):
>
> wget
> https://mirror.alpix.eu/tails/tails/stable/tails-amd64-3.16/tails-amd64-3.16.iso
> wget https://tails.boum.org/torrents/files/tails-amd64-3.16.img.sig
> wget https://tails.boum.org/tails-signing.key
> gpg --import tails-signing.key
> TZ=UTC gpg --no-options --keyid-format long --verify
> /iso/tails-amd64-3.16.img.sig /iso/tails-amd64-3.16.iso
> if [ $? -eq 0 ]
> then
> yad --width=220 --title "**Iso verified**" --text "Iso is
> verified" --button="OK"
> else
> yad --width=220 --title "**Iso not verified**" --text "Iso is
> not
> verified" --button="OK"
> fi
> _______________________________________________
> Tails-dev mailing list
> Tails-dev@???
> https://www.autistici.org/mailman/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to
> Tails-dev-unsubscribe@???.
>
