teilpunkt

Important

Until version 1.0.0 it is not recommended for production use. Work in progress - certain features might not be complete.

teilpunkt™ (ger. sharepoint) is a C++23 self-hosted, security first, file server implemented natively for Linux® using modern technologies.

Dependencies:

• uWebSockets (latest): HTTPS server and sockets
• libsodium (latest): Crypto Primitives
• libsodium.js (latest): Crypto Primitives for the Frontend
• glaze (latest): JSON library
• ankerl (latest): Optimized Hashmap

Note: This project is built only with/for GCC and the Linux® kernel.

Feature Highlights:

• Security first approach using modern technology
• Websocket enabled file transfers
• Supports passkey and MFA authentication
• Fast and compliant multithreaded webserver with uWebSockets
• Linux native filesystem and webserver
• Comprehensive auditing and logging accessible with various endpoints
• Modern and lightweight frontend accessible on all devices
• Many more to come...

Deployment

Disclaimer: Currently teilpunkt is not ready to be deployed

teilpunkt chooses its default settings favoring security over convenience in order to avoid mishaps. Tradeoffs for more convenience have to be made explicitly by the admin that deploys the instance.

Customization

Nearly all aspects of teilpunkt can be customized to accommodate for various deployment situations. It chooses more secure defaults to avoid mishaps. Tradeoffs for more convenience have to be made explicitly by the admin that deploys the instance.

Storage

You can configure multiple storage locations (storage endpoints)

Security

These are the active (and passive) security measures used by teilpunkt.

Storage

• Use of encryption for all persisted files

Transfer

• Use of HTTPS for encrypted traffic
• Use of client side hashing of credentials

Deployment

• Runs only on Linux kernel
• All unneeded ports blocked (with setup.sh)
• Core dumps disabled (with setup.sh)
• Use of locking and blocking sensitive memory regions
• Use of encrypting sensitive data in memory with TPM support

Frontend

• Use of file hashes for served static files to detect tampering
• No usage of CDN's, font providers or third parties services to avoid sharing user data (IP, ...)
• No frontend framework for simple and auditable code

Source Code

• Use of clear code formatting
• Use of simple code style (C + templates)
• Use of only few dynamic memory

Compilation

• Only compiles with recent GCC
• Use of safe optimization level -O2
• Use of symbol stripping (except relocation information to not hinder ASLR)
• Use of many compiler warning flags

Implementation

Threading

WebServer Threads (2-x):

• Handle incoming HTTP requests
• Directly handle tasks that return immediately:
  • Modify virtual filesystem
  • Create, Login or Remove users
  • Change settings, etc.
• Also handles chunked file transfer:
  • Use of non-blocking sockets allows to have many connections even per thread

Worker Threads (1-x):

• Priority-based queue worker system
  • Only run tasks that are explicitly given to them

Background Thread (1):

• Runs the main event loop
  • Handles incoming events
  • Adds tasks to the worker thread

This means it runs hardware concurrent on devices with 4+ cores.

Instance

Files and Data

Notice

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.