Thanks for providing additional information to readers. However, this is not entirely correct. Let me clarify:
- Community nodes are used to diversify server ownership and strengthen the privacy of connections.
- Community nodes may technically act as entry, middle and/or exit nodes.
- Community nodes will never be used for unencrypted connections, only for encrypted connections. We are thinking about a concept of trusted partners, which will also be allowed to handle unencrypted connections - but this is currently not the case.
- We publish advisories [0], which are automatically applied by all clients. This gives us the ability to quickly react to changing situations. Currently, community nodes _are_ being selected as exit nodes, but not as entry nodes.
I hope this cleared things up. I am happy to go into more detail.
- Community nodes are used to diversify server ownership and strengthen the privacy of connections.
- Community nodes may technically act as entry, middle and/or exit nodes.
- Community nodes will never be used for unencrypted connections, only for encrypted connections. We are thinking about a concept of trusted partners, which will also be allowed to handle unencrypted connections - but this is currently not the case.
- We publish advisories [0], which are automatically applied by all clients. This gives us the ability to quickly react to changing situations. Currently, community nodes _are_ being selected as exit nodes, but not as entry nodes.
I hope this cleared things up. I am happy to go into more detail.
[0] https://github.com/safing/intel-data/blob/master/spn/main-in...