www/blog.hillion.co.uk/categories/weekly-updates/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Weekly Updates on Jake Hillion</title>
    <link>https://blog.hillion.co.uk/categories/weekly-updates/</link>
    <description>Recent content in Weekly Updates on Jake Hillion</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 02 May 2022 11:00:00 +0000</lastBuildDate><atom:link href="https://blog.hillion.co.uk/categories/weekly-updates/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Jake&#39;s Weekly - 2nd May 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-05-02/</link>
      <pubDate>Mon, 02 May 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-05-02/</guid>
      <description>Research Project Dissertation draft A block of progress on the stuff learnt so far and how each of the namespaces can be modified to create a void. The work is available here on Overleaf (permissions required), here on Gitea (no permissions required), and a current draft is available here.
Finished Table 1 (history of namespaces).
I haven&amp;rsquo;t mentioned it in the write up but this was horrible to firstly find the answers to and secondly to cite.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 25th April 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-04-25/</link>
      <pubDate>Mon, 25 Apr 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-04-25/</guid>
      <description>Research Project Dissertation draft A block of progress on the stuff learnt so far and how each of the namespaces can be modified to create a void. The work is available here on Overleaf (permissions required), here on Gitea (no permissions required), and a current draft is available here.
Finished Table 1 (history of namespaces).
I haven&amp;rsquo;t mentioned it in the write up but this was horrible to firstly find the answers to and secondly to cite.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 28th March 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-03-28/</link>
      <pubDate>Mon, 28 Mar 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-03-28/</guid>
      <description>Research Project Programming Built a new VoidBuilder struct to better align with how creating a void is described in the writing (void.rs).
A new builder describes a complete Linux void. Methods allow you to make it less of a void as you see fit. This aligns well with the structure in the write up. Creating a void first then adding only precisely what is needed to it. It&amp;rsquo;s also a much higher level API that&amp;rsquo;s object oriented.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 14th March 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-03-14/</link>
      <pubDate>Mon, 14 Mar 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-03-14/</guid>
      <description>Research Project Read Capsicum (Watson et al., 2010) I re-read this paper, but in the context of my project&amp;rsquo;s work, it provided some incredibly useful insight. I&amp;rsquo;ve listed the most important takeaways here, but there are more.
My niche might now be figured out. Capsicum discusses eliminating dual-coding by only being in the code, at the cost of potential static analysis. By using high-level language integrations, I think that my solution can achieve both being integral to the code and having a static description.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 28th Feb 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-02-28/</link>
      <pubDate>Mon, 28 Feb 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-02-28/</guid>
      <description>Research Project Process Isolation Expanded the shim with so called PipeTriggers.
Wrote an example for this (examples/pipes/main.rs). Wrote the specification for this application to be launched with the shim (examples/pipes/spec.json). I think this is very neat and certainly a focal point of the project. This style of request driven programming that the shim enables with a powerful level of privilege dropping each time should be useful. The spec is also pretty easy to parse and even write for this too.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 13th Feb 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-02-13/</link>
      <pubDate>Mon, 14 Feb 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-02-13/</guid>
      <description>Research Project Process Isolation Built the shim in Rust (clone_shim).
Wrote a quite nice to use wrapper for the clone3 syscall in (relatively) safe Rust (clone.rs).
Wrote the basis of specification, that should be extensible enough for future features (specification.rs).
Currently this reads only JSON specifications, but Rust&amp;rsquo;s serde library has support for a variety of binary formats to try later on. Started tying things together. Currently on the running at startup launches work, but they do launch and it&amp;rsquo;s a strong basis to add more features from.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 31st Jan 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-01-31/</link>
      <pubDate>Mon, 31 Jan 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-01-31/</guid>
      <description>Research Project Process Isolation Built three privilege separated test applications.
Wrote a privilege separated fib implementation (fib_priv_sep.c).
Pretty basic separation as the program is trivial. In the later cp example I did privilege separate the arguments, but I didn&amp;rsquo;t for the purpose of fib. Starting to build up a structure. The files are structured to have a main implementation reminiscent of the eventual shim, while the functions like real_main would come from the eventual binary.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 17th Jan 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-01-17/</link>
      <pubDate>Sat, 15 Jan 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-01-17/</guid>
      <description>Research Project Process Isolation Wrote an OCaml binding for the clone3 syscall (clone_shim.ml/clone3_stub.c).
Some decisions made to make this feel a bit higher level: List of flags rather than ORed together numbers. Options used where helpful. Looked into using an OCaml callback, but of course this doesn&amp;rsquo;t work (as expected - OCaml didn&amp;rsquo;t like Multicore!). Currently execve&amp;rsquo;s a specific binary (/bin/sh), but should be easy to extend. Tricky to know sometimes what to put in C and what to put in OCaml.</description>
    </item>
    
    <item>
      <title>Jake&#39;s Weekly - 3rd Jan 2022</title>
      <link>https://blog.hillion.co.uk/posts/weekly-2022-01-03/</link>
      <pubDate>Sat, 01 Jan 2022 11:00:00 +0000</pubDate>
      
      <guid>https://blog.hillion.co.uk/posts/weekly-2022-01-03/</guid>
      <description>Research Project Process Isolation Setup a Fedora testing VM for easier and consistent testing.
Fedora 35 uses pure cgroups2 by default - very useful! Sorted out backups for the repo and the above machine. Chose a testing framework for C enabling testing of the assertions to build the project upon.
Used Unity. Simple and the examples show that it doesn&amp;rsquo;t do much beyond the minimum - important for this low level code with syscalls.</description>
    </item>
    
  </channel>
</rss>