<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>~ on Unsorted Stuff</title>
    <link>/</link>
    <description>Recent content in ~ on Unsorted Stuff</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Wed, 01 Jan 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>O stránce</title>
      <link>/about/</link>
      <pubDate>Tue, 14 Jul 2020 15:51:14 +0200</pubDate>
      
      <guid>/about/</guid>
      <description>Tato stránka je v přípravě, ještě tu nic není. Každopádně se jedná o soukromé stránky pro potřeby jedné rozvětvené rodiny. Ačkoliv věřím tomu, že by se řešení mohlo hodit i dalším rodinám, v tuto chvíli není v plánu žádné rozšiřování.
Nicméně &amp;ndash; pokud to všechno dobře dopadne, celý návrh řešení, všechny poznámky a informace k zabezpečení bych rád vyvěsil a dal volně k dispozici.
Pěkný den, admin</description>
    </item>
    
    <item>
      <title>2020-January</title>
      <link>/docs/newsletters/2020-01-newsletter/</link>
      <pubDate>Wed, 01 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>/docs/newsletters/2020-01-newsletter/</guid>
      <description>A Very Long Good Bye  “I didn’t have time to write a short letter, so I wrote a long one instead.”
― Mark Twain
 Good news, everyone! A new issue of my very irregular (not-so-much-about-security-now) newsletter is out!
My original idea of publishing this every quarter (or so) was clearly too optimistic, as you can see. Which leads to a huge problem &amp;ndash; there&amp;rsquo;s a load of links and texts I&amp;rsquo;d like to share with you, and the length of the text could be demotivating, I know.</description>
    </item>
    
    <item>
      <title>2018-November</title>
      <link>/docs/newsletters/2018-newsletter/</link>
      <pubDate>Thu, 01 Nov 2018 00:00:00 +0000</pubDate>
      
      <guid>/docs/newsletters/2018-newsletter/</guid>
      <description>Long time, no see… It’s been a while since I shared any news from the outer world. Doesn’t necessarily mean I stopped reading or caring about the world or you, it just was a difficult year for me. But it’s time to restart this activity, hopefully with more feedback this time! :)
Before we really start, I’d like to thank Shawn McGhee and Marek Kumpost for their suggestions, corrections and help with this.</description>
    </item>
    
    <item>
      <title></title>
      <link>/docs/projects/secure-home-net/brainstorming/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/projects/secure-home-net/brainstorming/</guid>
      <description>Secure Home Network Subnet Definitions Let&amp;rsquo;s start with some subnets definitions:
 VPN subnet  For indidivual users B2B (or rather Home-2-Home) networks will use individual subnets.   WiFi  guest kids main   Docker/VMs  For any kind of VMs, Kubernetes, etc.   Infrastruktura  Switches, routers, APs, management interfaces of NAS, anything else fitting this category (e.g. Docker mgmt) LDAP, Kerberos, Keycloak   Home network  Most likely the same thing as the main Wi-Fi network.</description>
    </item>
    
    <item>
      <title></title>
      <link>/docs/projects/secure-home-net/resources/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/projects/secure-home-net/resources/</guid>
      <description>Interesting Resources    URL Description     HomelabOS Basically a personal datacenter, which is a huge part of what I&amp;rsquo;d like to put together.    </description>
    </item>
    
    <item>
      <title></title>
      <link>/docs/teaching/memory-analysis/materials/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/teaching/memory-analysis/materials/</guid>
      <description>In-Memory Malware Analysis This page contains some information and links for In-Memory Malware Analysis course.
In case of any questions, don&amp;rsquo;t hesitate to contact me at vaclav.lorenc-at-gmail.com or @valorcz on Twitter.
Course Texts  In-Memory Analysis (text) &amp;mdash; A brief introduction to reverse engineering and memory forensics (English). In-Memory Analysis (slides) &amp;mdash; Handouts for this course (English).  Tools and Templates  In-Memory Analysis (tools) &amp;mdash; A bootstrap folder structure with Volatility Framework and other tools.</description>
    </item>
    
    <item>
      <title></title>
      <link>/docs/teaching/memory-analysis/sample-report/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/teaching/memory-analysis/sample-report/</guid>
      <description>PV204: Sample Analysis Report This is a sample report describing analysis of xp-infected.vmem memory image (i.e. exercise01). We&amp;rsquo;ll demonstrate both the structure of the report and one of the possible analysis workflows you could use for your own research/work.
Sample Preparation Before we start with the analysis, we need to download the memory image. That can be done via exercise 1 command issued on the VM command line (see the official course documentation for more details).</description>
    </item>
    
  </channel>
</rss>