<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/research/</link><description>Recent content in Research on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 11 Apr 2022 11:42:42 +0200</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/research/index.xml" rel="self" type="application/rss+xml"/><item><title>Container Deep Diving: Part 3</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-3/</link><pubDate>Mon, 11 Apr 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-3/</guid><description>After looking at the nitty gritty functionality of containers in Part 2 lets make life a bit easier now. First by making this post a short one and secondly by using tools for abstracting away the manual labour that had to be done in order to switch namespaces and set them up. For this lets take a look at container runtimes.
While you have probably heard of and used Docker lets talk about the common layer that underlies modern Docker and other runtimes.</description></item><item><title>Container Deep Diving: Part 2</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-2/</link><pubDate>Thu, 03 Feb 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-2/</guid><description>Okay, so here we are in part 2 of the container post series.
At the end of part 1 we were able to identify the problems of just using chroot to achieve process isolation on a machine. With this post the goal is to have the same functionality - running bash with test-root as the new root directory with the same technologies as containers. Once that is running we will adress the problems of seeing all the network interfaces as well as still being able to kill arbitrary processes on the machine.</description></item><item><title>Container Deep Diving: Part 1</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-1/</link><pubDate>Fri, 07 Jan 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-1/</guid><description>Containers serve 1 purpose. Selling kubernetes certificates! \s
But of course there is more to it then just hype.
Over the next few posts on my blog I would like to dig into the container world, see how we got to the current state and show what the current state actually is.
Overview So what is the real purpose of containers?
Isolate different families of processes on 1 computer from each other, so that if a process is ever compromised it does not affect any other processes on the same machine.</description></item><item><title>Bug hunting on iOS 6.3.1</title><link>https://blog.sodawa.com/blog/bug-hunting-on-6-3-1/</link><pubDate>Wed, 14 Nov 2018 15:35:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/bug-hunting-on-6-3-1/</guid><description>Impulse Me and my SO recently got an old iPad2, which we were planning to use for everyday usage around the house. Meaning, having it ready to research a recipe, get information about a topic or researching things to do together.
Unfortunately though, the iOS version that it came preinstalled with was 9.3.5. On this later version of iOS there is quite a problem with the responsiveness though.
Probably due to the big alterations on the design side the iPad feels slow and has noticeable lags when switching between applications, and even when using the web browser.</description></item></channel></rss>