Public hidden services
- Forum intended to discuss activity of Deep Tech Group itself.
- Git repositories for DTG and community projects.
- Trac – issue tracker and wiki.
More information about our services is available at this wiki page. All the services are implemented using docker and docker-compose so you should be able to create your own instances easily.
Planned evolution of these basic services: private E2E-encrypted issue trackers, wiki and git repositories.
Planned deployment guides for personal services
- How to create personal VPN and Tor bridge
- We do not provide non-anonymous VPN and Tor bridges. That would have allowed us (as well as an attacker who gained access to our infrastructure) to identify our users. VPN at the entrance to network is a personal service just like Internet access from ISP.
- How to properly store (and effectively work with) sensitive information
- Sensitive information shouldn’t be stored at the personal computer. It should be stored encrypted at third party server.
- How to create personal outgoing VPN or proxy. Enter via Тор and I2P, exit to Internet.
- Such service is useful to hide usage of Tor from the target site (e.g. many sites block Tor entirely).
- How to deploy Delaytor service
- Implementation of protection from practical attacks against Tor.
Planned services: the second stage
Planned services useful for general public, not only for operation of DeepTech group. The list is very preliminary, it is discussed here.
- Matrix. Entrance via Tor and I2P, federation with normal Matrix network
- Why Matrix? There are quite a few public jabber services but almost no independent Matrix servers. Also need to work on Matrix’s metadata protections (online status, contacts, timestamps of messages etc), by default it is not protected.
- Jabber. Federation with normal Jabber
- Mumble. Voice services
- Need to use audio codecs suitable to work over Tor and I2P
- Delivery to Clearnet and other Tor and I2P providers
- Mailing lists
Our community relies on anonymizing networks. We have to support their infrastructure:
- Tor relays, including non-personal bridges
- I2P routers
- Bitmessage servers
- Anonymous remailers
Security of DeepTech’s infrastructure
We have to ensure security of our services. Following means are suggested:
- Use protection systems. For example IDS
- Perform regular penetration testing
While we’re trying to make our infrastructure as secure as possible, it shouldn’t be relied upon. It can be compromised. Here are advices to increase your security:
- Deploy your own private services when it is possible (and makes sense)
- Use decentralized software (though it can be vulnerable too)
- Use anonymizing technologies that protect metadata. For example, anonymous remailers.
We’re working on anonymizing software to protect metadata of the client even if the server is compromised (owned by attacker). While it is intended to be used for blogging, social networks and messengers, it can be used to access our services to increase your security.
Co-operation of independent communities
Joint service creation
DeepTech group proposes independent communities to co-operate for creating services. For example, a community needs some service. Highly probably the service will be useful for other communites too. So technically skilled people from all interested communities join DeepTech group and work on the service together.
Potential topics of collaboration for communities within DeepTech group:
- Docker containers, deployment guides for services
- Templates of sites, blogs (e.g. static site like this one)
- Consultation, tech support
- Application development
Helping particular community
Any independent community can ask DeepTech group to help with
- creating and administrating their infrastructure
- web design and development
- penetration testing
Of course, participating in such ‘private’ projects is non-mandatory for DeepTech group members. Requesting community will need to catch the interest of other members. This may go outside the technical limits of the group.
We suggest to put such requests in a special subforum. Be careful: obviously, there is a risk of deanonymization (use another pseudonym if it matters to you).