... | ... | @@ -10,7 +10,9 @@ please see the [donation site][]. |
|
|
[donation site]: https://donate.torproject.org/
|
|
|
|
|
|
This list is not final, and if you have questions, please [contact
|
|
|
us](doc/how-to-get-help).
|
|
|
us](doc/how-to-get-help). Also note that we also accept virtual
|
|
|
machine "donations" now, for which requirements are different, see
|
|
|
below.
|
|
|
|
|
|
## Must have
|
|
|
|
... | ... | @@ -39,3 +41,39 @@ us](doc/how-to-get-help). |
|
|
* proprietary Java/ActiveX remote consoles
|
|
|
* hardware RAID, unless supported with open drivers in the mainline
|
|
|
Linux kernel and userland utilities
|
|
|
|
|
|
# Virtual machines requirements
|
|
|
|
|
|
## Must have
|
|
|
|
|
|
Without those, we will have to be basically convinced to accept those
|
|
|
machines:
|
|
|
|
|
|
* Debian OS
|
|
|
* Shell access (over SSH)
|
|
|
* Unattended reboots or upgrades
|
|
|
|
|
|
The latter might require more explanations. It means the machine can
|
|
|
be rebooted without intervention of an operator. It seems trivial, but
|
|
|
some setups make that difficult. This is essential so that we can
|
|
|
apply Linux kernel upgrades. Alternatively, manual reboots are
|
|
|
acceptable if such security upgrades are automatically applied.
|
|
|
|
|
|
## Nice to have
|
|
|
|
|
|
Those we would have in an ideal world, but are not deal breakers:
|
|
|
|
|
|
* Full disk encryption
|
|
|
* Rescue OS boot to install our own OS
|
|
|
* Remote console
|
|
|
* Provisionning API (cloud-init, openstack, etc)
|
|
|
* Reverse DNS
|
|
|
* Real IP address (no NAT)
|
|
|
|
|
|
## To avoid
|
|
|
|
|
|
Those are basically deal breakers, but we have been known to accept
|
|
|
those situations as well, in extreme cases:
|
|
|
|
|
|
* No control over the running kernel
|
|
|
* Proprietary drivers |