<?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>School on kimobu</title><link>https://www.kimobu.space/tags/school/</link><description>Recent content in School on kimobu</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright Kimo B</copyright><lastBuildDate>Fri, 13 May 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.kimobu.space/tags/school/index.xml" rel="self" type="application/rss+xml"/><item><title>Reflecting on Completing a PhD</title><link>https://www.kimobu.space/posts/Reflecting-on-a-PhD/</link><pubDate>Fri, 13 May 2022 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Reflecting-on-a-PhD/</guid><description>&lt;p&gt;In March of this year, I successfully defended my dissertation &lt;a href="https://scholar.dsu.edu/theses/381/"&gt;An Application of Machine Learning to Packed Mach-O Detection&lt;/a&gt;. After four years, I completed a &lt;a href="https://dsu.edu/programs/phdco/index.html"&gt;PhD in Cyber Operations&lt;/a&gt; from Dakota State University (DSU). In this post, I want to reflect on this journey, what I learned, and thoughts on the program.&lt;/p&gt;
&lt;h1 id="curriculum"&gt;Curriculum&lt;/h1&gt;
&lt;p&gt;The DSU PhD in Cyber Operations consists of core technical classes, core research classes, electives, and the dissertation. When I started the program, it was actually a Doctor of Science (DSc) vice a Doctor of Philosophy, but the South Dakota Board of Regents approved the transition to PhD relatively soon after my acceptance.&lt;/p&gt;</description></item><item><title>Converting DoH to DNS</title><link>https://www.kimobu.space/posts/Converting-DoH-to-DNS/</link><pubDate>Wed, 06 Jan 2021 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Converting-DoH-to-DNS/</guid><description>&lt;p&gt;In a &lt;a href="https://www.kimobu.space/posts/Investigating-DoH/"&gt;previous post&lt;/a&gt; I wrote about investigations
that I performed on DNS over HTTPS (DoH). That research was performed as part of
&lt;a href="https://catalog.dsu.edu/preview_course_nopop.php?catoid=32&amp;amp;coid=20604"&gt;Cyber Security Research&lt;/a&gt;. During
&lt;a href="https://catalog.dsu.edu/preview_course_nopop.php?catoid=32&amp;amp;coid=20607"&gt;Security Tool Development&lt;/a&gt;, I
expanded on that research by implementing a Python script which creates DNS wire
format packets from a DoH packet capture. This post describes how that script
was made and how it works.&lt;/p&gt;
&lt;h1 id="updates-to-gen_dohpy"&gt;Updates to gen_doh.py&lt;/h1&gt;
&lt;p&gt;In addition to the use of &lt;code&gt;sslkeylog&lt;/code&gt; which was discussed in the previous post, I needed to update the &lt;code&gt;client_protocol.py&lt;/code&gt; file. Line 45 of that file contains:&lt;/p&gt;</description></item><item><title>Investigating DoH</title><link>https://www.kimobu.space/posts/Investigating-DoH/</link><pubDate>Tue, 31 Dec 2019 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Investigating-DoH/</guid><description>&lt;h1 id="dns-security"&gt;DNS Security&lt;/h1&gt;
&lt;p&gt;As a plain-text protocol, DNS lacks Confidentiality, Integrity, and Availability (CIA) protections. An attacker who can observe DNS activity can see where the DNS request originated from, where responses came from, what the query and response were, or tamper with the response.&lt;/p&gt;
&lt;p&gt;DNS over HTTPS (DoH) effectively mitigates many of those weaknesses. Instead of being a plain-text protocol over UDP, DoH is an exchange of DNS queries and responses over a TLS encrypted connection, using the HTTP2 protocol to transmit messages. Because of this encryption, an attacker can neither observe nor tamper with DoH queries and responses.&lt;/p&gt;</description></item></channel></rss>