7.3.1. Is the Fedora Security Lab Test bench a Live CD?¶
No, it’s a default Fedora installation which is configured with the help of Ansible. For setup a system like the Fedora Security Lab Test bench some file modifications are needed. Live CDs don’t allow to ship modified content or files.
7.3.2. Why not make RPMS of all parts?¶
Because the Package Review process in Fedora is slow (even for simple packages it takes months and I wanted to have the FSL Test bench now). Most software core parts are coming out of the Fedora Package Collection. The surrounding items and the configuration are installed by Ansible out of their upstream sources.
7.3.3. Will the Fedora Security Lab Test bench become a Live CD one day?¶
I don’t think so, but never say never. We are customizing configuration files. Those configuration files are modified during the setup process to match the provided environment. The web interface is dynamically generated according your choises on the fly. This is not possible with a Spin.
7.3.4. Do you provide a VM or something similar?¶
No, because one big issue is trust. Providing a VM is like shipping a blackbox. You have to trust us about what’s inside the VM. By using Ansible’s playbooks you can see what steps are taken to setup the FSL Test bench. You are in control of every setup step, nothing is hidden and everything is transparent. The core components are installed out of the Fedora Package Collection on top of a minimal Fedora installation. This ensure that the operating system runs the latest packages and behave with integrity.
7.3.5. How should the network around the FSL Test bench looks like?¶
As mentioned on the setup page a DNS/DHCP server is a requirement. For security purposes we suggest that you use a dedicated network for setup your FSL Test bench.
7.3.6. Is internet access needed for the Fedora Security Lab Test bench?¶
For the setup access to the internet of the system which will host the FSL Test bench is needed. When the setup is finished, you can shutdown the internet access. DO NOT expose the FSL Test bench to the internet. Bad things could happen. You have been warned.
7.3.7. Can I use the FSL Test bench repository to setup a Fedora Security Lab?¶
7.3.8. Why are you still using yum and not dnf?¶
dnf was used, then we switched back to
yum. Soon we will switch
dnf again because DNF will become the next default Package manager for
Fedora. And as always we wanted to be ahead of the rest of the world.
7.3.9. Do you have some reference installations?¶
No. This is project is a proof of concept only at the moment.
7.3.10. How long does it take from Zero to go?¶
Creating a libvirt-based virtual machine and using Ansible to configure it, takes something between 25 and 30 minutes. It heavily depends on your hardware and the speed of your internet connection.
7.3.11. Is The Fedora Security Lab Test Bench vulnerable for Heartbleed?¶
It depends on the point in time when you created your Test bench. Check if
you are running at least with
7.3.12. Is this something similar to Fedora Formulas?¶
Yes, it is. Basically we skipped the discussions and just made an implementation which we think is feasible for our needs.
7.3.13. Why is this project not hosted on Fedorahosted.org?¶
Because github offers easy access to the git repositories for everyone not only Fedora contributors. To get as many contributions as possible we need to be as open as possible. The Fedora Security Lab is hosted on Fedorahosted.org and we don’t plan to change that.
7.3.14. Can I contribute?¶
Sure, contributions are appriciated. Please for the Fedora Security Lab Test bench repository and when you are done, open a Pull request.