hi,
anonym, what's the point of forbidding relative source paths such as
"dotfiles" in the first column of live.persist?
E.g.:
$ cat live.persist
gnupg /home/amnesia/.gnupg
=> currently triggers a live-persist error:
Skipping unsafe custom mount with source ${source}: the source must
be an absolute path w.r.t. the persistent media root and cannot
contain "." or ".."
I find it a bit weird. I think there's no such thing as an "absolute
path wrt. the persistent media root", and this makes it harder to deal
with user input on tails-persistence-setup's side, not to mention the
burden on users themselves.
Can we easily and safely remove that requirement, and treat "gnupg"
the same way as "/gnupg"?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
| If you must label the absolute, use it's proper name: Temporary.
_______________________________________________
tails-dev mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-dev
