Virtual private networks are often used to secure communication between two hosts and preserve privacy by tunneling all traffic over a single encrypted channel. Previous work has already shown that metadata of different secured channels can be used to fingerprint various kinds of information. In this work, we will dive into the encrypted tunnels as used by VPNs. We have collected automatically generated data of 9 network protocols sent over 8 different VPN solutions with 3 different rates for mixed traffic each. Due to the single combined traffic channel of the VPN, this work had to focus on packet-wise features instead of stream-wise ones, requiring the development of new features compared to related work. Both Random Forest and Markov Chains are trained to distinguish the network protocols by finding the patterns of the protocols in the developed features. We show that it is possible to fingerprint network protocols in all different scenarios based on the metadata available. Moreover, it was found that size features are more important than timing-related ones, especially when padding comes into place. Lastly, we show that obfuscations methods focussing on distorting size or timing patterns solely are not effective enough and future obfuscation methods should incorporate both features.

Interactive Robotics aims to familiarize children with robotics, which they try to do with their RoboTutor. Towards this goal they developed a platform for controlling the robots but this platform only worked for the Nao robot and not for the Pepper robot.
So for our bachelor end project we have been asked to build a connection tunnel between the server and the Nao and Pepper robots so that it is possible to also use the Pepper robot.

As our research progressed however, it became more clear to us that in order to make a generic solution for both the robots the existing platform would not suffice. So instead of only creating the tunnel we also worked on a new server side solution.
the solution we came up with, virtualization, was sure to solve the problems that caused the Pepper robot to be incompatible with the current platform. By running the server side processes for each robot inside their own environment using Docker containers we where able to create a generic solution for both robots. And with some custom code on the robots themselves, we could ensure that the robots would always connect to the server if they where connected to the Internet.