R4.0 introduces the concept of multiple disposable templates, whereas R3.2 was limited to only one. Similarly to how app qubes are based on their underlying template, disposables are based on their underlying disposable template. When it is essential to avoid leaving any trace, consider using Tails.
Disposables and Local ForensicsĪt this time, disposables should not be relied upon to circumvent local forensics, as they do not run entirely in RAM. This means that it will have access to everything that you open with this feature.įor this reason, it is strongly recommended that you base the default disposable template on a trusted template. In particular, the default disposable template is important because it is used by the “Open in disposable” feature. If a disposable template becomes compromised, then any disposable based on that disposable template could be compromised. See this article for more on why one would want to use a disposable. This diagram provides a general example of how disposables can be used to safely open untrusted links and attachments in disposables. While running, disposables will appear in Qubes VM Manager with the name disp#. This means that you can safely work with untrusted files without risk of compromising your other VMs.ĭisposables can be launched either directly from dom0’s Start Menu or terminal window, or from within app qubes. A disposable is a lightweight qube that can be created quickly and will self-destruct when closed.ĭisposables are usually created in order to host a single application, like a viewer, editor, or web browser.įrom inside an app qube, choosing the Open in disposable option on a file will launch a disposable for just that file.Ĭhanges made to a file opened in a disposable are passed back to the originating VM.
0 kommentar(er)
