Help to create dev environments for bug hunting - Inheritance issues

[apparatus]

@EntomoSci

Updated configuration made to template qube

I changed the BurpSuiteCommunity directory containing the executable to /opt/ and created a symbolic link called
burp pointing to /opt/BurpSuiteCommunity/BurpSuiteCommunity at /bin (which is a symlink included by default pointing to /usr/bin), so I can trigger BurpSuite with burp command from all the standalones based on that template qube.
I don’t know if this is the better approach given the Filesystem Hierarchy Standard or some Qubes OS best practices, but it works!

Feedback is always appreciated.

You can just add the directory with binaries to the PATH environment variable, e.g. in template run:

echo 'export PATH="/opt/BurpSuiteCommunity/BurpSuiteCommunity:$PATH"' >> /etc/profile.d/opt.sh

@EntomoSci

About docs likely being wrong

What do you recommend in this case?
If the docs are wrong how to proceed and contribute?
I don’t feel an advanced Qubes OS user yet to tweak too much the docs and make a pull request of that size.

You can try to edit the docs, it’s not too hard and the whole process of editing the docs with screenshots as an example is available:

Qubes Documentation

The documentation is a community effort, and everyone is welcome to contribute. There is currently already an effort underway to migrate the documentation to “Read the Docs” (RtD), which looks similar to the documentation you linked. You can read more about that effort here: https://groups.google.com/g/qubes-devel/c/ASj7tehn1G0 You can read more about how to submit documentation changes here: You may also be interested in the documentation style guide: