Ihor Radchenko <yanta...@posteo.net> writes: > Joseph Turner <jos...@ushin.org> writes: > >>> You probably meant to link to some different ticket here. >> >> https://todo.sr.ht/~ushin/ushin/188 > > So, you want an equivalent of `org-safe-remote-resources'.
For now, we've added a command `hyperdrive-mark-as-safe`, which causes automatic major modes activation when opening a file in a "safe" drive: https://ushin.org/hyperdrive/hyperdrive-manual.html#Mark-a-hyperdrive-as-safe https://git.sr.ht/~ushin/hyperdrive.el/commit/1e9b892e87979d3da5e9a1f04d0255a620500214 `org-file-contents' and `org-safe-remote-resources' already work with hyperdrive.el. We just need to figure out a way to treat #+SETUPFILE: /foo/bar.org as #+SETUPFILE: hyper://CURRENT-DRIVE-PUBKEY/foo/bar.org since the latter already works. Perhaps this link conversion will work when we implement magic file name handlers. :) > Generally, we might eventually move it to Emacs core, making a more > general Emacs safety framework with unified preferences. > But someone™ has to do this job. As usual. Yes, a general Emacs safety framework would be an improvement. Thank you for helping thinking through these security concerns! Joseph
